Message262472
| Author | vstinner |
|---|---|
| Recipients | Arfrever, berker.peksag, brett.cannon, eric.snow, python-dev, r.david.murray, serhiy.storchaka, vstinner |
| Date | 2016-03-26.00:06:24 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1458950784.8.0.693905890727.issue20021@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> Or does it matter to be able to use an external python program? Oh wait, I misunderstood how the script is used. I understood that the script must be run manually only when a new opcode is added and so is rarely used and only used with the built Python program. In fact, the script is part of the build process! I completely missed that, sorry. I searched how it was used but I missed the build process. So yes, it matters to support Python 2 and Python 3 in Python/makeopcodetargets.py. I pushed Serhiy's patch issue20021_2.diff. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2016-03-26 00:06:24 | vstinner | set | recipients: + vstinner, brett.cannon, Arfrever, r.david.murray, python-dev, eric.snow, berker.peksag, serhiy.storchaka |
| 2016-03-26 00:06:24 | vstinner | set | messageid: <1458950784.8.0.693905890727.issue20021@psf.upfronthosting.co.za> |
| 2016-03-26 00:06:24 | vstinner | link | issue20021 messages |
| 2016-03-26 00:06:24 | vstinner | create | |