Can a non-python-programmer set up a Django website with a few hours of practice?

I have very minimal Python experience (some sql and vba experience) and am looking to build a simple Django-based webapp for work. Is this something I can do relatively quickly and easily early-on in my Python journey? I know it's not exactly a Wix website but I'm attracted to Django's simplicity and scalability. Will I have difficulty with this as my first dip into Python?

update: WOW this blew up. Thanks for the responses everybody. I should have provided more detail but basically I would like my website to be a simple Group of Fields that would allow the user to input vehicle data into our MYSQL database (or at least into a format easy enough to clean and put into our database). The reason we are using Django over Flask is because of its security features. I have actually finished sentdex's tutorial but I am having trouble knowing what all the possible webapps are, what files/directories I need to create to add new features, and how to modify the end result of that tutorial. Also the tutorial, while excellent, is a little old now. I spent a long time trying to figure out why Django wasn't fetching my Bootstrap CSS sheet but it (kind of) worked out in the end.

I love the simple admin of Django and I think I will stick with it. Does anybody know of any cheatsheets or "for x result do y" with Django/Bootstrap? Or how to get it working with MySQL? I would love to get this built and return to improve on my foundational knowledge afterwards.

I really tried hard for that time, but my close to 0 linux knowledge made me even re-install linux several times before I even figured out how to get a GUI on it. We're talking about very basic level. At that level, Flask is miles away easier to set up than Django because the documentation was honestly confusing, so I was suggesting to the OP to try that instead if it's too hard. If instead you want to judge me, feel free.

I have to say it took me two weeks before I got there in a good way. My lack of understanding and inability to find a simple guide that explains high level that the flow is something along the lines of URL dispatcher > view > template didn't help much. The rest was easier and just time taken to figure stuff out. Agreed day 1 flask is easier.

To set up a Django app you have to learn its special ritual which can be a pain in the ass for a complete beginner. The official docs are not especially helpful for absolute beginners to be honest. For a non Python programmer https://tutorial.djangogirls.org is probably the best choice.

If you want simplicity you should use Flask. If you want scalability you should use Django. That's the status quo in the Python world.

To set up a Django app you have to learn its special ritual which can be a pain in the ass for a complete beginner.

Truer words have never been spoken, I had to do the tutorials several times over to really get a hang of it.

But once you do know the ritual it becomes quite easy.

The official docs are not especially helpful for absolute beginners to be honest.

The docs sometimes seem vague about what you should do and only state what you can do. Which leaves a world of possibilities but few standards (best practices) it seems.

Moreover Django abstracts a lot of the complexities away from building a web app, thought this sometimes can leave you with more questions than answers as to how you should do something that's not explicit in the documentation.

I recently was trying to setup channels in order to have a simple user notification, was a little frustrating to say the least. Without diving into the source code, along with outdated half-answered SO submissions I would still be stuck.

Don't get me wrong, Django is an amazing tool for building webapps, just the learning curve can be a bit steep.

One of the things I love about Django is that it comes with tons of stuff out of the box. The community has also written apps for pretty much everything that you can plug in and start using. Whereas in Flask you are expected to write some of that stuff yourself with a more DIY approach.

For instance, if I want to add credit card payments for my users and I have no user interface or Stripe code at all, I can just add an app to get a user interface and one for a Stripe backend. Then it allows me to focus on writing real time notifications or a rare feature that has not been built by somebody else.

It's more that as your app grows bigger, you'll need to use more and more of the features that comes out-of-box with Django but not with Flask. A small application might not need all the stuff that Django comes with (so Flask will get you up and running quicker), but if you're expecting the application to get bigger you'll be happier off if you started with Django instead of Flask.

For example, the second you need to deal with db migrations, Django is a better choice. Same thing with using an ORM (the Django ORM is hands down the best ORM available in any language).

Is SQLAlchemy your preference? I've never really done a deep dive with it, but I've always been bummed working with it when I'm building Flask applications, knowing that Django's ORM is right around the corner.

From what I understand it seems like SQLAlchemy is more powerful, but the Django ORM feels so intuitive in comparison.

When your code undergoes a schema change from one version to another (like adding a column to a table), the update to the database schema is considered a migration. Tools like Django or SQLAlchemy's Alembic can generate the scripts to apply and roll back said migrations. Or perhaps the scripts are, themselves, called the migrations. IDK

Mypy is just a static type checker that verifies your static type annotations. You can make it as strict or as loose as you want regarding calls off to untyped libraries. I have mine fairly strict, but my project almost exclusively uses the standard library.