* Once you know PHP, it's really fast to get shit done. Can't deny that.
* After staying with one language for so many years, it's crucial to try something new. You might not like it, but there might be some parts that could inspire you. It's really toxic to be stuck in one mindset for a very long time.
* Anecdotal, but I found an average Python dev to be better than average PHP dev (oh god, all those custom PHP frameworks I had to maintain and rescue projects from death).
* Python has great libraries for statistics, machine learning, image processing, etc - it's very universal.
* There is loads of great info about Python on the Internet and transition should be smooth once you get used to not putting semicolon ;)
* I found that there are more better paying jobs in Python.
All in all, why not to try?
But over the years I've also inherited some absolutely abhorrent PHP nightmare projects, whose design/coding decisions truly boggle the imagination. Often based on no framework at all, and apparently motivated largely by the developer's desire to use as many PHP and SQL features as possible in the same project.
Latterly I've been using python for some web projects. I played briefly with django, but I've found myself settling on Flask [2], a very nice "microframework" which is super easy to get running with, and which gives a great balance between power and stay-out-of-my-way-ness. It has a simple URL routing system based on function decorators and regex, the ability to factor your apps into reusable components based around your python modules, jinja2 templates, etc. I use sqlalchemy for db access.
Honestly I find it much more of a pleasure to be coding python/flask vs PHP/codeigniter, but due to team and project constraints it isn't always possible to go that way.
http://jugad2.blogspot.in/2015/01/publish-databases-to-pdf-w...
PyDAL is now a separate project and can be used without web2py.
Python isn't the fastest dog out there, but doesn't fare so badly with the abstractions, and its OO style suits a dynamic language better. It doesn't try to be a Java.
Neither language will give you much protection against programming errors, nor optimize your code very well like many of the new hip languages (Rust, Go, Nim) do.
That said most of the stuff I write myself lately is in Python.
I don't know that I've ever heard anyone say that they prefer PHP over Python, so I doubt you'll get that response on here.
I'm honestly not a huge fan of either. Are you deciding whether to learn Python? What you want to use going forward?
Honestly having 10+ years of PHP experience probably makes it a hands-down winner (for you personally) in terms of productivity. It'd be a while before you'd see any real productivity gains from Python.
That said, there are maintainability considerations for each language, and Python wins in some of those categories.
I hear it all the time. Primarily by polyglots who are interested in prototyping things. I use both, I prefer PHP and I'm increasingly aware that people aren't learning PHP rather than watching it evolve past Python.
Taylor has done a great job on it.
And then of course it's the spacing issues which is hard to understand at first glance