R. David Murray <rdmur...@bitdance.com> added the comment:
In fact, this is a backward compatibility issue. Users expect that if you
install it in the old location, it behaves like it did in the old location
(lower security), and this is probably depended on by a number of users of
R. David Murray <rdmur...@bitdance.com> added the comment:
It isn't obvious from your description here what 'listsize' does. I think you
should have provided some more motivating details :)
Looking at your PR, this is essentially a configuration setting. I wonder if
we should think
R. David Murray <rdmur...@bitdance.com> added the comment:
This is probably a topic for the python-ideas mailing list. For example,
rather than complicating input, it might be better to propose adding a
redirect_stdin to contextlib to parallel the two existing redirect context
manage
Changes by R. David Murray <rdmur...@bitdance.com>:
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<https://bu
R. David Murray added the comment:
To be clear: doctest compares strings, so "-0.0" is not the same as "0.0" to
doctest.
--
___
Python tracker <rep...@bugs.python.org>
<https
R. David Murray added the comment:
Can you explain why you think that is a bug in doctest? It looks like you are
getting different output than you expect, but that by itself wouldn't be a bug
in doctest.
--
nosy: +r.david.murray
___
Python tracker
R. David Murray added the comment:
pyping is not part of the standard library, you'll need to find their bug
tracker and report the problem to them.
--
nosy: +r.david.murray
resolution: -> third party
stage: -> resolved
status: open -> closed
type: crash -&
R. David Murray added the comment:
Precompiling as a compile-time optimization would be cool. I think we are
currently favoring doing that kind of thing as an AST optimization step?
I think Raymond and my point was that the current behavior should remain
unchanged by default. So
R. David Murray added the comment:
I agree with Raymond. It would be strange to have the API that is obviously
designed to pre-compile the regex not pre-compile the regex.
If the concern is that a non-precompiled regex might get bumped out of the
cache but you want a way to only compile
R. David Murray added the comment:
Since it hasn't been an issue for a few releases, I say we close it. If there
is some problem remaining, it probably deserves its own tracker issue anyway.
--
nosy: +r.david.murray
resolution: -> fixed
stage: needs patch -> resolved
status
R. David Murray added the comment:
In the absence of the appropriate __future__ import, the python2 division
operator uses integer division.
--
nosy: +r.david.murray
resolution: -> not a bug
stage: -> resolved
status: open -> closed
_
Changes by R. David Murray <rdmur...@bitdance.com>:
--
nosy: +r.david.murray
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python
R. David Murray added the comment:
I can't reproduce this on a linux VM with 3.7 tip. I don't currently have a
windows instance to test against.
--
nosy: +r.david.murray
___
Python tracker <rep...@bugs.python.org>
<https://bugs.p
R. David Murray added the comment:
We do not currently officially support cygwin. There are people working on
getting it working again (and having a buildbot) so we can support it, so
cygwin support is a goal, but not currently a requirement. I've nosied Erik
Brey, who is one of the main
R. David Murray added the comment:
It just needs to call set_unixfrom as well as set_from. I don't know why the
MMDFMessage tracks it separately, but I'm sure the author had a reason that
seemed good at the time :)
--
___
Python tracker <
R. David Murray added the comment:
It looks like it is saving it (the set_from line). Do you have a test that
proves otherwise?
--
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/i
R. David Murray added the comment:
New changeset 9e7b9b21fe45f7d93eaf9382fedfa18247d0d2b2 by R. David Murray
(Rohit Balasubramanian) in branch 'master':
bpo-31507 Add docstring to parseaddr function in email.utils.parseaddr (gh-3647)
https://github.com/python/cpython/commit
R. David Murray added the comment:
Yes, I think we can "fix" some things. I don't know if this falls into the
class of things we should fix. I'll leave that decision to people with more
experience with time stuff.
--
___
Python tr
R. David Murray added the comment:
It's a FAQ, but it was faster for me to just cut and paste than it was to look
up the FAQ link :)
--
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/i
R. David Murray added the comment:
You are being tripped up by operator precedence:
>>> -1**2
-1
>>> (-1)**2
1
--
nosy: +r.david.murray
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python trac
R. David Murray added the comment:
Well, the first question that needs to be answered is: if you call the C
strftime with the same arguments, what result do you get? Because if it is the
C strftime doing this, then it is not a bug in Python, whether it is correct
behavior
R. David Murray added the comment:
I'm not Raymond, but he is correct. This is an example of "taking advantage of
the corner cases", and is something Python does a lot of, especially around
strings and slices. The current behavior was carefully considered and has
useful
R. David Murray added the comment:
Unless I'm mistaken (and someone will correct me and reopen the issue if I am
:) it is intentionally undocumented. A proposal for a documented protocol of
some sort is certainly a possibility, but is something that should start with a
discussion
R. David Murray added the comment:
Generally we're just reporting whatever the platform strftime does. Is that
what happens in this case?
--
nosy: +belopolsky, r.david.murray
___
Python tracker <rep...@bugs.python.org>
<https://bugs.p
R. David Murray added the comment:
Mark: re your training course...if you aren't trying to stay compatible with
python2, note that python3 has a much more sophisticated address parser now,
that gets called automatically if you use the new policies.
--
components: +email
nosy: +barry
R. David Murray added the comment:
You have to remember that the most useful way to think about python slice
indexes is that they point between characters. Consider, for example, that you
have a starting index of something, and you are looking backward in the string
for a trailing delimiter
R. David Murray added the comment:
I think there is nothing to do here unless Mark likes my suggestion and/or
someone comes up with an even better improvement.
--
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/i
Changes by R. David Murray <rdmur...@bitdance.com>:
--
nosy: +r.david.murray
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python
R. David Murray added the comment:
Dmitriy: you will note from the discussion on this issue that your "simple
patch" was not considered sufficient. There were additional concerns voiced
about haypo's patch, which is why I guess it didn't get applied. However, can
you review that a
R. David Murray added the comment:
Well, this is all volunteer work. Maybe someone else will feel like doing it :)
--
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/i
R. David Murray added the comment:
Note that as far as I know without a reproducer, it is confusing to me to talk
about argparse supporting or not supporting utf8. It deals only with text
strings, which are unicode. Or is this a 2.7 only bug report? (Although even
there it would
R. David Murray added the comment:
As I requested in the PR, please provide a way to reproduce the bug you are
reporting.
--
nosy: +r.david.murray
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/i
Changes by R. David Murray <rdmur...@bitdance.com>:
--
versions: +Python 3.6, Python 3.7
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python
R. David Murray added the comment:
I agree that it would seem reasonable to add this to section 6.1 of the
tutorial, since it mentions both import statement variants and the modules
"global symbol table", which are the two concepts involved in import as.
Would you like to pr
R. David Murray added the comment:
Unless I'm mistaken, this has come up again in issue 31469.
--
nosy: +cinerar, r.david.murray
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/i
Changes by R. David Murray <rdmur...@bitdance.com>:
--
superseder: -> Python startup should not require passwd entry
___
Python tracker <rep...@bugs.python.org>
<https://bugs.pyt
R. David Murray added the comment:
It sounds like docker is just broken (I would expect unix tools to work in a
docker container). That however is beside the point.
I believe this is a duplicate of issue 10496, but I don't know why it hasn't
been fixed.
--
nosy: +r.david.murray
R. David Murray added the comment:
It is a new feature, so no it would not be backported.
--
nosy: +r.david.murray
type: -> enhancement
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.or
R. David Murray added the comment:
Where do you find that it is not documented that you would expect it to be?
Because 'import' 'as' is certainly documented.
--
nosy: +r.david.murray
___
Python tracker <rep...@bugs.python.org>
R. David Murray added the comment:
10 million mime parts? That sounds like the kind of thing rfc 1870 was
designed to address in a more general fashion (ie: the SMTP server should be
enforcing maximum message size if you are worried about DOS attacks).
1 million = 3 seconds, 10 million
Changes by R. David Murray <rdmur...@bitdance.com>:
--
nosy: +r.david.murray
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python
R. David Murray added the comment:
Here is a not-much-more-complicated version that solves the problem. It is
probably worth changing as the revised example makes clear the difference
between self and obj, which is an important distinction.
class RevealAccess(object
R. David Murray added the comment:
Have you followed the instructions on this page?:
https://www.python.org/download/mac/tcltk/
--
nosy: +r.david.murray
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/i
R. David Murray added the comment:
https://docs.python.org/3/tutorial/floatingpoint.html
--
nosy: +r.david.murray
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/i
R. David Murray added the comment:
And actually, I wouldn't be surprised if eventlet depended on the
*functionality* in _dummy_threading, so you probably need to restore that, too.
--
___
Python tracker <rep...@bugs.python.org>
R. David Murray added the comment:
dummy_threading should definitely not have been removed, and like all the other
APIs should not be removed until 2.7 is dead. Deprecating it is of course fine
:)
--
nosy: +r.david.murray
___
Python tracker <
R. David Murray added the comment:
Hmm. I must have made a mistake when I ran (jpc's) test on 3.7. It is failing
with the NameError for me when I try it again.
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
type: compile error -&
R. David Murray added the comment:
Mark: Yeah, I think my comment was directed more to haypo than you :)
--
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/i
R. David Murray added the comment:
Seems like it ought to be possible to use the same hooks that venv uses to make
this work, but I haven't looked at the details of how those work.
--
nosy: +r.david.murray
___
Python tracker <rep...@bugs.python.
R. David Murray added the comment:
Anyone who uses stdlib code as examples of best practice doesn't understand the
history of stdlib code.
Generally, we consider the danger of introducing bugs to be more significant
than the benefit of the "cleanup" changes. The fact that you are
R. David Murray added the comment:
Thanks for wanting to improve Python, but we don't usually accept refactoring
requests like this. We "fix" such issues when the code is touched for other
reasons. We'll see what other developers think, though.
--
nosy: +r.da
Changes by R. David Murray <rdmur...@bitdance.com>:
--
keywords: +patch
pull_requests: +3478
stage: needs patch -> patch review
___
Python tracker <rep...@bugs.python.org>
<https://bugs.pyt
Changes by R. David Murray <rdmur...@bitdance.com>:
--
keywords: +patch
pull_requests: +3479
stage: -> patch review
___
Python tracker <rep...@bugs.python.org>
<https://bugs.pyt
R. David Murray added the comment:
Thanks for the PR, but I've managd to finish my rewrite of the folder so that
it not only doesn't traceback on this, but correctly folds it. I'll probably
post the PR tomorrow.
--
___
Python tracker <
R. David Murray added the comment:
I managed to finish the rewrite, and it does fix this issue. I'll probably
post the PR tomorrow.
--
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/i
R. David Murray added the comment:
This is indeed not a bug, it it a consequence of the scoping rules.
What surprises me is that it works without passing in an explicit scope in in
3.7. I'm not sure what we changed that makes that true
R. David Murray added the comment:
Users on linux can and do screw this up too. I believe we also had a case
where a distro screwed up the defaults for, I think, the reverse resolve? Not
sure which test that was, and the test may since been fixed to not depend on
that. The point
R. David Murray added the comment:
Could you please post the examples instead of a zip file? Zip files are hard
to read on a mobile browser :)
--
nosy: +r.david.murray
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/i
R. David Murray added the comment:
In python3, u"a" and "a" are the same thing. The equivalent in python3 would
bee b"a" vs "a", but I have no idea if we even support bytes keys in python3
gdbm.
In 2.7 does has_key(u"x") work if x
R. David Murray added the comment:
Presumably the book didn't tell you everything you need to know to make this
work, or you missed something in the instructions, since this certainly does
work if the module is in a directory on sys.path. (The 'python module1.py'
will only work
R. David Murray added the comment:
Can you figure out what the input to feedparser is in those cases? If pip or
whatever is feeding in a None object, then that's not a bug in feedparser.
However, if the input is a string (or bytes via the bytes interface) and this
is heppening, then there's
Changes by R. David Murray <rdmur...@bitdance.com>:
--
stage: patch review -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<https://bugs.
R. David Murray added the comment:
New changeset e89b35dd2b87e85978b91e3e2dbdea1fc76d6be4 by R. David Murray (Miss
Islington (bot)) in branch '3.6':
[3.6] bpo-31330: Clarify that RawTextHelpFormatter collapses repeated newlines.
(GH-3272) (GH-3429)
https://github.com/python/cpython/commit
R. David Murray added the comment:
New changeset 82cae7c5be4175e2173e4d342825b5315a9d612a by R. David Murray (Miss
Islington (bot)) in branch '2.7':
[2.7] bpo-31330: Clarify that RawTextHelpFormatter collapses repeated newlines.
(GH-3272) (GH-3428)
https://github.com/python/cpython/commit
R. David Murray added the comment:
Thanks, Elena.
--
resolution: -> fixed
stage: -> backport needed
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python
R. David Murray added the comment:
New changeset 397c467c49385023de36411194d381ac993bae1a by R. David Murray
(Elena Oat) in branch 'master':
bpo-31330: Clarify that RawTextHelpFormatter collapses repeated newlines.
(#3272)
https://github.com/python/cpython/commit
R. David Murray added the comment:
It seems likely that this is related to the problems discussed (and hopefully
solved) in issue 30024.
--
nosy: +r.david.murray
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/i
New submission from David Hagen:
Consider the following Python project:
bugtest/
__init__.py (Contents: from .foo import *)
foo/
__init__.py (Contents: from .foo import *)
foo.py (Contents: )
Then in a Python session, the following line executes without error (as
expected
R. David Murray added the comment:
Thanks Paul. By the way, if you want your "real name" in What's New, just let
me know what it is and I'll make the change.
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
R. David Murray added the comment:
New changeset 0f6b9d230674da784ca79a0cf1a03d2af5a8b6a8 by R. David Murray in
branch 'master':
bpo-14191 Add parse_intermixed_args. (#3319)
https://github.com/python/cpython/commit/0f6b9d230674da784ca79a0cf1a03d2af5a8b6a8
R. David Murray added the comment:
New changeset e29ab7e75138e198b51c8bd04afa16d9d2c976a5 by R. David Murray (Miss
Islington (bot)) in branch '3.6':
[3.6] bpo-30824: Add mimetype for .json (GH-3048) (#3401)
https://github.com/python/cpython/commit/e29ab7e75138e198b51c8bd04afa16d9d2c976a5
R. David Murray added the comment:
Well, I consider that they really should be named constants and not an enum,
which is why I consider it an implementation detail :)
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
R. David Murray added the comment:
New changeset 47e5f791223773dd46273153e9fa5b48f848f0c9 by R. David Murray (Miss
Islington (bot)) in branch '2.7':
[2.7] bpo-30824: Add mimetype for .json (GH-3048) (#3394)
https://github.com/python/cpython/commit/47e5f791223773dd46273153e9fa5b48f848f0c9
R. David Murray added the comment:
I think RegexFlag is an implementation detail, but it is true that it isn't
prefixed with a _ so putting it in __all__ is not obviously wrong. However, if
we do that we should also document it (currently it is mentioned only in a
versionchanged line, which
R. David Murray added the comment:
You did not follow the request I made on the PR to explain in this issue you
opened what is failing and why. Unless you convince us that this is actually a
bug in python, we will close the issue and PR
R. David Murray added the comment:
I started rewriting the header folder in response to this bug, because the root
problem is a bit deeper than just _fold_as_ew being missing. I will probably
work on it some more this week, but if I don't think I'm going to get it
finished I'll look
R. David Murray added the comment:
I got an offline agreement from Zach Ware, and nobody here at the sprint has
objected (though I don't know if anyone else looked), so I'll go ahead and
finish the PR.
--
___
Python tracker <rep...@bugs.python.
Changes by R. David Murray <rdmur...@bitdance.com>:
--
pull_requests: +3350
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue15427>
___
Changes by R. David Murray <rdmur...@bitdance.com>:
--
pull_requests: +3348
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue15427>
___
R. David Murray added the comment:
I've turned intermixed.patch into a PR. I tweaked the documentation so that it
does not refer to the details of the implementation. I tweaked the
implementation to have the 'try' start before the code that modifies the state,
and did the line wrapping
Changes by R. David Murray <rdmur...@bitdance.com>:
--
pull_requests: +3345
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue14191>
___
Changes by R. David Murray <rdmur...@bitdance.com>:
--
versions: +Python 3.6, Python 3.7 -Python 3.2, Python 3.3, Python 3.4
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
R. David Murray added the comment:
I've turned this into a PR. The example was already changed in a previous
checkin. I reworded the optparse porting addition to match the existing style
of the list.
--
nosy: +r.david.murray
___
Python tracker
Changes by R. David Murray <rdmur...@bitdance.com>:
--
pull_requests: +3327
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue15427>
___
R. David Murray added the comment:
I don't think this use case is enough to justify documenting it, since this is
not an intuitive meaning of the word PARSER. I think if we wanted to expose
this for this kind of use case, we'd want to rename the constant (with an alias
for backward
David Ellis added the comment:
This is related to the issue I'd brought up previously here so closing this
would also close that issue: http://bugs.python.org/issue29627
I did originally attempt to add support for bytes in PR where I added support
for Path-like objects:
https://github.com
R. David Murray added the comment:
If that is the intended definition of "whitespace" in this context (I have no
opinion on that so far), then the docs need amplification, because in general
"whitespace" includes newlines. On the other hand, this might be considere
R. David Murray added the comment:
Duplicate of issue 29708.
--
nosy: +r.david.murray
resolution: -> duplicate
stage: -> resolved
status: open -> closed
superseder: -> support reproducible Python builds
type: security -> behavior
___
Changes by R. David Murray <rdmur...@bitdance.com>:
--
nosy: +lukasz.langa
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue31307>
___
Changes by R. David Murray <rdmur...@bitdance.com>:
--
nosy: +serhiy.storchaka
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
R. David Murray added the comment:
This is a duplicate of issue 8087, which contains quite a bit of discussion of
the subtleties of the issue.
--
nosy: +r.david.murray
resolution: -> duplicate
stage: -> resolved
status: open -> closed
superseder: -> Unupdated
R. David Murray added the comment:
No, it is correct as worded. It is talking about the default methods. With
the default methods, x == y implies that x is y.
--
nosy: +r.david.murray
resolution: -> not a bug
stage: -> resolved
status: open -&g
R. David Murray added the comment:
OK, agreed. The general principle is: if you reference the name, it is looked
up in the the builtins namespace at runtime (effectively an indirect
reference). If the syntax doesn't explicitly mention the name, then it is
going to be (the equivalent
R. David Murray added the comment:
I see I didn't specifically address your counter argument ("that would
obviously be absurd"). Having thought it it some more, your are right, there
*is* a difference between the examples you think it would be absurd to disclaim
and your ex
R. David Murray added the comment:
shadowadler, the documentation assumes *throughout* that you have not created
any variable that shadows any standard Python entities. There is no other
rational way to write the documentation. To change that policy would, as has
been pointed out, require
R. David Murray added the comment:
I'm not a networking expert at this level, but I believe what is happening here
is that the network stack does an arp, and has a timeout waiting for the arp
response that is longer than your socket timeout. So at some point its arp
timeout expires while
R. David Murray added the comment:
Thanks for wanting to improve the documentation.
Raymond will address this definitively, but unless I'm mistaken part of the
purpose of the examples is to show how the various itertools can be used. If
that is true, then in the context of the overall
R. David Murray added the comment:
I would phrase that as "check if any of the components of the path are links",
at which point one "obvious"[*] answer is "any(x.is_symlink() for x in
[*mypath.parents, mypath])". If the path is absolute, you could use &qu
R. David Murray added the comment:
The docs say, eg: "Return True if the path points to a symbolic link". The
path points to a file system object, and it is the object that is being
checked, not each component of the path used to get to that object.
--
nosy: +r.da
R. David Murray added the comment:
Have you tried the equivalent C program? I'm guessing this is happening at the
OS layer and Python is just reporting it. On my system a timeout of 5 will
always report the OS error.
--
nosy: +r.david.murray
1201 - 1300 of 12771 matches
Mail list logo
