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 eli.bendersky
Recipients benjamin.peterson, brett.cannon, eli.bendersky, eric.snow, larry, ncoghlan, rhettinger, serhiy.storchaka, skrah, techtonik
Date 2014-04-04.15:30:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAF-Rda91w-aHGn2WZECqHW_RcBHE_u6L+cnTJZfX4hqAC0edMQ@mail.gmail.com>
In-reply-to <1396617012.78.0.171940980086.issue19655@psf.upfronthosting.co.za>
Content
On Fri, Apr 4, 2014 at 6:10 AM, Serhiy Storchaka <report@bugs.python.org>wrote:

>
> Serhiy Storchaka added the comment:
>
> Now make fails when system Python is older than 3.4.
>
>
This is why the .h & .c files are checked in - someone just building Python
doesn't need them regenerated at all. Only if one wants to *modify the
AST*, he'll need an up-to-date Python. Otherwise we'll have to stick to the
"oldest Python possible" for every script we use internally. I think this
was discussed on the mailing list(s) at some point.
History
Date User Action Args
2014-04-04 15:30:41eli.benderskysetrecipients: + eli.bendersky, brett.cannon, rhettinger, ncoghlan, larry, techtonik, benjamin.peterson, skrah, eric.snow, serhiy.storchaka
2014-04-04 15:30:41eli.benderskylinkissue19655 messages
2014-04-04 15:30:40eli.benderskycreate