Hirokazu Yamamoto [EMAIL PROTECTED] added the comment:
GetFileAttributes() succeeds for nul, but GetFileAttributesEx() fails.
Maybe is it good idea to use GetFileAttributesEx()?
# test code
import ctypes
import ctypes.wintypes as type
dll = ctypes.windll.kernel32
print
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
I reproduced the problem on windows, and it is indeed a problem with the
print statement, when the write() method reassigns sys.stdout: the
code calls PyFile_WriteString(), then PyFile_SoftSpace on the same
object, which has been freed in
New submission from Chris Withers [EMAIL PROTECTED]:
The following demonstrates the problem:
from datetime import datetime,timedelta
datetime.now().date()+timedelta(hours=1)
datetime.date(2008, 7, 1)
I'd expect the above to either result in a TypeError or (preferably)
datetime.datetime(2008,
New submission from Chris Withers [EMAIL PROTECTED]:
from datetime import time
time(9,0)-time(8,0)
Traceback (most recent call last):
File stdin, line 1, in module
TypeError: unsupported operand type(s) for -: 'datetime.time' and
'datetime.time'
I'd expect a datetime.timedelta(0,3600)
Changes by Benjamin Peterson [EMAIL PROTECTED]:
--
type: - feature request
versions: +Python 2.7 -Python 2.4, Python 2.5
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3250
___
Tim Peters [EMAIL PROTECTED] added the comment:
This isn't a bug, since it's functioning as documented and designed.
Read note 1 in the date Objects section of the reference manual,
explaining the meaning of date2 = date1 + timedelta:
date2 is moved forward in time if timedelta.days 0, or
Changes by Benjamin Peterson [EMAIL PROTECTED]:
--
resolution: - invalid
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3249
___
New submission from Mark Summerfield [EMAIL PROTECTED]:
I know it is almost certainly too late, but I think a lot of people will
be confused by str.decode() and bytes.encode() (or was that the other
way around)?
Calling the methods str.tobytes() and bytes.tostr() (or nicer,
str.to_bytes() and
Changes by Mark Summerfield [EMAIL PROTECTED]:
--
type: - behavior
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3000
___
___
Python-bugs-list mailing
Benjamin Peterson [EMAIL PROTECTED] added the comment:
-1
encoding and decoding is generally accepted terminology. Besides then we
would be binding ourselves to returning bytes or a str; that's not
necessarily guaranteed.
Anyway, I think this hardly has a chance in the place we are (between
Brodie Rao [EMAIL PROTECTED] added the comment:
Thanks. The patch fixes the crash for me on Python 2.5.2 and 2.6b1 on OS X
and Python 2.4.5 on Debian and Ubuntu.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3242
Collin Winter [EMAIL PROTECTED] added the comment:
The change to pytree.py doesn't add much speed benefit over the
fix_imports.py change, and causes a test to fail.
The fix_imports.py change, on the other hand, takes the test suite run
time from 8m31s down to 1m45s -- this needs to go in!
That
Marc-Andre Lemburg [EMAIL PROTECTED] added the comment:
There's nothing new to .encode() and .decode(). They have existed since
Python 1.6.
--
nosy: +lemburg
resolution: - wont fix
status: open - closed
___
Python tracker [EMAIL PROTECTED]
New submission from grissiom [EMAIL PROTECTED]:
Build the environment in a fat32 file system:
$echo test test_move
$mkdir testmove
If I shutil.move('test_move', 'testmove'), it will raise:
Traceback (most recent call last):
File testmove.py, line 5, in module
shutil.move('test_move',
Georgij Kondratjev [EMAIL PROTECTED] added the comment:
import curses.ascii as curses_ascii
If you like curses_ascii you would probably like curses.ascii :) so here
is the patch. I tested it with module built-in testing facility (if
__name__ == '__main__') but didn't run other tests.
Patch
Nick Edds [EMAIL PROTECTED] added the comment:
Here is a diff for the both the fix_imports changes which I corrected,
and the pytree changes. The pytree changes were a lot more significant
before the fix_imports change, but I think they are still a decent
improvement. I think I have now restored
Benjamin Peterson [EMAIL PROTECTED] added the comment:
Ok. I tried to get it working in r64618.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3174
___
___
Georg Brandl [EMAIL PROTECTED] added the comment:
Fixed docs in r64619.
--
resolution: - fixed
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2683
___
Rafael Zanella [EMAIL PROTECTED] added the comment:
_communicate still encodes the string under the hood
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2683
___
Benjamin Peterson [EMAIL PROTECTED] added the comment:
Done for 2.6 in r64622. (Georg reviewed.)
--
resolution: - fixed
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3219
Changes by Benjamin Peterson [EMAIL PROTECTED]:
--
resolution: - fixed
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3174
___
Georg Brandl [EMAIL PROTECTED] added the comment:
You're right, I fixed that too in r64621.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2683
___
___
Georg Brandl [EMAIL PROTECTED] added the comment:
Lib Ref/Built-in Types/Sequence Types/Bytes and Byte Array Methods
The following set/frozenset and dict sections repeat (and for dicts,
expands upon) the constructor interface from the Built-in Functions
section. The sequence type
Georg Brandl [EMAIL PROTECTED] added the comment:
Fixed with r64629.
--
resolution: - fixed
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3217
___
Georg Brandl [EMAIL PROTECTED] added the comment:
Well, that wouldn't be different if you had set the locale in your
prompt. In short, ``u'a' in string.letters`` can never work with any
string.letters except the default, English-only one, and therefore is wrong.
Georg Brandl [EMAIL PROTECTED] added the comment:
This is already on my to-do list. Thanks for raising it as an issue
though, I won't forget it so easily this way :)
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3203
Mark Dickinson [EMAIL PROTECTED] added the comment:
Well, I can't find anything more to fuss about here. :-)
Reclosing.
--
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1682
Georg Brandl [EMAIL PROTECTED] added the comment:
Fixed in r64634.
--
resolution: - fixed
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3191
___
Georg Brandl [EMAIL PROTECTED] added the comment:
Added note in r64635.
--
resolution: - fixed
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1523853
___
Georg Brandl [EMAIL PROTECTED] added the comment:
Reworded a bit and applied as r64638.
--
resolution: - fixed
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1410739
___
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
Corrected as r64633 (trunk) and r64639 (release25-maint). version 3.0 is
not affected, and there won't be any more 2.4 release.
Thanks for the report!
--
resolution: - fixed
status: open - closed
Georg Brandl [EMAIL PROTECTED] added the comment:
Thanks, fixed in r64642.
--
resolution: - fixed
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3251
___
Changes by Georg Brandl [EMAIL PROTECTED]:
--
assignee: georg.brandl -
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2351
___
___
Python-bugs-list
New submission from cvp [EMAIL PROTECTED]:
After defining my own __eq__ method for a class that judged equality
based on a 'name' variable, imagine my surprise to see this:
In [20]: my_graph.edges[-1].end == my_graph.vertices[-1]
Out [20]: True
In [21]: my_graph.edges[-1].end !=
Brett Cannon [EMAIL PROTECTED] added the comment:
And it looks like the 2.6 docs need to be updated as well.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2885
___
Benjamin Peterson [EMAIL PROTECTED] added the comment:
Sorry, this is documented [1], and it unlikely to ever be changed.
[1] http://docs.python.org/ref/customization.html
--
nosy: +benjamin.peterson
resolution: - rejected
status: open - closed
cvp [EMAIL PROTECTED] added the comment:
1) I didn't say that the option to edit __ne__ should be removed, only that
it'd be both more consistent and convenient to change the meaning to
something relative by default.
2) So long as the old code defines __ne__, which I'm guessing is the code
that
Changes by cvp [EMAIL PROTECTED]:
Removed file: http://bugs.python.org/file10792/unnamed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3254
___
___
Changes by cvp [EMAIL PROTECTED]:
Removed file: http://bugs.python.org/file10793/unnamed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3254
___
___
Changes by Senthil [EMAIL PROTECTED]:
Removed file: http://bugs.python.org/file9907/issue2275.patch
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2275
___
___
Senthil [EMAIL PROTECTED] added the comment:
Issue applicable to Py2.6 and Py3K. Previous patch attached was wrong.
Removed it.
--
versions: +Python 2.6, Python 3.0
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2275
Paddy McCarthy [EMAIL PROTECTED] added the comment:
Hi Georg,
A bit of relevant background about me:
I've been interested in Duck Typing _specifically_ for a couple of
years when I started watching edits to it on Wikipedia. I researched the
history of the use of the term and changed the
42 matches
Mail list logo