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 steve.dower
Recipients Arfrever, barry, brett.cannon, eric.snow, lemburg, ncoghlan, ned.deily, pitrou, steve.dower, tim.golden, vstinner, zach.ware
Date 2014-12-02.18:40:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1417545657.4.0.177414865595.issue22980@psf.upfronthosting.co.za>
In-reply-to
Content
I was more interested in source file resolution than bytecode caching. If Python 3.5 would prefer "spam.cpython-35.py" or "spam.cpython-3.py" over "spam.py" and Python 2 preferred "spam.py", then I can more easily separate the code that won't parse in the alternative.

Happy to be told it's unrelated and I should raise it separately, but from my POV resolving .pyd filenames looks very similar to resolving .py files.
History
Date User Action Args
2014-12-02 18:40:57steve.dowersetrecipients: + steve.dower, lemburg, barry, brett.cannon, ncoghlan, pitrou, vstinner, tim.golden, ned.deily, Arfrever, eric.snow, zach.ware
2014-12-02 18:40:57steve.dowersetmessageid: <1417545657.4.0.177414865595.issue22980@psf.upfronthosting.co.za>
2014-12-02 18:40:57steve.dowerlinkissue22980 messages
2014-12-02 18:40:57steve.dowercreate