Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Worth mentioning unittest2? #40
Hey, just started scanning through the guide!
In the testing section, http://docs.python-guide.org/en/latest/writing/tests/#unittest2 covers the backport of unittest2 for Python 2.6.
As this is an "opinionated" guide and I'm assuming focused on current Python 2.7, is it worth mentioning backwards compatibility at this point?
Alternatively, since I would think backwards compatibly is a more advanced topic, perhaps it's worth pulling into a new section, that tox can link to?
This comment has been minimized.
This comment has been minimized.Show comment Hide comment
App Engine dev chiming in here. 2.5 suport is still pretty crucial within the niche of the App Engine community. While it's true that 2.7 is now supported, the transition is not necessarily a gentle one.
I suspect that it will be a little while yet before 2.7 is the dominant Python verison for App Engine.
I'm not sure that's fair. I really with it was, as I agree with the sentiment a lot.
To give you an idea, support for 2.7 happened mere months ago. It has, in fact, taken the App Engine team this long to catch up (Yes, from before f!*#$ing YouTube, even. I wish I knew what they were doing in that span of time... SSL support is another one of these).
Among the quirks are weird performance characteristics you'd never guess would come up until you start profiling. Datastore queries are impacted by the pure Python Protocol Buffer parser implementation, for example. The time to fetch a Datastore instance inceases linearly with respect to the number of properties, so it looks like there's a constant overhead to parse an entity.