Changes by R. David Murray :
--
nosy: +jnoller
___
Python tracker
<http://bugs.python.org/issue8333>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
To fix this, urlparse would have to differentiate between a null netloc and no
netloc characters specified at all. This could be done by using None for one
an '' for the other. I'm not sure that behavior change could be backported to
2.
R. David Murray added the comment:
Converting DictMixin to collections.MutableMapping is not necessarily a
complete solution. MutableMapping does not provide all the methods that
DictMixin does. See for example the problems encountered in issue 7975.
--
nosy: +r.david.murray
R. David Murray added the comment:
Thank you very much for those tests. I think you can simplify them a bit. For
example, you can use assertRaises. You also might be able to use the
test_support.temp_cwd context manager in your context manager, even though you
don't need the cwd
R. David Murray added the comment:
The issue is not invalid. The code duplication should be removed, but using the
email module as Éric suggests. Reopening.
--
nosy: +r.david.murray
resolution: invalid ->
stage: committed/rejected -> test needed
status: closed -
Changes by R. David Murray :
--
versions: +Python 3.2
___
Python tracker
<http://bugs.python.org/issue7370>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by R. David Murray :
--
title: patch: BaseHTTPServer reinventing rfc822 -> patch: BaseHTTPServer
reinventing rfc822 date formatting
___
Python tracker
<http://bugs.python.org/iss
R. David Murray added the comment:
If the problem with the fix is that lots of tests use test_support.unlink, then
I don't see why the rename dance can't be implemented in test_support.unlink.
(Possibly conditioned on whether or not the tests are running on a windows
platform.
R. David Murray added the comment:
For what it is worth, the unix 'diff' command does not produce unified format
by default. It doesn't produce the format diff.py does by default either,
though.
Our normal policy is not to change an interface unless there's a strong re
Changes by R. David Murray :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue8357>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by R. David Murray :
--
nosy: +benjamin.peterson
___
Python tracker
<http://bugs.python.org/issue8358>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
It doesn't look like it is the same bug to me. This one is more general.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/i
R. David Murray added the comment:
I didn't put maintainers.rst into 2.6 because I didn't want to commit to
maintaining the two divergent copies. If you want to commit to maintaining it
in the 2.x branch (copying changes backwards from the 3.x branch), then I'd be
+0 (or mayb
Changes by R. David Murray :
--
nosy: +haypo
___
Python tracker
<http://bugs.python.org/issue8366>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Yes, that would be clearer wording.
--
___
Python tracker
<http://bugs.python.org/issue7905>
___
___
Python-bugs-list mailin
R. David Murray added the comment:
There are a couple problems with this patch. The first is that fixing
date_time_string by using strftime rather than email.utils.formatdate is
suboptimal from a code reuse standpoint. The reason is that the date in HTTP
message headers is required to
R. David Murray added the comment:
I've applied the fix to trunk in r79994, and py3k in r79996, but I'm leaving
this open because I still want a unit test for it.
--
keywords: +easy -patch
___
Python tracker
<http://bugs.python.
R. David Murray added the comment:
Believe it or not, this is the documented behavior of Idle on all platforms.
You have to specify -s to have PYTHONSTARTUP run.
See the last comment in Issue5594, and also the referenced issue 5233, which
has a patch that apparently changes this behavior
R. David Murray added the comment:
I guess I wasn't clear. The error you are seeing is exactly the error that
issue 3770 talks about. The *build* process wasn't able to find a functioning
sem_open implementation, and therefore you see that error. Now, clearly your
platform d
R. David Murray added the comment:
Applied to trunk in r8004 and py3k in r8006.
--
resolution: accepted -> fixed
stage: unit test needed -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
It might be worth mentioning in the tutorial the specific problem the OP points
out: that if an object returns itself in __iter__, then that object can have
only one iteration state. And that therefor only an object that is itself a
unique iterator (as
R. David Murray added the comment:
It's too late for 2.7 anyway.
--
nosy: +r.david.murray
priority: -> normal
versions: +Python 3.2 -Python 2.7, Python 3.1
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
I'm pretty sure it only applies to the python docs, since this is the Python
tracker, not the Sphinx or docutils tracker. (I'm not sure how the
'Documentation tools (Sphinx)' component gets in there...as far as I know
Sphinx bugs go th
Changes by R. David Murray :
--
resolution: -> wont fix
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
Yes, thanks for the typo correction.
--
___
Python tracker
<http://bugs.python.org/issue7585>
___
___
Python-bugs-list mailin
Changes by R. David Murray :
--
nosy: +brett.cannon
___
Python tracker
<http://bugs.python.org/issue8389>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by R. David Murray :
--
nosy: +tarek
priority: -> normal
___
Python tracker
<http://bugs.python.org/issue8395>
___
___
Python-bugs-list mailing list
Un
R. David Murray added the comment:
Thanks Mark and Ryan for the patches, and Shashwat for the review. Committed
to trunk in r80062, 2.6 in r80063, py3k in r80078, and 3.1 in r80079.
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -&g
Changes by R. David Murray :
--
nosy: +jnoller
___
Python tracker
<http://bugs.python.org/issue8326>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
No, Brett said he thought it was not a bug. If Raymond disagrees, he'll say
so. If I may attempt to channel Brett, I suspect his logic for closing it
"won't fix" went more or less like this: "it might be theoretically possible to
Changes by R. David Murray :
Removed file: http://bugs.python.org/file16925/unnamed
___
Python tracker
<http://bugs.python.org/issue8402>
___
___
Python-bugs-list mailin
R. David Murray added the comment:
Senthil, Facundo, is there a reason this bug shouldn't be fixed, or are we just
waiting for someone to come up with a patch? I'm assuming the latter and
setting it to languishing, but maybe this will wake somebody up who is
interested in
R. David Murray added the comment:
Will the modified test fail on platforms that don't define HAVE_SIGACTION?
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/i
R. David Murray added the comment:
Yes, my question was directed at finding out if there were any platforms on
which we'd have to add an additional skip (which would mean refactoring that
test into two tests). But if the buildbots are all happy after it is applied
we can probably choo
R. David Murray added the comment:
I think this one is worth making an exception for, since it would mean that a
project could have 3.x doctests that also work with 2.7, whereas if we leave it
out of 2.7 the doctests have to stay in 2.x format even if the project has (at
some future point
R. David Murray added the comment:
@Lennart: no, in that direction (2.7 to 3.x) there's less of a problem. You
leave the module name off in the doctest, and have 2to3 add the
IGNORE_EXCEPTION_DETAIL to the doctest during translation.
I was looking at the farther future case, where a pr
R. David Murray added the comment:
By that logic, 2to3 can't solve anything. I don't think there's any question
that this patch should be applied to 3.2. 3.1 might be an issue as it is a new
feature, but maybe we can claim it is a bug fix :)
As for 3to2, like I said I d
R. David Murray added the comment:
My understanding is that David noticed the problem originally on MacOS. If the
emulation is indeed being used on that platform (and a little googling
indicates the MacOS posix semaphore implementation is considered at least
slightly broken, and FreeBSD
R. David Murray added the comment:
Also note that his results were much worse on MacOS than anyone was seeing on
Linux, which may support this theory :)
--
___
Python tracker
<http://bugs.python.org/issue8
R. David Murray added the comment:
I like this version of the patch better. Is there any reason not to drop the
initial sleep(0.5) and loop 10 times instead? Any place we can cut down the
sleeps so the test suite runs faster on fast machines is good.
As someone else said, it *ought* to be
Changes by R. David Murray :
--
nosy: +rhettinger
___
Python tracker
<http://bugs.python.org/issue8413>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Benjamin was using the term 'bug' as a synonym for 'issue in the tracker'. The
point is that a feature like this (a whole new module) is not an appropriate
tracker item. In most cases the procedure for getting a new module includ
R. David Murray added the comment:
Review the code, test the patch, confirm that it fixes the problem and doesn't
break anything else, and report your results here. That doesn't guarantee that
it will get applied, but it definitely helps.
--
nosy: +r.da
R. David Murray added the comment:
@Éric: even if you prepare the patches, I find I'm not interested in doing the
checkins. If someone else wants to take this on that's fine with me, but I'm
not going to do it.
--
assigne
R. David Murray added the comment:
The meta-tracker (the tracker to report problems with the tracker) is a
separate tracker and you have to create a new login there. I agree that this
is awkward, but nobody has stepped up to fix it yet.
'your issues' is issues assigned to you, a
R. David Murray added the comment:
I'm writing unittests for a program I'm writing, and would really love to be
able to use captured_stdout/stderr. Of course, I have to support Python 2.5,
and can't really justify installing unittest2, so I'll have to roll my own
anyway
Changes by R. David Murray :
--
title: move test_support into the unittest package -> move generally useful
test_support functions into the unittest package
___
Python tracker
<http://bugs.python.org/iss
R. David Murray added the comment:
Thanks, David. test_socket passed on the latest trunk run on the tiger
buildbot.
--
nosy: +r.david.murray
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
type: -> behavior
__
R. David Murray added the comment:
Any module without a listed maintainer is maintained by the community as a
whole (as it says in the introduction). The fact that a module does not have a
listed maintainer does not mean it is dead, and I don't think anyone(except
you? :) thinks that.
R. David Murray added the comment:
The FreeBSD bot in question is now running 6.4, and test_signal is still
failing. I have access to a 6.3 box, which shows exactly the same failures as
I see in the buildbot log. On that box, doing
t = threading.Thread(target=lambda: None)
t.start
R. David Murray added the comment:
I can reliably reproduce the SIGINT problem on a FreeBSD 6.3 box, if (and so
far only if) some test that uses threading is run first (see also issue 3864).
So I suspect this is a freebsd6 specific problem and just needs a skip added.
--
nosy
R. David Murray added the comment:
The FreeBSD 7.2 buildbot also shows this failure. See also issue 3864;
although this failure appears to be slightly different, it might be due to a
remnant of the same platform bug. I'm making everyone from that bug nosy on
thi
R. David Murray added the comment:
That's because 7681 is closed. (That said, I consider it a bug in the tracker
that it defaults to searching only open issues...and I think I filed an issue
in the metatracker for that, too. Maybe I'll get around to fixing it if I can
get agre
R. David Murray added the comment:
I posted this to the checkins list, but for reference, the following invalid
URL should be added to the test cases:
http://[::1/foo/bar]/bad
--
nosy: +r.david.murray
___
Python tracker
<h
R. David Murray added the comment:
I don't know how deep you want to get into detecting invalid URIs, but with the
new patch this one causes a parsing error that is probably worth dealing with:
http://abc[xyz]jkl
Maybe a reasonable set of checks would be (in hostname) that if the pa
Changes by R. David Murray :
--
priority: -> normal
stage: -> committed/rejected
superseder: -> Error calling .storlines from ftplib
type: crash -> behavior
___
Python tracker
<http://bugs.pytho
R. David Murray added the comment:
The test_break unit test is now skipped for freebsd6 on trunk in r80155. I
suspect this affects py3k as well on freebsd6.
--
___
Python tracker
<http://bugs.python.org/issue8
Changes by R. David Murray :
--
nosy: +brian.curtin
___
Python tracker
<http://bugs.python.org/issue5099>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
i486 Ubuntu also showed the test_itimer_virtual failure (but not the other
one...FreeBSD didn't show the other one either) here:
http://www.python.org/dev/buildbot/builders/i386 Ubuntu
trunk/builds/949/steps/test/logs/stdio
--
title:
R. David Murray added the comment:
Just to be clear, the freebsd6 problem was unrelated (presumably). Freebsd7
seems to be suffering from the issue discussed here.
--
___
Python tracker
<http://bugs.python.org/issue8
R. David Murray added the comment:
Alexander, do you think it would be worthwhile to write up a summary of all the
issues involved in these three releated bugs and post it to python-dev?
Alternatively we could ask for a decision on what should be done in python 2.7
from Benjamin
R. David Murray added the comment:
I don't think bash itself has a default path, I think the default path is set
by the system bash profile, and is therefore system dependant. I could be
wrong, though.
--
nosy: +r.david.murray
___
Python tr
R. David Murray added the comment:
The only reason the freebsd6 skips aren't in py3k is that I wanted to make sure
they worked first, and then I was on vacation and haven't gotten to the merge
yet. If you want to merge your patch before I get to it, feel free to merge
mine along
R. David Murray added the comment:
The argument documentation style change was made for py3k. The old convention
is still used in the 2.x docs.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue8
R. David Murray added the comment:
One argument in favor of letting openlog pick it (assuming it uses argv[0]) is
that for a while at least we will have many systems running both python2 and
python3, and it might be useful to have that distinction show up in the log if
the fallback is used
R. David Murray added the comment:
I prefer an approach that allows this option to be defined by default, since if
it is not defined by default it defeats part of the purpose of having the
option. The program author may not be concerned with completions (or even know
about them), but if the
R. David Murray added the comment:
Removing 2.7 since it is now in feature freeze.
--
versions: -Python 2.7
___
Python tracker
<http://bugs.python.org/issue4
R. David Murray added the comment:
I'm not clear on what you are finding weird, here. Your issue title talks
about __repr__, but your last post talks about __str__.
--
nosy: +r.david.murray
priority: -> low
___
Python tracke
R. David Murray added the comment:
I somehow missed the fact that B was a dispatcher subclass. Too early in my
morning, I guess.
So, I think the title of this issue should be "asyncore.dispatcher's __repr__
not being used as fallback for __str__", and your speculation looks l
R. David Murray added the comment:
This is a duplicate of #5998, which was rejected.
--
nosy: +r.david.murray
priority: -> normal
resolution: -> rejected
stage: -> committed/rejected
status: open -> closed
superseder: -> Add __bool__ to threading.Event and multip
R. David Murray added the comment:
Well, the attribute error message could be fixed, too, by enclosing the
forwarding getattr in a try/except and generating the "correct" attribute error
text.
Changing the forwarding behavior itself is the kind of issue that would need to
be di
R. David Murray added the comment:
By the way, the __getattr_ was in the very first version of the code checked in
to the repository. I think the chances of removing it are pretty much zero :)
--
___
Python tracker
<http://bugs.python.
R. David Murray added the comment:
I don't see why --help-options would need to be listed in help. We could pick
a more obscure name, too. The point of this option is to support tools, not
users.
--
___
Python tracker
<http://bugs.py
R. David Murray added the comment:
There is either an issue or a python-dev (or maybe even python-ideas)
discussion about this subject somewhere. It's a much deeper issue than it
appears on the surface.
--
nosy: +r.david.murray
versions: -Python 2.5, Python 2.6, Pytho
R. David Murray added the comment:
Skips ported to 2.6 in r80295, py3k in r80296, and 3.1 in r80297.
--
resolution: -> fixed
stage: needs patch -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
Skip committed to py3k in r80331.
--
resolution: -> fixed
stage: unit test needed -> committed/rejected
status: open -> closed
versions: +Python 3.2
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
Thanks for writing these.
The patch looks good to me (caveat: I only have a passing familiarity with
asyncore). A couple of English nits:
A server which listen on an address and dispatches the
should be 'listens'
# EADDRINUSE indicates
Changes by R. David Murray :
--
assignee: barry -> r.david.murray
resolution: -> accepted
type: crash -> behavior
___
Python tracker
<http://bugs.python.o
Changes by R. David Murray :
Removed file: http://bugs.python.org/file11018/unnamed
___
Python tracker
<http://bugs.python.org/issue1563>
___
___
Python-bugs-list mailin
R. David Murray added the comment:
Since no doc only patch has been proposed and there is some disagreement as to
whether it is needed anyway, I'm closing this per msg88559.
--
resolution: -> out of date
stage: -> committed/rejected
status: ope
R. David Murray added the comment:
Hearing no further argument to the contrary, I'm closing this as invalid.
--
resolution: -> invalid
stage: unit test needed -> committed/rejected
status: open -> closed
___
Python tracker
<http:
R. David Murray added the comment:
The numbers should definitely not be there. I favor just documenting the -m
version, and you'll see why in the attached patch. I've incorporated Anatoly's
improvement to the argument description and the option updates, and made s
Changes by R. David Murray :
--
versions: -Python 2.6
___
Python tracker
<http://bugs.python.org/issue8325>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by R. David Murray :
--
assignee: -> r.david.murray
___
Python tracker
<http://bugs.python.org/issue8325>
___
___
Python-bugs-list mailing list
Un
R. David Murray added the comment:
Assuming that it is OK for this to be in 2.7 beta2 (it smells almost like a
feature, but I'm certainly willing to let it pass as a bugfix myself), the 2.7
doc change in the commit contains a typo (it says versionchanged 3.2 instead of
versionchange
R. David Murray added the comment:
Oh, and you forgot about your note to yourself to update the argument syntax
for the 3.2 commit.
--
___
Python tracker
<http://bugs.python.org/issue8
R. David Murray added the comment:
You are correct, it wasn't an argument. I've never seen numbered alternatives
anywhere *except* the svn merge help (which I've never looked at before, since
I/we don't use it for python development). And I don't like them. (svn
R. David Murray added the comment:
If solution 1 is acceptable in the general case, then I think a better fix
would look like this:
try:
names = os.listdir(path)
except os.error, err:
onerror(os.listdir, path, sys.exc_info())
return
That is, this is another case in which we
R. David Murray added the comment:
Committed (with both call formats) to trunk in r80503 and py3k in r80505.
--
resolution: -> accepted
stage: patch review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bug
R. David Murray added the comment:
The problem is that it would be equally reasonable for someone to want to put
real tab characters in the output section (which results in strange looking
doctest text) or to put expanded spaces in the doctest output section based on
the assumption that
R. David Murray added the comment:
Committed a very slightly modified version of the patch to trunk in r80512, and
to py3k in 80521. I'm leaving this issue open and, unless there is an
objection, if no problems show up after the next beta has been out for a while,
I'll backport
R. David Murray added the comment:
I thought Benjamin's answer was crazy until I looked at the help for
find/rfind. The optional 'start, end' arguments are interpreted like slice
notation, so it does make sense to have the interpretation be the consistent
between
Changes by R. David Murray :
--
resolution: -> out of date
___
Python tracker
<http://bugs.python.org/issue1462525>
___
___
Python-bugs-list mailing list
Un
R. David Murray added the comment:
Some committers have been using 'resolution: accepted' as a way to mark issues
that are definitely going to be fixed/enhancement added. For a critical bug I
think this is a bit redundant (it is more useful for feature requests), but I'm
pr
R. David Murray added the comment:
Seems reasonable.
--
nosy: +r.david.murray
status: open -> closed
___
Python tracker
<http://bugs.python.org/iss
R. David Murray added the comment:
How much would increasing the loop count slow down the test? Since if the bug
isn't present the loop will run to the end every time, if it is non-trivial it
would probably be better to keep it shorter, since Brian said it failed one way
or another 9 o
R. David Murray added the comment:
Well, I don't think removing the current onerror support is a viable option for
backward compatibility reasons, so we might as well fix it.
I agree that (2) sounds tricky to get reliably right, while I don't see how (1)
is an improvement over on
R. David Murray added the comment:
Changing the default value of shell is not an option anyway.
The behavior you describe is exactly what one should expect: the environment in
which the executable is located is the environment of the process calling
Popen, not the environment passed to Popen
R. David Murray added the comment:
-1
IMO it just makes the output messier and less readable, and I personally am
fine with judging the progress by the filenames.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue8
R. David Murray added the comment:
I think the issue is still open waiting for a unit test. On the other hand,
how likely is it that someone is going to write one at this point? If someone
doesn't speak up soon I think you can close it.
--
nosy: +r.david.m
2101 - 2200 of 10554 matches
Mail list logo
