On Thu, Feb 28, 2013 at 1:37 PM, Barry Warsaw <ba...@python.org> wrote: > On Feb 27, 2013, at 11:33 AM, fwierzbi...@gmail.com wrote: >>The easy part for Jython is pushing some of our "if is_jython:" stuff >>into the appropriate spots in CPython's Lib/. > > I wonder if there isn't a better way to do this than sprinkling is_jython, > is_pypy, is_ironpython, is_thenextbigthing all over the code base. I have no > bright ideas here, but it seems like a feature matrix would be a better way to > go than something that assumes a particular Python implementation has a > particular feature set (which may change in the future).
Yes, avoiding that kind of thing is a key motivation for sys.implementation. Any proposal for "is_jython" blocks should instead be reformulated as a proposal for new sys.implementation attributes. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
