Re: Jython 2.7.0 final released!

On Fri, May 8, 2015 at 5:04 PM, Stefan Richthofer
<[email protected]> wrote:
>> This would take much more than a conditional grammar, we'd have to
>> somehow keep two runtimes around and be able to mix them. We'd need
>> things like sometimes old style classes are permitted, sometimes not
>
> Hmmm I am honestly not 100% aware of all differences between Python 2 and 3
> to consider, so please apoligize if my thoughts are too naive.
> Rather than two runtimes I imagine kind of one runtime that is the
> "Least common multiple" of Python 2 and 3. (Jython already delivers a runtime
> that is kind of "Least common multiple" of Python 2 and Java; extending
> this to Python 3 sounds almost simple compared to what has already been achieved)
> E.g. for the old- vs new-style classes concern:
> Python 2.7 already _has_ this mix of old- and new style classes and deciding
> whether to permit old ones would be trivial due to a different import-directive.
>
> However, if you say it can't be done (with reasonable effort), I trust you and
> won't discuss further. I just wanted to make sure, the idea was considered.
I do think it would be hard, but I wouldn't stop anyone from trying :)

I think the hardest part would be keeping your head straight with
simultaneous 2 and 3 behaviors - the trouble I see is that in too many
respects 2 and 3 are too similar. I suspect the tiny differences would
hurt the most. If you've ever tried switching back and forth between
Python 2.5 and Python 2.7 - even those little differences can be
*maddening* :)

-Frank

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y