On Mon, Oct 26, 2009 at 7:09 PM, Mike Orr <[email protected]> wrote: > > I also haven't seen any guidance on how to manage two related > codebases in the same repository or in the same PyPI entry. It's > great if the 2to3 tool fixes everything, but if you have to hand-patch > things then you have to put the code for that somewhere. And while > binary eggs are specific to a Python version, source tarballs are not.
No-one seems to give any consideration to the very real possibility of adjusting the *same* code base to run on both py 2 *and* 3 -- the same tarball, the same setup.py. A recipe (and real world examples, one of which is a web fraemwork) for how this may be done is here: http://mail.mems-exchange.org/durusmail/qp/441/ This may certainly not be appropriate for some projects (and certainly not recommendable to python newbees, absolutely go with 2.6!). The mention of wsgi/py3/unicode issues in this thread reminded me of an similar earlier exchange on this same group (some 10 months ago in Jan)... where in one of the replies Micheal Bayer had said '''There are no "unicode" issues in WSGI''': http://groups.google.com/group/pylons-discuss/browse_thread/thread/7840c48a1b14c5aa/9bb0444c8dd4611b?#9bb0444c8dd4611b I guess it boils down to where does WSGI (should) end and where the rest of the stack (should) start... plenty room for opinion! mario --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
