R. David Murray added the comment:
Well, I think the fact that os.environ.copy is explicitly supported (and does
indeed do dict(os.environ)) is an argument in favor of giving that same meaning
to copy(os.environ). I think that follows the principle of least surprise
R. David Murray added the comment:
This is the same as issue 15113. If you delete __builtins__, don't expect
Python to work.
--
nosy: +r.david.murray
resolution: -> duplicate
stage: -> committed/rejected
status: open -> closed
superseder: -> IDLE Shell: del
R. David Murray added the comment:
All the tests should run from the standard test runner tool (currently
regrtest), with the GUI tests guarded by the GUI resource, which is how it
works for TK. I always run the test suite with -uall before non-trivial
commits, so I do in fact run the TK
R. David Murray added the comment:
IMO this is not a bug, according to the current documentation it is working as
designed. raw_decode says it decodes a string that *starts with* a json
document.
To my understanding, raw_decode is designed to be used when parsing a stream
containing more
R. David Murray added the comment:
Ah, I see, you are thinking that "json document" includes the possibility of
leading whitespace. That is a reasonable interpretation...just make sure that
we don't break backward compatibility.
--
___
R. David Murray added the comment:
By the way, you can use -F to run the test suite until it fails:
./python -m test -F test_pep277
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue15
R. David Murray added the comment:
Tatiana, are you on a Mac as well?
--
___
Python tracker
<http://bugs.python.org/issue15398>
___
___
Python-bugs-list mailin
R. David Murray added the comment:
We only update the docs for the active versions, so only 2.7, 3.2, and default
(3.3) are going to get updated.
--
nosy: +r.david.murray, vinay.sajip
versions: -Python 2.6, Python 3.1, Python 3.4
___
Python
R. David Murray added the comment:
I found this link:
http://www.weirdnet.nl/apple/rename.html
in issue 8828, which sounds like it is relevant. (I thought I remembered
something about rename not being atomic on OS X.) I didn't read it through,
but maybe Apple fixed th
R. David Murray added the comment:
We don't generally do that kind of type checking.
--
nosy: +r.david.murray
resolution: -> invalid
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.pyth
R. David Murray added the comment:
Looks like this broke the buildbots.
--
nosy: +r.david.murray
status: closed -> open
___
Python tracker
<http://bugs.python.org/issu
R. David Murray added the comment:
I've added the sentence to the docstring, as you suggested. Thanks for the
suggestion.
--
versions: +Python 3.2, Python 3.3
___
Python tracker
<http://bugs.python.org/is
New submission from R. David Murray :
In looking at another os.path.join documentation issue I tried the Windows join
to see if it matched the docs, and found that it was very unclear. I searched
the tracker and found Issue 1669539, which contains much relevant discussion
but also much
R. David Murray added the comment:
I've opened a issue 15414 for fixing the documentation for os.path.join on
Windows, and possibly existing bugs. So I'm reclassifying this as a feature
request, since that is most of what the discussion is about.
--
dependencies: +os
R. David Murray added the comment:
I reworded it so that it is clear we are talking about types and not strings.
--
nosy: +r.david.murray
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
type: enhancement -> behavior
versions: +Python
R. David Murray added the comment:
The screen flickers a bunch, so something involving my display is certainly
happening.
As for runtktests...test suites that live in the package as opposed to the test
directory require support files to gather the tests to be run. This can be
done by the
R. David Murray added the comment:
I wonder if it would be sensible to have test___all__ restore the state of
sys.modules after it runs.
--
___
Python tracker
<http://bugs.python.org/issue10
R. David Murray added the comment:
Yeah, we probably do not want to go there, even though technically I think
those would be bugs. But bugs that it would only be "nice" to fix, not
necessary to fix.
--
___
Python tracker
<http://bu
R. David Murray added the comment:
Done.
--
resolution: -> fixed
stage: test needed -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
Committed. Thanks, Jeff. By the way, although this patch isn't big enough to
require it, it would be great if you would submit a contributor agreement:
http://www.python.org/psf/contrib.
--
resolution: -> fixed
stage: -> committ
R. David Murray added the comment:
Could you please be more specific about what you are trying to do and what
error you are seeing?
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue15
R. David Murray added the comment:
I'm sorry, my phrasing there was awkward. I didn't mean "Why do you think this
is a bug", I meant "I don't think this is a bug, am I missing something?"
--
___
Python tracker
R. David Murray added the comment:
*xml*.dom.minidom parses only XML. The documentation mentions only xml, not
html. I suppose that confusion could arise from the fact that that the w3c-dom
API model can be provided by things that parse html as well. I'm not sure if
it is worth add
R. David Murray added the comment:
Jonathan: we are in feature freeze right now preparing 3.3 for release, so you
might want to ping the issue once 3.3 is out to remind us to do the checkin.
--
nosy: +r.david.murray
___
Python tracker
<h
R. David Murray added the comment:
Thanks for the report. Fixed.
--
nosy: +r.david.murray
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
versions: +Python 3.3
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
Same problem with the epilogue. Fixed both.
--
resolution: -> fixed
stage: needs patch -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
AttributeError is how Python decides that __getattr__ should be called. I
believe this is working as designed.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue15
R. David Murray added the comment:
If I understand correctly, the math module is providing C standard (Annex F)
*floating point* mathematical functions. Mark will have the definitive answer
once he gets a chance to comment. Perhaps a documentation clarification is in
order on this point
R. David Murray added the comment:
I'm not clear if your script is trying to do this, but there is no way to
automatically alphabetize the file. That's why it says "rough" alphabetic
order. The issue is that different languages alphabetize different letters in
differen
R. David Murray added the comment:
Your problems didn't come from the "Python" math library, it came from the C
math library that Python provides a wrapper for, which the documentation does
clearly state. And the result you got is accurate...for a floating poi
R. David Murray added the comment:
I believe Marc-Andre was looking for an actual real-world use case rather than
a hypothetical one. We discussed this briefly on the irc channel and we think
Guido vetoed it on a YAGNI basis (we haven't checked the archives though...) so
a real worl
R. David Murray added the comment:
Are the nanosecond timestamps timestamps or strings? If they are timestamps
it's not immediately obvious why you want to convert them to datetime objects,
so motivating that would probably help. On the other hand the fact that you
have an application
R. David Murray added the comment:
Even if accepted this can't get fixed in 2.7, so removing that from versions.
--
versions: -Python 2.7
___
Python tracker
<http://bugs.python.org/is
Changes by R. David Murray :
--
nosy: +vinay.sajip
___
Python tracker
<http://bugs.python.org/issue15445>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by R. David Murray :
--
resolution: -> duplicate
stage: -> committed/rejected
status: open -> closed
superseder: -> stack overflow evaluating eval("()" * 3)
title: Recursion SIGSEGV -> Eval Recursion SIGSEGV
R. David Murray added the comment:
Thanks. Is this warning printed by the webbrowser unit tests? If not can you
see a way to add one that does?
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue15
R. David Murray added the comment:
@Anton: That's what I was guessing. If we had a unit test in test_webbrowser
that did the same thing, we'd have seen the resource warning when running the
tests and fixed it. However, it looks like there aren't *any* tests for
webbrows
R. David Murray added the comment:
You could do it either way. Normally we prefer to have a test along with any
fix; in this case adding a test involves adding the test module as well, but it
is not different in principle. If you want to work on it and prefer to have it
as a separate issue
R. David Murray added the comment:
Because we are doing what the linux stat call (and command) does . See man
stat.
--
nosy: +r.david.murray
resolution: -> invalid
stage: -> committed/rejected
status: open -> closed
___
Python track
R. David Murray added the comment:
I believe this is a duplicate of issue 14452.
--
components: -IO, Library (Lib)
nosy: +r.david.murray, vinay.sajip
resolution: -> duplicate
stage: -> committed/rejected
status: open -> closed
superseder: -> SysLogHandler sends inva
Changes by R. David Murray :
--
nosy: +pitrou
___
Python tracker
<http://bugs.python.org/issue15464>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
This is an interesting idea and should at least improve matters. I'm
wondering, though...I seem to remember writing code that fished the wrapped
error out using one of those attributrs...but I'm not at a computer where I can
try to check on that.
R. David Murray added the comment:
I want the opposite: a way to say I don't care what the mode is as long as it
exists. Currently there is no way to do that, as far as I remember.
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
I think that expanding them before wrapping is correct. Any lining up would be
true only for the original unwrapped input text.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue15
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue15494>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by R. David Murray :
--
resolution: -> invalid
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
I *want* it to be the default, since I think that is the typical use case, but
the existing default behavior means that such a backward incompatible change
would not be acceptable for exactly the reason you state. So yes, I want it as
a new flag
R. David Murray added the comment:
FTR I agree with Antoine that returning the empty list is the more logical
behavior here. Wrap is turning a string into a list of lines...if there is no
content, the list of lines *should* be empty, IMO. That is what I would
expect, so for me the empty
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue1859>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue15500>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
The first of those acts as I would expect: os.path.realpath is operating only
on the path, so if the last element is a symbolic link it doesn't have any
reason to look for the target of that link.
The second one does seem less intuitive.
I'm no
Changes by R. David Murray :
--
resolution: -> duplicate
stage: -> committed/rejected
status: open -> closed
superseder: -> MULTILINE confuses re.split
___
Python tracker
<http://bugs.python
R. David Murray added the comment:
There is now a test_tools, so it would be great to have tests to go along with
this patch.
I haven't looked at the patch in detail, but as long as you are modernizing it
please kill those "# end ..." lines.
--
nosy:
Changes by R. David Murray :
--
nosy: +vinay.sajip
___
Python tracker
<http://bugs.python.org/issue15541>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
This is not something that is specific to unittest. In Python, if you call a
generator function *it returns a generator-iterator*. Unless you *do*
something with the the iterator, nothing else happens. This is true in *any*
python code.
Unittest calls
R. David Murray added the comment:
Sigh. ;)
At this point in my Python programming I intuitively understand what splitlines
does, but every time we try to explain it in detail it gets messier and
messier. I wasn't really happy with the addition of that sentence about split
in the
R. David Murray added the comment:
And that is the value of os.linesep at Python startup. I'm don't think that we
really support the mutability of os.linesep, we just don't bother to make it
immutable. I'm not sure how this would be documented, since code that does
R. David Murray added the comment:
This message does not come from the Python webbrowser module. You should
report this upstream to the bug tracker for your browser.
--
nosy: +r.david.murray
resolution: -> invalid
stage: -> committed/rejected
status: open -&g
R. David Murray added the comment:
We are happy that you wish to contribute; however, our policy is that
performance enhancements only go in to the newest version of Python, which
means any submitted patch must be against the 'default' branch of the Python
mercurial repository. I
R. David Murray added the comment:
Sure. If you convince me we can reopen the issue :)
--
___
Python tracker
<http://bugs.python.org/issue15492>
___
___
Pytho
R. David Murray added the comment:
Ah, now I see what you are talking about. Yes, your revision in the comment is
clearer; but, unless I read it wrong, in the patch it now sounds like you are
saying that ''.splitlines() does not return the same result as ''.split() when
R. David Murray added the comment:
Ah, I read too quickly before. But that expression "when a delimiter string
*sep* is given" is hard to wrap ones head around in this context. I think the
problem really is that 'split' has such radically different behavior when given
an
Changes by R. David Murray :
--
Removed message: http://bugs.python.org/msg167557
___
Python tracker
<http://bugs.python.org/issue15554>
___
___
Python-bugs-list m
R. David Murray added the comment:
Ah, I read too quickly before. But that expression "when a delimiter string
*sep* is given" is hard to wrap ones head around in this context. I think the
problem really is that 'split' has such radically different behavior when given
an
R. David Murray added the comment:
It is indeed the compatibility that is the worse issue. The problem is what
people have gotten used to and may have coded their applications to expect/deal
with. what people have gotten used to. I agree with you that most people would
*not* find it
Changes by R. David Murray :
--
Removed message: http://bugs.python.org/msg167559
___
Python tracker
<http://bugs.python.org/issue15500>
___
___
Python-bugs-list m
R. David Murray added the comment:
It is indeed the compatibility that is the worse issue. The problem is what
people have gotten used to and may have coded their applications to expect/deal
with. I agree with you that most people would *not* find it surprising to see
the name reflected in
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue15564>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
As far as I can see it has been. In both 2.7 and 3.3 I get:
rdmurray@hey:~/python/p33>./python somecode.py
> /home/rdmurray/python/p33/somecode.py(3)()
-> raise Exception('This is a message that contains a lot of characters and is
very long ind
R. David Murray added the comment:
Good point. Difference paragraph after the example would be best, I think.
--
___
Python tracker
<http://bugs.python.org/issue15
R. David Murray added the comment:
Thanks for sticking with it.
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
This is an intentional change (see issue 1079). It is entirely possible that
this bug fix should be reverted, however, because of backward compatibility
concerns. I'm open to that argument, but I'd prefer to keep the fixed
behavior, since t
R. David Murray added the comment:
Well, I don't think a full discussion of the subtlety about a module appearing
under multiple names belongs in the tutorial, but I think the sentence could be
amended to say "Statements in a module are executed only the *first* time the
modu
R. David Murray added the comment:
I wouldn't worry about working around it from user code...finding and fixing
regressions is what the beta period is for, after all.
As for which component, that's a good question with importlib ;) Both, I
suppose. Not that components are use
R. David Murray added the comment:
If I remember correctly there were non-trivial improvements made to the way
modules are finalized in 2.7 compared to earlier versions. That could be what
exposed the bug. The pre-2.7 code might have been leaving another reference
alive because of your more
R. David Murray added the comment:
In the first example you are shrinking the list you are iterating over, so not
all of the items in the list are going to be tested. Try doing for m in uzlist
instead.
--
nosy: +r.david.murray
resolution: -> invalid
stage: -> committed/re
Changes by R. David Murray :
--
resolution: -> invalid
___
Python tracker
<http://bugs.python.org/issue15579>
___
___
Python-bugs-list mailing list
Unsubscri
R. David Murray added the comment:
I think changing these is unnecessary churn. Change them when you change
surrounding text, just like we refrain from refactoring for PEP 8 compliance,
etc, unless we are changing the code for other reasons. There is nothing
*wrong* with these being links
R. David Murray added the comment:
I'm closing this with no specific resolution because the real resolution is
"this issue is too general" :)
As Ezio said, specific suggestions are welcome, but should be in separate
issues limited to the module/example proposed.
R. David Murray added the comment:
That's because we ultimately decided not to remove it.
--
nosy: +r.david.murray
resolution: -> duplicate
status: open -> closed
superseder: -> os.popen documentation is probably wrong
___
Python
R. David Murray added the comment:
There is already an open issue for this, with a (partial?) patch.
--
nosy: +r.david.murray
resolution: -> duplicate
stage: -> committed/rejected
status: open -> closed
superseder: -> os.popen documentation is pr
Changes by R. David Murray :
--
components: +email
nosy: +barry, r.david.murray
versions: +Python 3.3, Python 3.4
___
Python tracker
<http://bugs.python.org/issue15
R. David Murray added the comment:
Also you will note that the return of the empty list for an empty line is
exactly what you want for wrapping multiple line-break-delimited paragraphs.
Consider:
>>> doc = "a para\nanother para\n\na third, but with an extra blank line
betwee
R. David Murray added the comment:
My understanding is that we try to keep the documentation of all active
branches (2.7, 3.2, and 3.3 currently) in sync except where there are new
features/new deprecations in the development version. So if the 2.7 docs are
update, I think the 3.2 docs
R. David Murray added the comment:
It refers to the 'tools' subdirectory in the Doc directory, but that doesn't
exist unless you've built the docs with 'make' before, or done a 'make
checkout'.
Presumably you have sphinx installed on your system sepa
R. David Murray added the comment:
I don't think the C version does, though.
--
nosy: +pitrou
___
Python tracker
<http://bugs.python.org/issue1>
___
___
Changes by R. David Murray :
--
nosy: +vinay.sajip
___
Python tracker
<http://bugs.python.org/issue15616>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
But if getaddrinfo returns an IPv6 address, shouldn't a localhost connection on
that address work? It seems to me that a localhost connection failing when an
IPv6 localhost address is returned is an OS configuration bug.
--
nosy: +r.david.m
R. David Murray added the comment:
That sounds reasonable. However, on my box that has an IPv6 address configured
on lo, I get the same result with or without that flag:
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128
R. David Murray added the comment:
Hmm. I wonder what is different on my (linux) box. I have ::1 in /etc/hosts
for localhost.
Regardless, it certainly wouldn't hurt to add the flag to the test.
--
___
Python tracker
<http://bugs.py
R. David Murray added the comment:
I see our previous messages crossed, I'm glad you investigated this more
throughly than I did, since clearly just adding the flag could break things.
I'm using gentoo linux (gentoo stable on that particular machine). I don't
guarantee my /et
R. David Murray added the comment:
In t2, you assign to num. That makes it local. In t1, you don't, so num is
picked up from the global scope.
--
nosy: +r.david.murray
resolution: -> invalid
stage: -> committed/rejected
status: ope
R. David Murray added the comment:
Regrtest has evolved. For new test files (ie: 3.3 and later) the preferred (at
least by me :) idiom now is just:
if __name__ == '__main__':
unittest.main()
Everything else is now automatic, using the unittest machinery. For an
ex
R. David Murray added the comment:
I'd like to weigh in on this, but I need time to do research on the question
first. It may be a bit before I get that time.
--
___
Python tracker
<http://bugs.python.org/is
Changes by R. David Murray :
--
nosy: +ezio.melotti
___
Python tracker
<http://bugs.python.org/issue15626>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
The point of running the doctests in the docs to to make sure the *docs* are
correct, not to make sure Python is correct. So IMO adding them to regrtest is
much more trouble than the tiny benefit it would produce for test coverage. On
the other hand
R. David Murray added the comment:
That's exactly what Georg's suggestion is about. Sphinx does have a way to
mark doctest snippets as "run this", "don't run this". I believe that requires
using 'make doctest' as the runner, but I already t
R. David Murray added the comment:
Silence doesn't mean consent, but it does mean you can go ahead and see if
anyone complains :)
I think your proposal is fine, but I'd prefer making the sentinels just
"IGNORE" and "FAIL". The module namespace means the name
R. David Murray added the comment:
Without a reproducible test case I doubt we are going to be able to solve this,
but yes please provide what information you can for the record, in case someone
else runs in to it in a more reproducible situation.
--
nosy: +r.david.murray
R. David Murray added the comment:
Writing such a decorator is pretty trivial to do. On the other hand, I've done
it often enough that I could be convinced it is useful to add.
I think it would be better to have a decorator generator that takes a lock as
its argument, however, sin
4401 - 4500 of 10554 matches
Mail list logo
