Daniel Sturm added the comment:
> In my opinion, it is a bug in Windows
I don't think calling every complicated API a "bug" is useful. Is the Win32 API
exceedingly annoying? I think everybody agrees on that, but imo it's better to
fix this once in python itself and don
Changes by Daniel Sturm :
--
components: +IO
type: -> behavior
___
Python tracker
<http://bugs.python.org/issue18199>
___
___
Python-bugs-list mailing list
Un
New submission from Daniel Sturm:
Python at the moment does not handle paths with more than MAX_PATH characters
well under Windows.
With Windows 7 x64, Python 3.3 32bit, the attached file fails with:
Traceback (most recent call last):
File ".\filename_bug.py", line 4, in
os.ma
Daniel Sturm added the comment:
TBH I saw this more as an opportunity to get used to the whole system, how to
create a patch, etc. :) Should've made it clearer at the start that this is
unlikely to ever be a problem, sorry (didn't see a way to set priority to low
myself).
If my
New submission from Daniel Sturm :
The mid index computation in _bisectmodule.c in both internal_bisect_right and
internal_bisect_left is done with:
mid = (lo + hi) / 2; // all three variables Py_ssize_t
which is susceptible to overflows for large arrays, which would lead to
undefined
