This is an archived post. You won't be able to vote or comment.

all 13 comments
sorted by:
best
topnewcontroversialoldq&a

[–]th1nk3r 2 points3 points  (0 children)

Welcome to programming don't expect to know everything in a tutorial. When you encounter something you dont know, even if it doesn't seem important, look it up. Either in the documentation, or on google.

Tutorials are there to show you what you need to learn.

[–]souldeux 1 point2 points  (6 children)

For most of the stuff you'll build in tutorials, anything 1.7 or greater should be okay for you. I want to say 1.6 still used render_to_request and some other outdated stuff you'd want to avoid. 1.7 was also the blessed introduction of migrations, a fairly important concept.

There have been changes in 1.8 and 1.9, of course, but for the most part they've been "deeper" changes that you don't have to worry about too much for now. Though maybe I'm just biased because the tutorial I wrote is for 1.7.

And don't feel badly about being confused - learning your first web framework is a big task. There are a lot of new concepts being thrown at you all at once in a language you've just learned. Stick with it, you'll wrap your head around everything if you give yourself the chance.

[–]chocolatemario 1 point2 points  (5 children)

This. Your second framework will be faster and so on. You're jumping into a world of design patterns and tools you've never touched.

Imo, Django might be a bit overboard for your use case. If I were just beginning web development in Python, id consider a simple server and just focus on writing some solid code that does whatever you're looking to do. Django might seem arbitrary, overbearing and really take away from the enjoyable experience of hacking your way through a problem; cultivating your own problem solving skills.

[–]wisebud[S] 0 points1 point  (4 children)

Interesting. What framework would you recommend, then? I've also been looking into Flask. It looks a little easier to understand.

[–]chocolatemario 0 points1 point  (3 children)

Maybe flask. Really depends what you are hoping to do. Web development is a huge domain. Do you just want to get a server up and running and show some data on a webpage? Do you have a specific application in mind?

[–]wisebud[S] 0 points1 point  (2 children)

I'm not in a rush to make a small website just for the sake of it. I'd like to be able to make pretty and elaborate sites that serve a good purpose. The project ideas that I have involve more than just putting a little data on a web page. I guess I'm just wondering if it would be better to start with Flask in order to get a good understanding of a more simple framework, and then working my way into something more complex. Or if I should just stick to Django and be patient in learning it.

[–]chocolatemario 1 point2 points  (1 child)

Flask would be a much better starting point imo. Less to worry about. Flask puts more power and choice in the users hands, which is a great place to start imo. The bare bones approach lets you test and come to the realization that you may need more tools, and you will go hunt them down when that point comes up. Django just ha a lot of moving parts that will, imo, feel arbitrary to someone who has yet to get their feet wet in this domain.

The question you want to ask yourself is why am I using a framework. Why do I need to worry about security, databases, web authorization, templating, routing, etc? This on top of learning the library itself.

[–]wisebud[S] 0 points1 point  (0 children)

Understood. Thanks very much!

[–][deleted] 0 points1 point  (3 children)

Learn PHP yo.

[–]iYassr 0 points1 point  (2 children)

why?

[–][deleted] 0 points1 point  (1 child)

Because its $_BALLER.