Would anyone buy "Custom Debian repositories as a way to organize your deployment"? How about "Django deployment best practices"? Or "Leap from PHP to Django"?
I don't think there's any reason to cast doubts on my integrity.
In what way does PHP's standard library fall short that Python overcomes?
In what ways does PHP's standard library fall short of Python's? I was never comparing the two. I have always found that both could get the job done, except PHP's uses a very weak naming convention/has none at all.
I was comparing PHP's standard library features with those of Django. Here, Django wins hands down. If you are not familiar with either, I recommend trying reading through their tutorials and seeing which one comes out with a more complete product in which one feels less messy.
Lastly, implying that PHP's standard library is not a framework because it is not built in PHP ("A framework is an abstraction built up USING a programming language, like PHP.") is just plain wrong. If I decided to speed up Django by re-writing every line of its code in C and making it an extension to Python rather than a Python module, without breaking any function signatures, would Django cease being a web framework? What would it become then? What if instead of C I chose Visual Basic, or Common Lisp, or F#, or even PHP (assuming I found a decent way to compile it to a binary)? A framework is collection of code that abstracts certain functionality. See http://en.wikipedia.org/wiki/Software_framework for further information.
EDIT: I am not at all talking about PHP the language vs Python. The two are different and both have some very interesting features. PHP 5 has grown up to be a pretty interesting general purpose dynamic language. I am specifically talking about using PHP on the web.
Where you call pre-populated global variables "language constructs". They are not. PHP calls them "super globals". These are global variables mapped from the GET/POST/Cookie client headers into the server environment by the PHP SAPI, for instance the Apache SAPI. PHP has many SAPIs, including a command line one, which doesn't populate these globals for obvious reasons. Oh and FastCGI for PHP is provided by a SAPI as well (nothing to do with the standard library).
Oh and quickly - "I was comparing PHP's standard library features with those of Django." Can I pick a PHP framework of choice and start comparing it to Python?
So why PHP to Django? How would the Python crowd feel if it was the other way around, for instance: Python to Codeigniter.
I forget who I learned this trick from :(
Edit: I might add, at half the price I'd buy the advertised book in this article as presents for a couple of friends. I just don't have the language talent to write well myself.
PHP to Django sounds like an awesome idea. I'd say Django deployment best practices sounds more like a chapter in PHP to Django.