I would've loved to have had this resource when I was starting out and so desperately wanted to move to Python from PHP, but had little idea how.<p>Also, there's so little mentioned of Pyramid, which in my opinion is the most elegant Python framework there is.
I'm learning Python as part of a data science class and not for building web apps.<p>This article mentions a-ha moments in relation to Python conditionals. What is so special about Python conditionals? They seem pretty ordinary to me.
Great idea. Will sure read more on your site later on, but one thing that struck me is "Pyramid applications are built using a model-view-controller architecture." There is a note in pyramids design defenses which says they do not consider pyramid to be a mvc: <a href="http://docs.pylonsproject.org/projects/pyramid/en/1.3-branch/designdefense.html#pyramid-gets-its-terminology-wrong-mvc" rel="nofollow">http://docs.pylonsproject.org/projects/pyramid/en/1.3-branch...</a>
Interesting content. "Full Stack" means all those server-side bits <i>and</i> the client application portions as well. i.e., "everything". This looks like it addresses only the server-side part of the "stack".
Love the content! It's lame to say, but the first sentence under the Web Framework section has a subject-verb agreement issue. Believe it should be "makes," not "make."
I think recommending Python 3 would be good in this tutorial. Since the people that read this are probably starting a new project and both recommended frameworks support it.
Great timing as I was recently looking for a resource like this. I've been leaning towards Flask (vs. Django) so I'll definitely check this out.
Well I thought this is a project where you write django with python generated CSS and HTML, ZODB for db and some other kind of pure python mockup of redis/memcached, and using Tornado to replace Nginx. Now that's compelete-stack python
I guess it may be out of the scope for that book, but i was expecting a mention of saltstack on the deployment part. Since there wasn't any mention of any provisionning tools ( or i didn't see where), i suppose it's on purpose.
I think the virtualized servers was oversimplified a bit. In reality, 1 virtual core is generally less than 1 physical core. Virtual cores aren't on a 1 to 1 basic with physical cores.
Lately I've been writing some small scripts in Python to automatize some work and learn the language too, so this site is just what I needed. Great stuff.
This is such a useful guide for me. Especially as someone from the LAMP stack who played with javascript on the server side that left a bad taste in the mouth, I've finally turned to python (flask, uwsgi, nginx). I wish I had known about this site earlier, it has valuable information.