Jeff Hardy stated:.. > In addition, 3.0 will include most (but perhaps not all!) of 3.4's > features, mainly because I'd like to see a release later this year > (around October) and things like nonlocal or importlib could slip > because they're hard and not terribly exciting. Calling a release like > that 3.4 is a problem because it's really not 3.4-compatible. > > True, but calling it 3.3 would not be a problem, I think.
> Once the Python 3 features are in place, I want to make it as > cross-platform as possible - iOS, Android, Windows 8, etc. That would > strongly imply a new version number since it will require a new DLR > version to be used (not very good to slip a DLR version change into a > 3.4.z release). Hence I'd prefer to keep the ability to call it 3.1 > (or whatever) instead. > Well, speaking of cross-platform, most of my work in the near future will probably be on Mono -- so different DLRs will be kind of a normal thing. I don't have a problem with that being a factor in a point-level release -- it is an implementation detail, not a language change.
_______________________________________________ Ironpython-users mailing list Ironpython-users@python.org https://mail.python.org/mailman/listinfo/ironpython-users
