This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients
Date 2007-02-07.08:32:57
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
rhettinger: I agree with anthonybaxter; implementing this in a module to import is not possible (unless you want *another* module that works like __future__ imports, i.e. where importing it isn't just a plain import - you could then just as well require to put "this is py3k" as the first line of the file). I wish PEP 244 would have been adopted, then you could "directive python3" at the top.

As for testing: I don't see it as a problem if the test suite only works with the version where the feature is introduced. See test_future* and test_with.

As for PRINT_ITEM: it was always inlined, since day 1. It has grown since, but apparently nobody ever bothered refactoring (on day 1, it was smaller, and the bulk of it was, and still is, in writeobject aka PyFile_WriteObject)
History
Date User Action Args
2007-08-23 15:56:13adminlinkissue1633807 messages
2007-08-23 15:56:13admincreate