On Tue, Oct 27, 2009 at 9:27 PM, Mike Orr <[email protected]> wrote: > > On Tue, Oct 27, 2009 at 4:07 AM, Mario Ruggier <[email protected]> wrote: >> 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/ > > That would work in the short term, but it would suck to be limited to > a subset of Python's features, and to have 'if's all over the place.
There need only be one if block, centrally placed... all modules can import specific items from there. > In the long term it would seem even more restraining, although > presumably you could abandon the policy in a year or two. Well, yes, that's the price to pay for having a unique code base (and dist package). In any case, you would still gain on other py3 features, like performance, when running under py3. But, name me *one* py3 feature for which a legacy package *must* have ?!? >> 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! > > MikeB is not a framework developer. He's a database guy who has also > written a remarkable template engine, Hey, so did I ;-) Really, nothing to take away from Mike or anyone else, as I said it is a judgement call of how the WSGI api boundaries were drawn... as you explain very nicely, the issue is not because of a technical limitation. But, and that was my point, an issue there is, be it directly cause of WSGI or not, and every WSGI stack has to deal with it. m. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
