Martin v. Löwis added the comment:
I think it's incorrect: asynchat operates on bytes, not strings, as it
directly interfaces with the socket, and no encoding is specified for
the protocol.
So, IMO, callers should be expected to pass bytes only, as terminator
and as data.
--
nosy:
New submission from Talin:
This patch contains documentation updates for the Python Library Reference
pertaining to PEP 3101 Advanced String Formatting.
--
components: Documentation
files: docupdates.diff
messages: 55526
nosy: talin
severity: normal
status: open
title: Documentation
New submission from Georg Brandl:
With attached file (which contains a single latin-1 instead of utf-8
encoded character), Python prints SyntaxError: None instead of a more
helpful analysis of the problem.
--
assignee: loewis
files: x.py
keywords: py3k
messages: 55527
nosy:
New submission from Georg Brandl:
When showing a name in a NameError, the encoding is messed up.
(File y.py, encoded in UTF-8, contains only only the line shown in the
traceback; the terminal encoding is set to UTF-8.)
$ python3k y.py
Traceback (most recent call last):
File y.py, line 1, in
Georg Brandl added the comment:
Thanks! Committed as part of rev. 57829.
--
assignee: - georg.brandl
nosy: +georg.brandl
resolution: - accepted
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1068
New submission from Georg Brandl:
While it's documented that unicode.translate()s table maps ordinals to
strings/ordinals/None, if you give a unicode key in the table it will
just be ignored. This is quite surprising.
--
assignee: lemburg
components: Unicode
messages: 55530
nosy:
Martin v. Löwis added the comment:
This is now fixed in r57838.
--
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1069
__
___
Thomas Wouters added the comment:
I agree, but the change wasn't actually mine. I merely adjusted the
already-implemented strategy to the fact that bytes(str) no longer
works. I think the original change was Jeremy H's.
__
Tracker [EMAIL PROTECTED]
Martin v. Löwis added the comment:
This is now fixed in r57837
--
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1070
__
___
New submission from Aki:
Hi,
I'm not sure this is a right place to write in the problem I found.
What I found was:
(1) create a thread
(2) open a file in the thread
(3) everything works fine under Solaris
(4) Openning a file in the thread fails intermittenly under Windows
Not always it fails.
Bill Janssen added the comment:
I agree. It shouldn't be an absolute size, and it is too small.
--
nosy: +janssen
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1072
__
New submission from Koen van de Sande:
The python3.0-config script, installed into the py3k bin folder, does
not run on Python 3.0a1, because of the syntax change in the print
statement. Possibly there are other compatibility issues.
--
components: None
messages: 55538
nosy: koen
New submission from Amaury Forgeot d'Arc:
os.stat(nonexistent) raises a UnicodeDecodeError on German, Polish and
French Windowses.
The reason: Windows returns an error message which contains accented
letters encoded as MBCS, but python decodes it with utf-8.
This patch uses the Unicode version
Martin v. Löwis added the comment:
While I agree with the principle (use wide APIs where possible), I'd
like to point out that they don't work on Windows 95 (at least some
don't; if you link with MSLU, you get some more to work); that was the
major reason not to use them in the past. This is no
Martin v. Löwis added the comment:
I don't see the problem. When open() reports that the file does not
exist, the most likely reason is that it really does not exist. Perhaps
it has not been created, yet, and you need to wait until it has been
created before you can open it?
--
nosy:
Aki added the comment:
I know it is hard to believe.
I spent days to try out many things.
For example, I added the following:
try:
print os.path.isfile(fn) ---
fd = open(fn, 'rb')
crypted = fd.read()
fd.close()
Changes by Matthew Russell:
--
components: Interpreter Core, Library (Lib)
files: py3k_bug1.txt
severity: urgent
status: open
title: itertools missing, causes interactive help to break
type: behavior
versions: Python 3.0
__
Tracker [EMAIL PROTECTED]
Aki added the comment:
Sorry to disappoint you but ...
(1) Does the file exist before program is started, and remains after
program finishes?
Yes and Yes
(2) Do you change the current directory (with os.chdir or similar)?
No. The file is in the current directory where the program was invoked.
New submission from jinok:
Mac/scripts/cachersrc.py contains tuple unpacking in handler function
args definition, causing make frameworkinstall to complain and exit
early.
--
components: Macintosh
messages: 55546
nosy: jinok
severity: normal
status: open
title: cachersrc.py using tuple
Gabriel Genellina added the comment:
I've narrowed the problem to the usage of generator expressions.
Generator expressions appear to be MUCH slower on 2.5 than on 2.4.
python -m timeit tuple([1 for _ in xrange(3)])
2.4 - 2.23us
2.5 - 2.31us (a bit slower, but not so much)
python -m timeit
Guido van Rossum added the comment:
(Reopening given recent discussion.)
--
resolution: fixed -
status: closed - open
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1067
__
Gabriel Genellina added the comment:
I think the 2.4 version is in maintenance mode, so no new features are
added.
You may target 2.5 or 2.6. But the patch is incorrect: the base64 name
is undefined. You should include test cases and documentation changes
also; please read
Martin v. Löwis added the comment:
I'm closing this as works for me now. It cannot possibly be a bug in
Python, since the error was created by the operating system; Python does
not make it up randomly. I also doubt that the operating system will
arbitrarily report that a file is not present if
23 matches
Mail list logo