Author steve.dower
Recipients paul.moore, steve.dower, tds333, tim.golden, zach.ware
Date 2016-09-15.15:21:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
On issue28137 I agreed with the proposal to rename to EXENAME.pth, but rather than supporting all of .pth file's syntax we would abort the process on anything we don't like.

Specifically, we'd allow relative paths, absolute paths, blank lines, comments, and "import site". (The parsing code is written in C and runs before initialization, so we can't exec stuff anyway, but if I had my way I'd ban that from .pth files everywhere.)

Supporting this on other platforms requires porting the code to Python/getpath.c. I took a quick survey of core devs at the sprints and nobody seemed desperate to have it, but it's something that we can add at any time since it is tied to build/install (rather than anything you'd write in Python code).
Date User Action Args
2016-09-15 15:21:55steve.dowersetrecipients: + steve.dower, paul.moore, tds333, tim.golden, zach.ware
2016-09-15 15:21:55steve.dowersetmessageid: <>
2016-09-15 15:21:55steve.dowerlinkissue28138 messages
2016-09-15 15:21:55steve.dowercreate