R. David Murray added the comment:
Closing this issue as out of date was inappropriate. It may be a duplicate,
but someone with an interest should go through and evaluate all the related
'tolerant HTML parser' issues.
Issue 1486713 could perhaps serve as a master issue fo
R. David Murray added the comment:
See also issue 1058305, which may be a duplicate.
--
___
Python tracker
<http://bugs.python.org/issue1486713>
___
___
Pytho
R. David Murray added the comment:
Well, I let this bake so long I missed 2.6, but I've backported the fix to 3.1
in r84543.
--
status: open -> closed
___
Python tracker
<http://bugs.python.or
Changes by R. David Murray :
--
priority: high -> normal
___
Python tracker
<http://bugs.python.org/issue1467619>
___
___
Python-bugs-list mailing list
Un
R. David Murray added the comment:
Comments on patch:
1) if I'm reading the RFC correctly, to be validating strictly in compliance
with the RFC \r and \n should also raise an error. Do you agree?
2) We've pretty much dropped the convention of adding history notes to the file
Changes by R. David Murray :
--
nosy: +asksol
___
Python tracker
<http://bugs.python.org/issue9733>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
After thinking about it, I'm inclined to reject this and say that quopri should
be fixed to reject string input to decode. On python-dev Guido opined that a
kind of polymorphism in the stdlib was good (bytes in --> bytes out, string in
-->
Changes by R. David Murray :
--
nosy: +loewis
___
Python tracker
<http://bugs.python.org/issue9741>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Thanks for contributing this; sorry it took so long to get a review. Overall
the tests look good (I didn't work through the logic of each test that looks up
data; I'm trusting you on that part :)
Here are some comments:
1) In test_listmailcap
R. David Murray added the comment:
Matt: if you want to learn the file format and propose a patch, I think it
would be OK for gzip to duck-type the file object and only raise an error when
a seek is explicitly requested. After all, that's the way real file objects
work. A quick glan
Changes by R. David Murray :
--
keywords: +easy
nosy: +pitrou
versions: +Python 3.2
___
Python tracker
<http://bugs.python.org/issue9759>
___
___
Python-bug
R. David Murray added the comment:
Note that issue 6074 may be relevant to your problem.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue9
R. David Murray added the comment:
If this is a problem with the Apple supplied tk there isn't much we can do
about it from the Python end. We've had a number of other bugs like that...
--
nosy: +r.david.murray
___
Python trac
Changes by R. David Murray :
--
nosy: +bethard
___
Python tracker
<http://bugs.python.org/issue9779>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by R. David Murray :
--
nosy: +bethard
___
Python tracker
<http://bugs.python.org/issue9509>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
I've included my take on this in my proposed patch for issue 9608.
--
stage: -> committed/rejected
superseder: -> Re-phrase best way of using exceptions in doanddont.rst
type: -> behavior
___
R. David Murray added the comment:
Here is a more extensive rewrite that I think makes things clearer and (I hope)
makes the text read better. I also updated the preceding section per the
confusion expressed in issue 8518.
Note that this patch is somewhat Python3 specific, since it assumes
R. David Murray added the comment:
(1) and (2) are good ideas. For (3), would it be clear enough if it read
"``except:`` catches *all* exceptions, [...] and GeneratorExit (which is not an
error and should not normally be caught by user
R. David Murray added the comment:
cvxopt looks like it includes a C-based extension module. Have you reported
the bug to cvxopt? They are more likely to be able to spot the problem and
determine if it is a bug in Python or their code.
--
nosy: +r.david.murray
R. David Murray added the comment:
Python 3.2a2+ (py3k:84613, Sep 7 2010, 19:17:31)
[GCC 4.4.4] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> "%s %(abc)s" % dict(abc=2)
"{'abc': 2}
Changes by R. David Murray :
--
nosy: +eric.araujo
___
Python tracker
<http://bugs.python.org/issue9807>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by R. David Murray :
--
nosy: +brian.curtin, tim.golden
___
Python tracker
<http://bugs.python.org/issue9808>
___
___
Python-bugs-list mailing list
Unsub
R. David Murray added the comment:
See also Issue7860.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue2745>
___
___
Python-bugs-list m
R. David Murray added the comment:
Python's strftime is a thin wrapper around the system strftime. This means,
for example, that a slightly different set of % codes is supported on windows
vs linux. So, from Python's point of view this is at *most* a doc bug.
That said, I think
Changes by R. David Murray :
--
resolution: -> duplicate
stage: needs patch -> committed/rejected
status: open -> closed
superseder: -> %-formatting and dicts
___
Python tracker
<http://bugs.pytho
R. David Murray added the comment:
The general rule for submitting patches is to make them against development
trunk (which is currently the py3k branch). Unified diffs from the top level
of the checkout are preferred; whole files are not useful.
However, it is not clear what bug you are
R. David Murray added the comment:
I did not realize the build instructions recommended using the buildbot tool.
It is clearly past time I got around to doing windows build myself.
Please regenerate the diffs from the top level of the checkout, and we'll see
if one of the windows
R. David Murray added the comment:
If you could update it that would be great.
--
___
Python tracker
<http://bugs.python.org/issue1466065>
___
___
Python-bug
R. David Murray added the comment:
Here is another edit pass, incorporating Éric's suggestions and adding some
additional tweaks. In particular, I eliminated the anti-pattern of catching
(IOError, OSError) in one of the earlier examples in favor of the correct
EnvironmentError, and
R. David Murray added the comment:
Please read about floating point arithmetic in the tutorial:
http://docs.python.org/tutorial/floatingpoint.html
Also observe that this works:
>>> Fraction(Decimal('1.23'))
Fraction(123, 100)
So yes, it is a limitation in ho
R. David Murray added the comment:
That bug (the link works fine for me) leads to this bug: Issue6792. Closing
this one as duplicate.
--
nosy: +r.david.murray
resolution: -> duplicate
status: open -> closed
superseder: -> Distutils-based installer does not detect 64bit ve
R. David Murray added the comment:
I'm not very familiar with zipfile, but my immediate reaction is, why should
it? It can't know that the file is a unix file, and indeed if the program is
running on windows it may not be.
Perhaps instead there's something missing in the API
R. David Murray added the comment:
Is this merge going to happen before 3.2 beta?
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue5
R. David Murray added the comment:
Committed in r84719 and r84720, backported to 2.7 in r84721 with the addition
of a sentence admitting that sometimes you need a bare except to catch
third-party exceptions that don't inherit from Exception.
--
resolution: -> fixed
stag
R. David Murray added the comment:
But if it is a bug, it is a bug in OS/X, not in Python. Python could
potentially fix it for python programs by providing our own strftime, but until
someone does that the best we can do is a doc mention of this platform quirk
Changes by R. David Murray :
--
nosy: +pitrou
___
Python tracker
<http://bugs.python.org/issue9837>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
... is also the Ellipsis object, and it is probably even more important that
the index cross reference that usage :)
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue9
R. David Murray added the comment:
I discussed this issue with Antoine Pitrou on #python-dev, and his opinion is
that SMTPSocketConnectError doesn't add enough value to be worthwhile. So he
is in favor of making this a doc fix.
However, the suggestion also came up to have SMTPExce
R. David Murray added the comment:
We use versions to track which versions we are going to fix, not which versions
are affected (which is why we don't list any versions pre-2.5...2.5 and 2.6
occasionally get security fixes, but no earlier versions even get those).
Now, why Brett remove
R. David Murray added the comment:
After the decision to ignore undecodable file names in os.listdir but before
PEP 383 there was a long discussion on python-dev (in which I was a
participant) about how horrible just ignoring the undecodable filenames was.
This applies *especially* to the
R. David Murray added the comment:
But in the case of BZ2File and ssl.SSLContext.load_cert_chain(), isn't it the
case that they are trying to open the files? So producing an early error about
the decoding problem makes sense. Are there any functions other than listdir
where the de
R. David Murray added the comment:
Assuming we can break backward compatibility, it sounds fine to me.
--
___
Python tracker
<http://bugs.python.org/issue9
R. David Murray added the comment:
Antoine, any reason not to put the close in the ZipFileExt close method instead
of a __del__ method? (And document it, of course).
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue9
Changes by R. David Murray :
--
nosy: +asksol, jnoller
___
Python tracker
<http://bugs.python.org/issue9851>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
The test does not fail if FSIZE is not max on linux/py3k, but max is still
represented as -1 on linux. So the reported bug is no longer valid, but
Martin's concern has not been addressed.
--
nosy: +r.david.m
R. David Murray added the comment:
Shouldn't the test suite catch such discrepancies by testing all of the API?
So your script catching something would be the equivalent of "oops, we forgot a
test" (or "oops, this name shouldn't be public"). Which is not a bad
R. David Murray added the comment:
As a point of information, on my gentoo linux system without largefile support
in the kernel, any value 4294967295 or above results in getrlimit reporting -1.
Any smaller value is set and reported as itself. (If a sufficiently large
value is passed in to
R. David Murray added the comment:
I can confirm this, and that it works on python2.5 (I don't have a 2.6.2 around
to test). It also has the looping behavior on 2.7 and 3.2.
Given the timing, I wonder if this is the result of the fix to issue 1722344.
(Note, I removed 2.6 because it do
R. David Murray added the comment:
Sébastien, you could email Martin (tracker id loewis) about adding your
buildbot to our unstable fleet (or even to stable if it is stable; that is, the
tests normally pass and don't randomly fail). As long as you are around to
help fix bugs it wou
R. David Murray added the comment:
I'm closing this as invalid, but I note that this kind of behavior change is
not something we would normally have done in a point release if we had realized
the consequences.
--
resolution: -> invalid
stage: -> committed/rejected
s
Changes by R. David Murray :
--
nosy: +r.david.murray
title: urlparse -> cgi handling of POSTed files is broken
___
Python tracker
<http://bugs.python.org/iss
R. David Murray added the comment:
Can you provide a simple example program that demonstrates the problem?
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue9
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue9873>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
I've only been on the periphery of the distutils/makefile discussion, but I
thought the goal was to *autogenerate* a module containing the relevant
information at python build time, instead of (as now) parsing the makefile at
run time. Whether or not
Changes by R. David Murray :
--
nosy: +mrabarnett
___
Python tracker
<http://bugs.python.org/issue416670>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Got your off-ticket email. I was hoping for something that *just* demonstrated
the problem (just enough code to show the issue). It may be a bit before I can
find the time to reduce your code to such a test case.
--
stage: -> unit test nee
R. David Murray added the comment:
It could still exist since we don't seem to have many people building python on
hpux. That said, unless the op confirms the problem still exists in 2.7 or
later this can stay closed.
--
nosy: +r.david.m
Changes by R. David Murray :
--
status: closed -> languishing
___
Python tracker
<http://bugs.python.org/issue460474>
___
___
Python-bugs-list mailing list
Un
R. David Murray added the comment:
Please read
http://docs.python.org/tutorial/floatingpoint.html
Although your case isn't directly covered there, the root cause is the same.
Floating point can't exactly represent 10.3.
Note that in Python2.7 and 3.x, the repr will be shorten
R. David Murray added the comment:
No, this feature request has not been satisfied. Georg fixed some subsidiary
issues, but they did not in fact address the feature request for an shlex.split
equivalent for Windows.
Since no one has expressed interest in working on this, even though model
R. David Murray added the comment:
The bug probably does still exist (see issue 7038 for a recent similar report).
However, without a repeatable test case we can't fix it, so leaving this
closed is fine. If the OP can still reproduce it we can try working on it
again.
--
R. David Murray added the comment:
I would say you should make the call on whether or not it is worth adding.
IIUC it would mean there was more than one way to do something (\Z vs 'exact'),
so I personally am -0 on the feature request. But I'm not a frequent regex
user, so I
R. David Murray added the comment:
Resolution "won't fix" is inappropriate. We'd love to fix it, but someone has
to volunteer to (re)write the doc update...
--
nosy: +r.david.murray
resolution: wont fix ->
type: -> feature request
R. David Murray added the comment:
This update appears to be turning the windows buildbots red. See for example
http://www.python.org/dev/buildbot/all/builders/x86 XP-4
3.1/builds/1230/steps/test/logs/stdio.
--
nosy: +r.david.murray
status: closed -> o
Changes by R. David Murray :
--
nosy: +belopolsky
___
Python tracker
<http://bugs.python.org/issue9888>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
This does not reproduce for me on python2.6.5 gentoo linux; however, gentoo
linux does have some additional post 2.6.5 patches applied.
It also does not reproduce on 2.7.
--
nosy: +barry, r.david.murray
___
Python
R. David Murray added the comment:
It looks like we are getting buildbot failures as a result of this checkin:
http://www.python.org/dev/buildbot/all/builders/i386 Ubuntu
3.x/builds/2216/steps/test/logs/stdio
--
nosy: +r.david.murray
status: closed -> o
Changes by R. David Murray :
--
nosy: +haypo
___
Python tracker
<http://bugs.python.org/issue9889>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
I tested this against my existing py3k nttp client code.
Why is it a good thing to make file a keyword only parameter? But given that it
is, line 720 needs to use it as such, which omission means your missing at
least one test :)
On line 193 you index fmt
R. David Murray added the comment:
Gah. I reviewed patch4, didn't noticed today's update :(
--
___
Python tracker
<http://bugs.python.org/issue9360>
___
__
R. David Murray added the comment:
I understood the documentation snippet Terry quoted as saying exactly what you
say the code does. The doc could be clearer by replacing "multiple times" with
"that number of times". Not that more than two has any meaning currently...
C
R. David Murray added the comment:
OK. It doesn't seem all that likely that we'll be adding parameters, but you
never know. So I'm OK with file becoming keyword only.
As for the overview headers...if they aren't decoded through decode_header
already, why are they unico
Changes by R. David Murray :
--
resolution: out of date ->
status: closed -> open
___
Python tracker
<http://bugs.python.org/issue678250>
___
___
Pyth
R. David Murray added the comment:
OK, I'm not entirely sure I want to post this, but
Antoine and I were having a conversation about nntplib and email and I noted
that unicode as an email transmission channel acts as if it required 7bit clean
data. That is, that there's no
R. David Murray added the comment:
The 'str' around get_param shouldn't be there, that was left over from an
earlier version of the patch.
I use surrogateescape rather than latin1 because using surrogateescape with
ascii encoding gives me a reliable way to know whether or n
R. David Murray added the comment:
That's what the original report is about, as opposed to the linux repr issue
that Martin wants to break out into a new ticket (which I will do). Any ideas
how to fix the test? It didn't fail for me on linux, so I don't have a good
test plat
New submission from R. David Murray :
Breaking out the library bug discussed in issue 678264 from the test bug the
issue is about.
See msg14344 and msg116479.
--
components: Library (Lib)
messages: 117123
nosy: ajaksu2, loewis, mdr0, nnorwitz, r.david.murray, sable
priority: normal
R. David Murray added the comment:
Yes, email6 should make use of datetime objects. For email5 Antoine's proposal
is better, but the question is will it happen before 3.2 beta :)
--
___
Python tracker
<http://bugs.python.org/i
R. David Murray added the comment:
I'm amazed you only got two failures. Victor has been doing a lot of work in
3.2 trying to make non-ascii paths work reliably.
--
nosy: +haypo, r.david.murray
___
Python tracker
<http://bugs.python.org/i
R. David Murray added the comment:
oh, wait, victor's work is for undecodable non-ascii characters. I think flox
did the work on decodable non-ascii characters, and that may well have gone
into 3.1.
--
nosy: +flox
___
Python tracker
R. David Murray added the comment:
And here is Martin's summary of the issue:
I think we really should create new issues for any remaining problems.
AFAICT, the remaining problems are:
- resource.RLIM_INFINITY is -1 on Linux, when it is meant to be
a really large value
- (as you rep
R. David Murray added the comment:
Since changing the implementation would be a backward incompatible behavior
change to a behavior that has existed for a long time, it's the docs that
should be updated.
--
assignee: -> d...@python
components: +Documentation -Library (Lib)
R. David Murray added the comment:
In fact, I find the proposed syntax *less* obvious than the slice syntax, for
sorted. IOW, I'd be -1 on adding these to sorted. The potentially useful case
is between
l[a:b] = sorted(l[a:b})
vs
l.sort(start=a, stop=b)
where the interestin
Changes by R. David Murray :
--
nosy: -BreamoreBoy
___
Python tracker
<http://bugs.python.org/issue1491804>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
I'm assigning this to myself because I'm assigned on all email issues, but that
shouldn't prevent someone from working on a patch implementing Antoine's
suggestion.
--
___
Python tracker
<
Changes by R. David Murray :
--
assignee: -> r.david.murray
___
Python tracker
<http://bugs.python.org/issue9864>
___
___
Python-bugs-list mailing list
Un
R. David Murray added the comment:
Anatoly, last we heard you did not wish to sign the contributor agreement and
so were not submitting patches. We are respecting your wishes by not applying
this. Have you changed your mind?
--
___
Python
R. David Murray added the comment:
Could you post some simple examples and an explanation of what you think the
problem is? I have no clue what problem your code is trying to show just by
looking at it. (Maybe it will be clear to someone else, but still, simple
examples are usually better
R. David Murray added the comment:
No, but you could bring it up on python-ideas. (It would have to wait until
after the moratorium in any case.)
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue9
Changes by R. David Murray :
--
nosy: +gregory.p.smith
___
Python tracker
<http://bugs.python.org/issue9905>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
I believe that charset is the standard default for html, which would make this
a feature request.
--
assignee: tim_one ->
nosy: +r.david.murray
stage: unit test needed -> needs patch
type: behavior -> feature request
versions: +Python 3.
R. David Murray added the comment:
It appears as though this was fixed as part of issue 1983. Antoine, can you
confirm that?
--
nosy: +pitrou, r.david.murray -BreamoreBoy
versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.6, Python 3.0
R. David Murray added the comment:
Perhaps this constant existed at some point on some linux systems...google
found one comment about it referencing posix.2. I also found it mentioned in a
specific version of sendmail, and in bash. When it appears it seems to most
often have the value 127
R. David Murray added the comment:
s/linux/unix/
--
___
Python tracker
<http://bugs.python.org/issue9933>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
it does seem that the consensus is that this is not a generally desirable
feature.
--
nosy: +r.david.murray -BreamoreBoy
resolution: -> rejected
stage: -> committed/rejected
status: open -> closed
_
Changes by R. David Murray :
--
status: closed -> languishing
___
Python tracker
<http://bugs.python.org/issue1763>
___
___
Python-bugs-list mailing list
Un
R. David Murray added the comment:
http://launchpad.net/python-email6
--
___
Python tracker
<http://bugs.python.org/issue9864>
___
___
Python-bugs-list mailin
R. David Murray added the comment:
But if line buffering doesn't work, disabling buffering on stdout/stderr does
have a functional consequence: it allows process output to appear as generated
instead of coming in chunks when the buffer is full. Of course, I could be
compl
R. David Murray added the comment:
Thanks, Jeffrey. I've applied your patch (with minor doc tweaks) to the email6
branch.
--
___
Python tracker
<http://bugs.python.org/i
R. David Murray added the comment:
Hmm. It seems as though since issue 2302 is now closed, the comment about
deadlocking if called before serve_forever may no longer be true. Gabriel?
--
nosy: +r.david.murray
___
Python tracker
<h
2601 - 2700 of 12936 matches
Mail list logo
