Isaac Morland added the comment:
I would suggest that the need to create directories that may already
exist (really ensure existence of directories) is not exclusive to
trace.py. I am suggesting this be added as an option to os.mkdir and
os.makedirs. See Issue 1675.
--
nosy: +ijmorlan
Guido van Rossum added the comment:
I think we can fix this as follows: whenever it calls os.mkdir() and an
error is returned, check if that is EISDIR or EEXISTS, and if so, check
that indeed it now exists as a directory, and then ignore the error.
Moreover, I'd like to do this for the ultimate
Changes by Isaac Morland:
Added file: http://bugs.python.org/file9016/makedirs.py
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1675
__
___
Python-bugs-list mailing list
Guido van Rossum added the comment:
Can you rephrase this as svn diff output?
Also, mkdir() is a confusing name for the helper -- I'd call it
forgiving_mkdir() or something like that.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1675
Isaac Morland added the comment:
Yes, I'm really combining two things here - the race condition, which I
argue is a (minor) bug, and a feature request to be able to ensure
exists a directory.
I have not produced a proper Python patch before and I have other things
to do so this will take longer
Martin v. Löwis added the comment:
print .encode(iso-8859-9).upper().decode(iso-8859-9)
does not
Please get your types right. is a byte string (in Python 2.x).
encode: unicode - string
decode: string - unicode
That you still can apply .encode to the byte string is a bug/pit fall in
Ismail Donmez added the comment:
Tried like ,
unicode(iii).encode(iso-8859-9).upper()
doesn't work, I'll ask on python users list. Thanks.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1609
__
Martin v. Löwis added the comment:
As of r59585, _PyLong_FitsInLong() is no longer.
--
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1666
__
New submission from Kevin Walzer:
I've just updated to Tk 8.5 on OS X (Leopard, 10.5.1) and have rebuilt
Python to link to the new version of Tk. I'm seeing tons of weird error
messages in my logs when I run IDLE:
12/20/07 8:18:46 PM [0x0-0xa50a5].org.python.IDLE[1300] Break on
New submission from Isaul Vargas:
When running Python 2.5.1 stable in Windows, you can press Ctrl-C as
many times as you want and it will always output Keyboard Interrupt in
the interpreter.
Python 3.0a+ will quit if you press ctrl-c too many times. The last
release of 3.0a2 can handle many
Changes by Martin v. Löwis:
--
status: pending - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1673
__
___
Python-bugs-list mailing list
Unsubscribe:
Martin v. Löwis added the comment:
I would expect that this is a Tk bug, primarily, not a Python bug. If
somebody could reproduce it with Tk alone, it would be good to report it
at http://sourceforge.net/tracker/?group_id=12997
--
nosy: +loewis
__
201 - 212 of 212 matches
Mail list logo