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.

classification
Title: Unhelpful diagnostic 'cannot find the path specified'
Type: behavior Stage: resolved
Components: Library (Lib) Versions: Python 2.6
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: Nosy List: eric.araujo, eric.smith, raph@mankin.org.uk, tim.golden
Priority: normal Keywords:

Created on 2010-11-18 12:30 by raph@mankin.org.uk, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (4)
msg121453 - (view) Author: Raphael Mankin (raph@mankin.org.uk) Date: 2010-11-18 12:30
Something somewhere in the library issues the diagnostic 'The system cannot find the path specified' with no indication of what path it was looking for nor where the error was detected.

The relevant routine needs modification to print at least the path and preferably also a back-trace.
msg121455 - (view) Author: Eric V. Smith (eric.smith) * (Python committer) Date: 2010-11-18 13:31
What code were you executing when this message was printed? What platform are you running on? What's the exact version of Python this happens with? (If you're running 2.6.x, what's "x" equal to?)
msg121456 - (view) Author: Eric V. Smith (eric.smith) * (Python committer) Date: 2010-11-18 14:18
I ask about the specific version and platform because the string "cannot find the path specified" doesn't appear anywhere in release26-maint. And indeed "cannot find the" doesn't appear anywhere except comments. I'm going to close this issue, assuming it's a problem in something other than the standard library. If you have a repeatable case, please let us know and reopen the issue (or I can reopen it for you).
msg121459 - (view) Author: Tim Golden (tim.golden) * (Python committer) Date: 2010-11-18 15:05
It's almost certainly coming straight back from the O/S,
where Python is doing its usual thing of channelling
an O/S error directly. Obviously we could special-case
this or any other specific error; but we usually don't
History
Date User Action Args
2022-04-11 14:57:09adminsetgithub: 54661
2010-11-18 15:05:39tim.goldensetnosy: + tim.golden
messages: + msg121459
2010-11-18 14:18:15eric.smithsetstatus: open -> closed
type: behavior
messages: + msg121456

resolution: not a bug
stage: resolved
2010-11-18 13:38:29eric.araujosetnosy: + eric.araujo
2010-11-18 13:31:09eric.smithsetnosy: + eric.smith
messages: + msg121455
2010-11-18 12:30:11raph@mankin.org.ukcreate