Changes by Martin v. Löwis:
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1029
__
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python
Martin v. Löwis added the comment:
It had indeed the status Fixed/Open on SF. It was marked as Fixed and
Closed by rhettinger, then reopened by rhettinger in response to my
comment in msg53513.
It does not refer to _bsddb.c, but bsddbmodule.c. Are you saying that
bsddbmodule.c supports __iter__
Changes by Martin v. Löwis:
--
priority: immediate - normal
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1542308
_
___
Python-bugs-list mailing list
Martin v. Löwis added the comment:
It should not be possible to trigger Py_FatalError through pure Python
code. I still haven't tried reproducing the problem, but if it is
reproducable, it's a bug.
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue837234
Martin v. Löwis added the comment:
Yes, nobody seems to be interested in fixing it.
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue877124
___
Python-bugs-list mailing
New submission from Martin v. Löwis:
In r57374, the ParseTuple string for datetime_strptime was changed from
ss:datetime to uu:datetime, without adjusting the output arguments. It's
not clear to me what the rationale of this change was; it is incorrect
as u outputs Py_UNICODE, not char
Changes by Martin v. Löwis:
--
nosy: +gvanrossum
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1055
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
nosy: -gvanrossum
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1055
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Martin v. Löwis added the comment:
I think it is neither possible nor good to produce a uniform result.
Python traditionally exposes APIs as-is, providing the system actually
has an API with the same name. It never tries to hide differing system
behaviors in the Python wrapper; if systems vary
Changes by Martin v. Löwis:
--
priority: - normal
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1055
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
assignee: - loewis
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1040
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Martin v. Löwis added the comment:
This is now fixed in r57720.
Using wide APIs would be possible through GetTimeZoneInformation,
however, then TZ won't be supported anymore (unless the CRT code to
parse TZ is duplicated).
--
nosy: +loewis
resolution: - fixed
status: open - closed
Martin v. Löwis added the comment:
I now see the problem. What you want to do cannot possibly work.
You are trying to create a string object that is larger than 2GB; this
is not possible on a 32-bit system (which I assume you are using). No
matter how you modify the read() function, it would
Changes by Martin v. Löwis:
--
resolution: - accepted
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1039
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
versions: +Python 3.0 -Python 2.6
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1675334
_
___
Python-bugs-list mailing list
Changes by Martin v. Löwis:
--
versions: +Python 3.0
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1001
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
versions: +Python 3.0
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1463370
_
___
Python-bugs-list mailing list
Unsubscribe
Martin v. Löwis added the comment:
The patch looks fine to me, please apply.
--
assignee: loewis - georg.brandl
resolution: - accepted
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1753395
Martin v. Löwis added the comment:
I have now fixed it in 57750, 57751, 57754. I leave the bug open until I
can actually test it.
--
resolution: - fixed
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1746880
Martin v. Löwis added the comment:
Given that the underlying platform has no support for that, it will be
difficult to implement correctly across all systems.
--
nosy: +loewis
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1062
Martin v. Löwis added the comment:
I agree with cartman: Python behaves as designed in all cases discussed
here. Closing this report as invalid.
--
nosy: +loewis
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1528802
Martin v. Löwis added the comment:
Thanks for the patch. Committed as r57759 and r57760. I added it to the
trunk as well, as it might be possible that the test is run on FAT even
if the operating system is Windows XP.
--
nosy: +loewis
resolution: - accepted
status: open - closed
Martin v. Löwis added the comment:
The fatal error is raised if the stack overflows in the process of
handling RuntimeError. In certain cases, the C algorithms won't bail out
if a RuntimeError is raised, and just catch it. If that then causes
another stack overflow, Python gives up. One
New submission from Martin v. Löwis:
Let's see who gets this
--
assignee: georg.brandl
messages: 55508
nosy: georg.brandl, loewis
severity: normal
status: open
title: Test issue
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1064
Changes by Martin v. Löwis:
--
resolution: - invalid
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1064
__
___
Python-bugs-list mailing list
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
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
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
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
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
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
Martin v. Löwis added the comment:
It definitely sounds like a compiler bug. Unless you can provide further
details to the specific error in the C code of Python, it's likely that
we can do little about it.
If you want to analyze this further, here is a number of things you can try:
- compile
Martin v. Löwis added the comment:
This is a duplicate of #1078.
--
nosy: +loewis
resolution: - duplicate
status: open - closed
superseder: - cachersrc.py using tuple unpacking args
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1085
Martin v. Löwis added the comment:
If you are curious, we could now try to find out what precisely goes
wrong. The procedure would be this
* after each step, check whether the problem still occurs
a) resolve the includes manually, then strip everything that isn't
needed. This could start
Martin v. Löwis added the comment:
Mark Hammond has now confirmed it worked for 3.0a1, so closing it.
--
status: open - closed
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1746880
Martin v. Löwis added the comment:
I don't understand the problem. What Solaris version are you using?
Why do you want to remove _XOPEN_SOURCE? Solaris considers this as a
request for XPG 4.2 only _XOPEN_SOURCE_EXTENDED is defined, which it
shouldn't be on Solaris 10
Martin v. Löwis added the comment:
A 2.5 patch would not be accepted; there won't be any new features
for 2.5 , and new port would be a new feature.
Procedurally, are you willing to support a QNX port for the coming years
(say, 5 years)? Otherwise, there is little point in accepting
Martin v. Löwis added the comment:
Closing because of lack of feedback. (it may be that I got feedback in
private mail off-tracker; I don't remember).
--
resolution: - works for me
status: open - closed
_
Tracker [EMAIL PROTECTED]
http
Changes by Martin v. Löwis:
--
severity: normal - minor
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1654408
_
___
Python-bugs-list mailing list
Unsubscribe
Martin v. Löwis added the comment:
The source of make_type is in Parser/asdl_c.py.
--
nosy: +loewis
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1752184
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1087
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1006
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1007
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1012
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1015
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1016
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1017
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1023
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1029
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1030
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1000
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1002
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1004
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1005
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1019
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1022
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1026
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1027
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1032
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1034
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1043
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1047
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1061
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1071
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1075
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1076
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Martin v. Löwis added the comment:
I don't think recoding the message is the right thing to do. Instead,
the email package should be fixed to not treat the bytes before the
first part of a multipart message as text, or else assume that it is
Latin-1 encoded (it's certainly not *meant* to be text
Martin v. Löwis added the comment:
Thanks for the report. This is now fixed.
--
nosy: +loewis
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1088
Martin v. Löwis added the comment:
-1. I doubt this is needed often enough to justify a builtin function.
--
nosy: +loewis
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1093
Martin v. Löwis added the comment:
I could not quite reproduce this on the German version (the error text
reads Das System kann die angegebene Datei nicht finden on XP),
however, the patch looks good and it fixes the same problem for the
registry functions (where I get Das Handle ist ungültig
Martin v. Löwis added the comment:
Thanks for the patch. Committed as r57928
--
resolution: - accepted
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1076
New submission from Martin v. Löwis:
Yes.
--
nosy: +loewis
resolution: - wont fix
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1089
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1094
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Martin v. Löwis added the comment:
There definitely won't be any new features in 2.5.x. However, I think
Bill said he might make this available separately.
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1114345
Martin v. Löwis added the comment:
I'm not sure like the naming of the format. mixed-endian could mean
anything. I doubt IEEE specifies this as a possible byte representation
(but then, I'm uncertain whether IEEE specifies big-endian and
little-endian, either).
One option would be to call
Martin v. Löwis added the comment:
Thanks for the report. This is now fixed in r57947
--
nosy: +loewis
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1097
Martin v. Löwis added the comment:
Thanks for the report. This is now fixed in r57957 (although I tested it
only on Unix).
--
nosy: +loewis
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1100
Martin v. Löwis added the comment:
The first issue (non-ASCII characters won't work in interactive mode)
was reported as issue 1100 also, and is now fixed in r57957.
As for the other issues, I'm not quite sure what to make out of them - I
see a different behavior:
py Äpfel.decode('latin-1
Martin v. Löwis added the comment:
I have three problems with the current form of the patch:
a) in the documentation, it should state that __dict__ is an attribute,
not a method.
b) why are you moving the subclassed-from-builtin types into the except
block? It is there to reject things
Martin v. Löwis added the comment:
Ok, I added a comment in r57958
--
resolution: - fixed
status: open - closed
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1626801
Martin v. Löwis added the comment:
I'm closing this as out-of-date, now that the documentation format is
not based on TeX anymore. If you would like to port this to Sphinx, feel
free to reopen it (or submit any such feature as a new patch).
--
nosy: +loewis
resolution: - out of date
Martin v. Löwis added the comment:
Thanks for the patch. Committed as r57960.
--
nosy: +loewis
versions: +Python 2.6 -Python 2.4
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1388440
Changes by Martin v. Löwis:
--
resolution: - accepted
status: open - closed
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1388440
_
___
Python-bugs-list
Martin v. Löwis added the comment:
Thanks for the patch. It wouldn't work as-is, because it broke PGEN. I
fixed that, and committed the change as r57961 and r57962.
--
resolution: - accepted
status: open - closed
versions: +Python 2.5, Python 2.6
Martin v. Löwis added the comment:
What's wrong with
py for x in 1,2,3:print(x,end= )
...
1 2 3
Closing as invalid.
--
nosy: +loewis
resolution: - invalid
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1101
Martin v. Löwis added the comment:
Why do you think so? The documentation is correct as it stands;
dummy_threading should be used when thread is not present, not when
threading is not present (as threading will always be present, it just
won't import when thread is not present).
--
nosy
Changes by Martin v. Löwis:
--
assignee: - loewis
nosy: +loewis
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1102
__
___
Python-bugs-list mailing list
Unsubscribe
Martin v. Löwis added the comment:
Thanks for the patch. Committed as r57984 and r57985.
--
nosy: +loewis
resolution: - accepted
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1105
Martin v. Löwis added the comment:
Thanks for the patch. Committed as r57990 and r57991.
--
resolution: - accepted
status: open - closed
versions: +Python 2.5, Python 2.6 -Python 2.3
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue786737
Martin v. Löwis added the comment:
The patch looks fine to me (with the addition of checking for sunos5
instead). A few things to consider:
- you could check the system at import time, rather than call time, of
_get_soname()
- notice that the file is located in /usr/ccs/bin, which may
Martin v. Löwis added the comment:
There are really two issues here; it is usually better to report them
separately, so they can be analyzed, fixed, and closed separately:
a) the compileall script apparently fails (not surprisingly so, I never
tested it for 3.0), and
b) Python does not work
Martin v. Löwis added the comment:
For 2.5, it reverts to the state of 2.4. You'll have to find a
work-around on your own.
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue978833
Martin v. Löwis added the comment:
Can you please elaborate? What does that have to do with Python?
--
nosy: +loewis
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1112
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Martin v. Löwis added the comment:
A plain print only results in output of built-in function print in
interactive mode, as interactive mode will not only perform the action,
but also display the result. In a Python script, a plain print will
have no effect.
Guido, can you take a look
Martin v. Löwis added the comment:
Greg, can you take a look? If not, please unassign.
--
assignee: - gregory.p.smith
nosy: +gregory.p.smith, loewis
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1112
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1115
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Martin v. Löwis:
--
assignee: - loewis
nosy: +loewis
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1104
__
___
Python-bugs-list mailing list
Unsubscribe
Martin v. Löwis added the comment:
Marc-Andre, what should we do about this patch?
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1505257
_
___
Python-bugs-list mailing
Changes by Martin v. Löwis:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1116
__
___
Python-bugs-list mailing list
Unsubscribe:
http
1 - 100 of 4659 matches
Mail list logo