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 | tim.golden |
|---|---|
| Recipients | amaury.forgeotdarc, eric.araujo, georg.brandl, markm, ocean-city, terry.reedy, tim.golden |
| Date | 2013年07月31日.15:09:34 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1375283374.61.0.555218608252.issue3099@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
This one seems to have been fixed by the importlib rebuild. I haven't bothered to trace the code path, but certainly "import nul" returns the expected "ImportError: No module named 'nul'" in both Debug & Release builds. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013年07月31日 15:09:34 | tim.golden | set | recipients: + tim.golden, georg.brandl, terry.reedy, amaury.forgeotdarc, ocean-city, eric.araujo, markm |
| 2013年07月31日 15:09:34 | tim.golden | set | messageid: <1375283374.61.0.555218608252.issue3099@psf.upfronthosting.co.za> |
| 2013年07月31日 15:09:34 | tim.golden | link | issue3099 messages |
| 2013年07月31日 15:09:34 | tim.golden | create | |