Message339582
| Author | jesse.farnham |
|---|---|
| Recipients | jesse.farnham, rhubarbdog x, steven.daprano, xtreak |
| Date | 2019-04-07.19:04:59 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1554663899.51.0.829634415325.issue36259@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
Upon further digging, the filename to search for ultimately comes from the PyCodeObject where the error occurred. So a possible solution could be to populate the PyCodeObject with the absolute path to the file when it’s first created in compilation. Then no searching is needed and the problem doesn’t happen. This seems like a potentially very invasive change, though. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-04-07 19:04:59 | jesse.farnham | set | recipients: + jesse.farnham, steven.daprano, xtreak, rhubarbdog x |
| 2019-04-07 19:04:59 | jesse.farnham | set | messageid: <1554663899.51.0.829634415325.issue36259@roundup.psfhosted.org> |
| 2019-04-07 19:04:59 | jesse.farnham | link | issue36259 messages |
| 2019-04-07 19:04:59 | jesse.farnham | create | |