R. David Murray added the comment:
"things with __getitem__ are clearly iterable"
This is false. IMO it should be fixed in the glossary. It should say "or
__getitem__ method implementing sequence semantics". That plus the addition to
the Iterable docs w
R. David Murray added the comment:
Thanks for the suggestion, but I don't think so.
Python imports are not lazy. They are ordered. Python is an *interpreted*
language, so __subclasses__ is only going to hold those subclasses whose class
definitions have been executed. This is fundamental
Changes by R. David Murray <rdmur...@bitdance.com>:
--
resolution: -> out of date
stage: -> resolved
status: open -> closed
superseder: -> can't interpolate byte string with \x00 before replacement
identifier
___
P
R. David Murray added the comment:
No, refusing to guess in this case is to believe the class's declaration that
it is an iterable if (and only if) it defines __iter__, which is the modern
definition of iterable. If that doesn't work when the object is iterated,
that's a bug in the class
R. David Murray added the comment:
Thanks for being interested in improving Python. Please join the discussion in
the existing issue 26781, which proposes a max_depth parameter for walk.
--
nosy: +r.david.murray
resolution: -> duplicate
stage: -> resolved
status: open -&g
R. David Murray added the comment:
This is the standard way that we write examples. Sprinkling in extra blank
lines everywhere would make the examples less readable. One you've learned how
the command interpreter works, the examples are clear, so you each beginner
only has to learn
David Roundy added the comment:
Here is a little script to demonstrate the regression (which yes, is still
bothering me).
--
type: -> performance
versions: +Python 3.5
Added file: http://bugs.python.org/file47016/test.py
___
Python tracker &
New submission from David Rieger:
IPython's "who" and "whos" command provide a way to list all user-defined
variables and inspect them, respectively.
At the moment, a way to work around this would be by either using e.g. "pp
locals()" to list all local vari
R. David Murray added the comment:
If I remember correctly, the exceptions adhere to the standard because it gives
the option of "signaling" in those cases (but in any case it is the behavior we
want).
0.5 is a float, so x**.5 is not the square root.
>>> math.sqrt
R. David Murray added the comment:
I just had a colleague get confused about the container returning self, and he
was referring to the iterator protocol docs at
https://docs.python.org/3.6/library/stdtypes.html#iterator.__iter__. If you
don't read that section with your thinking cap firmly
R. David Murray added the comment:
The biggest problem, as paul.j3 says, is to get someone from core to review the
argparse issues. I am currently planning to make argparse one of my foci in a
sprint we are doing at the beginning of September, so there is some hope
Any reviews/testing
R. David Murray added the comment:
It is documented how to call a static method when you don't have an instance.
So when you don't (for example, inside a static method on the same class) you
use that form (call the method on the class name).
I realize you don't find this clear
R. David Murray added the comment:
Thanks. OK, so you agree a fix is appropriate. What about the question of
backport/backward compatibility?
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
R. David Murray added the comment:
I don't think that helps. The issue here is that *sequences* are iterated over
by incrementing an integer index. If you change the size of the list, you are
potentially changing which value any given index points to. Presumably the
tutorial writer thought
R. David Murray added the comment:
I'm not sure there's a "best practice" choice between the two calling forms
that are documented. Although obviously when you don't have an instance you
can't use the instance calling form. I think it is *common* practice to use
the instance for
R. David Murray added the comment:
Also note that we have fixed a number of bugs in the stdlib code where a raw
string was not used for a docstring when it should have been. And when I say
bugs, I mean both formatting problems in pydoc, and doctest bugs. There may
even have been a case
R. David Murray added the comment:
Given a choice between catering for Python programmers and catering for
Java/C++ programmers, the Python docs obviously ought to chose to cater to
Python programmers. To a python programmer, calling C.f() is intuitive.
I would myself definitely
R. David Murray added the comment:
I think we are waiting on confirmation that we have a buildbot that has the
necessary headers.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
David added the comment:
I made the syntax error go away by moving the global current_user above the
try..
I will have to revisit this one when time permits and write a script that
recreates the error. This will probably be later this week.
Thanks for your volunteer service.
David
On Jul
David added the comment:
when I do anything like this:
import flask ...
class User..
.
.
.
try:
current_user
except NameError:
global current_user
current_user = User(request.form['parameter1'], request.form['parameter2'],
'')
I get the error that current_user_user
New submission from David:
when I do anything like this:
import flask ...
try:
current_user
except NameError:
global current_user
current_user = User(request.form['parameter1'], request.form['parameter2'],
'')
I get the error that the_user was 'used' before the global
David Haney added the comment:
I've attached the test output summary from a recent build.
--
Added file: http://bugs.python.org/file46995/tests.out
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
R. David Murray added the comment:
Thanks, Joel!
--
resolution: -> fixed
stage: backport needed -> resolved
status: open -> closed
type: -> behavior
___
Python tracker <rep...@bugs.python.org>
<http://bugs.
R. David Murray added the comment:
New changeset 3bbdf990a2c1b0b303b950058e3177a1bd5f697a by R. David Murray (Joel
Hillacre) in branch '3.5':
bpo-30532: Fix whitespace folding in certain cases (#2592)
https://github.com/python/cpython/commit/3bbdf990a2c1b0b303b950058e3177a1bd5f697a
R. David Murray added the comment:
New changeset c60d2f5e8609b040ab58c498fde23928fe9dbef5 by R. David Murray (Joel
Hillacre) in branch '3.6':
bpo-30532: Fix whitespace folding in certain cases (#2591)
https://github.com/python/cpython/commit/c60d2f5e8609b040ab58c498fde23928fe9dbef5
R. David Murray added the comment:
Reading through some of the linked material, it looks like the issue is with
how UNC "symlinks" are resolved.
--
nosy: +r.david.murray
___
Python tracker <rep...@bugs.python.org>
<http://bugs.py
R. David Murray added the comment:
@qingyunha: we are telling you that that would *introduce* a bug. This is
working the way it is supposed to.
Vinay, what if we rewrote the beginning of that paragraph like this:
Sets the threshold for this logger to lvl. Logging messages which are less
R. David Murray added the comment:
If I saw your message, I would think "what is a 'simple name'?". There's no
glossary entry for that, nor is it a concept used elsewhere in the
documentation as far as I remember. One could instead use "single identifier",
but t
R. David Murray added the comment:
I will let Vinay answer definitively, but this is working as designed. This
allows you to set 'debug' level on a sub-logger without getting debug output
for every logger in your system, which is what you would get otherwise as the
default logging level
R. David Murray added the comment:
I think the current error message is more informative than your suggestion,
myself. However, the message could say "keyword argument name" instead of just
"keyword", which I think would be quite a bit clearer.
I seem to remember anothe
R. David Murray added the comment:
Probably. Figure out a protocol to inject them into linecache, perhaps. But
I'm not sure such a thing would be accepted. If you can figure out a way to
make it work at least theoretically, it would probably be best to talk about it
on python-ideas first
R. David Murray added the comment:
This issue is closed. Please open a new issue for your problem and proposal.
--
nosy: +r.david.murray
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
R. David Murray added the comment:
I'm guessing we can only do something here in 3.7, for backward compatibility
reasons, but maybe I'm wrong. Hopefully Lukasz will notice the activity on the
issue and have time to take a look.
--
nosy: +r.david.murray
versions: +Python 3.6, Python
Changes by R. David Murray <rdmur...@bitdance.com>:
--
assignee: -> docs@python
components: +Documentation
nosy: +brett.cannon, docs@python, eric.snow, ncoghlan
versions: +Python 3.6, Python 3.7
___
Python tracker <rep...@bugs.pytho
R. David Murray added the comment:
Yes, setting _MAX_LENGTH can be an independent feature request.
The default will not be changed, however, since it is the most useful default
given that assertEquals in general produces a much more useful diff output in
addition to the one-line summary
Changes by R. David Murray <rdmur...@bitdance.com>:
--
versions: -Python 3.3, Python 3.4
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
R. David Murray added the comment:
There's a deeper problem here involving how Header is used in compat32 that
I've been aware of for a while but haven't had time to try to think through a
fix for (there may not be one, given the history of the compat32 code). In the
meantime, the proposed
David Lord added the comment:
After thinking about it more, I guess I misunderstood what \w was doing
compared to isidentifier. Since Python just relies on the Unicode database,
there's not much to be done anyway. Closing this.
For anyone interested, we ended up with a hybrid approach
David Lord added the comment:
Adding `or ('a' + s).isidentifer()`, to catch valid id_continue characters, to
the test in the previous script reveals many more characters that seem like
valid word characters but aren't matched by `\w`.
--
___
Python
New submission from David Lord:
This came up while writing a regex to match characters that are valid in Python
identifiers for Jinja. https://github.com/pallets/jinja/pull/731 `\w` matches
all valid identifier characters except for 4 special cases:
import unicodedata
import re
import sys
R. David Murray added the comment:
I have no opinion on that issue. I opened this issue to fix a hole in our
validation, but if that hole no longer exists after that (subsequently opened
:) issue is resolved, then this isn't needed (sorry, Ammar, and thank you for
your work
R. David Murray added the comment:
Yes. There's a chance someone else will review it if you do that. I'm still
not likely to have time for a while, myself, but ping me again in a month if I
haven't gotten to it.
--
___
Python tracker <
R. David Murray added the comment:
Per our current policy with respect to mime types, this should be added to all
currently maintained versions.
--
stage: -> needs patch
versions: +Python 2.7, Python 3.5, Python 3.6
___
Python tracker &
R. David Murray added the comment:
If you pass shell=True, PWD gests set, because it is a shell variable and the
shell sets it. If you don't, it doesn't, just like all the other
shell-maintained variables. I'm not sure it is worth calling out specifically
in the Popen docs, myself
R. David Murray added the comment:
Interestingly, this just came up again in issue 30717.
--
nosy: +r.david.murray
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
R. David Murray added the comment:
See also issue 12568.
--
nosy: +r.david.murray
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
R. David Murray added the comment:
We should fix the docs for 3.5 and 3.6, and open an enhancement request for 3.7
if we still think this feature is a good idea.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
R. David Murray added the comment:
If the docstring changes incorporate changes from this PR, I'd keep them in a
single PR myself. If not, two PRs would make review easier. On the other
hand, if haypo is volunteering to do the review, do whatever he wants
R. David Murray added the comment:
I'm not entirely sure what you are asking for opinions on, but for what it is
worth I'm with Haypo: the repr should show the *actual* value of the attributes.
--
nosy: +r.david.murray
___
Python tracker <
R. David Murray added the comment:
Hmm. All the dunder methods are listed in the index on the '_' page. It would
kind of be consistent to have an '@' page. Not sure what would be needed to
make that happen though (might be a sphinx level thing).
--
nosy: +r.david.murray
R. David Murray added the comment:
See also issue 30772 about the deeper problem.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
David Bolen added the comment:
Antoine, yes. Send me your public key (db3l.net at gmail) and I'll set it up.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Changes by R. David Murray <rdmur...@bitdance.com>:
--
nosy: +lukasz.langa
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue30760>
___
Changes by R. David Murray <rdmur...@bitdance.com>:
--
nosy: +ncoghlan
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue30755>
___
_
R. David Murray added the comment:
IMO allow_non_nfkc=True that just returns False would be a bad idea, since as
Benjamin points out it *is* a valid identifier, it's just not normalized (yet).
Raising might work, that way you could tell the difference, but that would be
a weird API
R. David Murray added the comment:
Given that background, closing it seems reasonable to me :)
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
R. David Murray added the comment:
If it's a good idea, why close the issue? Maybe post it to core-mentorship
instead? It's not an easy issue, but it also has the beginnings of a patch.
So if there is anyone on core-mentorship with some windows knowledge (and I'm
guessing their are), maybe
R. David Murray added the comment:
Given that there hasn't been any response that would help us improve the docs
on this, I'm going to close the issue. I hope you've figured out how to do
what you want to do!
--
resolution: -> not a bug
stage: -> resolved
status: open -&g
Changes by R. David Murray <rdmur...@bitdance.com>:
--
stage: -> backport needed
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
R. David Murray added the comment:
New changeset b350c22ebcbb891412e0b334afc9f0db19534e06 by R. David Murray (Joel
Hillacre) in branch 'master':
bpo-30532: Fix whitespace folding in certain cases
https://github.com/python/cpython/commit/b350c22ebcbb891412e0b334afc9f0db19534e06
R. David Murray added the comment:
Just as well. I had no time last weekend. I should have time this Sunday,
though.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
R. David Murray added the comment:
On the PR Berker wrote:
I'm wondering if we should still advertise the use of set([...]). We
replaced all instances of it with set literals in the stdlib.
set([...]) is part of the language, and the python documentation is also a
specification
Changes by David Haney <david.ha...@gmail.com>:
--
pull_requests: -2361
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue30183>
___
David Haney added the comment:
I submitted a pull request for a possible fix for this issue but haven't
received any feedback yet. Is there any additional information needed from me?
--
pull_requests: +2361
___
Python tracker <rep...@bugs.python.
R. David Murray added the comment:
This isn't the place to get help on Python coding, but since this is a
relatively new API I'll give you a pointer, and then you can tell me where the
docs need improvement :)
If you do message_from_string(yourstring, policy=email.policy.default), you
should
R. David Murray added the comment:
IMO, it would actually be surprising for ChainMap to support unhashable keys.
In Python, as Raymond indicates, "mapping" is pretty much synonymous with
'dict-like', and it would be where that was *not* true that we might add extra
doc
R. David Murray added the comment:
Yep, you found an edge case I didn't write a test for. The defect should get
added to the header object during parsing. (Those are supposed to get copied
to the message object...)
--
___
Python tracker <
R. David Murray added the comment:
I'll make one argument in favor of retaining the exception, and if that doesn't
fly then I agree to the solution and will try to review the PR soon.
The argument is this: if parsedate_to_datetime raises an error, you get
information about *why* the date
R. David Murray added the comment:
OK, I think I've reloaded my brain at least partially on this topic.
I think my original reason for having prasedate_to_datetime raise errors is
that it was my opinion that that is the way it should work, and that parsedate
should work the same way (raise
R. David Murray added the comment:
This appears to be a duplicate of issue 29097.
--
nosy: +r.david.murray
resolution: -> duplicate
stage: -> resolved
status: open -> closed
superseder: -> datetime.fromtimestamp(t) when 0 <= t <= 86399 fa
R. David Murray added the comment:
The problem is that if it returns None on parse failure, then you can't tell
the difference between the header not existing and the date not being
parseable. I don't have a solution for this problem. Suggestions welcome.
(Note that this is only a problem
R. David Murray added the comment:
This seems sensible to me (I haven't looked at the PR, I'm talking about adding
the support). When textwrap was written python was pretty ascii oriented, so
it is not too much of a surprise that unicode em dashes were not supported.
--
nosy
R. David Murray added the comment:
We don't generally document all exceptions that a method can raise, only those
that are relevant to its specific API. In this case, documenting the exception
answers the question, "what happens if the directory already exists?" This
question i
R. David Murray added the comment:
Yes, that's all you needed to do. She updated your status in the tracker (you
now have the CLA signed '*' next to your name).
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
R. David Murray added the comment:
OK, so the key here is venv's dependency on a pip wheel. That makes sense, but
is certainly counterintuitive. One would naively think that having a copy of
PIP installed would make it easy to link that into the venv, but obviously it
is a lot more complex
Changes by R. David Murray <rdmur...@bitdance.com>:
--
resolution: not a bug -> third party
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by R. David Murray <rdmur...@bitdance.com>:
--
nosy: +brett.cannon, eric.snow, ncoghlan, r.david.murray
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
R. David Murray added the comment:
It's not obvious from your discussion, Nick, *why* venv won't use an upgraded
system pip if it has been manually upgraded. There's no need for internet
access in that case (which is the argument for using the bundled pip when
running ensurepip for the first
R. David Murray added the comment:
Since according to Eryk there's no way to have a reliable cross-platform
exception class catching file name to long, I'm rejecting this feature request.
--
resolution: -> rejected
stage: -> resolved
status: open -&g
R. David Murray added the comment:
Thanks, Sanyam.
--
resolution: -> fixed
stage: needs patch -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
R. David Murray added the comment:
New changeset b9c3da5c89c66dcccf382e8f196746da2a06d4cc by R. David Murray
(Sanyam Khurana) in branch 'master':
bpo-24744: Raises error in pkgutil.walk_packages if path is str (#1926)
https://github.com/python/cpython/commit
R. David Murray added the comment:
There appears to be an errno for file name too long, so I presume you are
making a feature request for a new exception class. I believe Antoine tried to
strike a balance between the utility of the sub-exceptions and their number, so
you'll have to make
R. David Murray added the comment:
What is your proposed solution? This doesn't at the moment sound like a bug in
Python to me.
--
nosy: +r.david.murray
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
R. David Murray added the comment:
Steve can correct me if I'm wrong, but I think this means your Windows OS isn't
up to date. Googling seems to indicate that this isn't a problem unique to
Python.
--
nosy: +r.david.murray
___
Python tracker <
R. David Murray added the comment:
There is a possible future in which the development style is based around
continuous integration with third parties, where we apply our backward
compatibility policy even to changes from one commit to the next within our
development cycle. I think
Changes by R. David Murray <rdmur...@bitdance.com>:
--
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
versions: +Python 3.7
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
R. David Murray added the comment:
Looks like it just needs a NEWS entry.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
R. David Murray added the comment:
There's a good chance, yes. You'll have to keep periodically pinging the issue
(say once a month :), and if you can specifically talk someone into doing a
review your chances go up :) For it to go in we need a review from a
core-dev, but one or more
R. David Murray added the comment:
I'm going to try to review this this weekend.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Changes by R. David Murray <rdmur...@bitdance.com>:
--
resolution: -> not a bug
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
R. David Murray added the comment:
It gets installed along with python3, I believe. If you google for 'python py'
you should see the pypi package version in the top hits.
--
resolution: -> not a bug
status: open -> closed
___
Python tracke
R. David Murray added the comment:
If you just type 'server.py' it will use whichever interpreter is associated
with .py files, which might not be python3. You may want to learn about the
'py' helper command.
--
resolution: -> not a bug
stage: -> resolved
status: open -&g
R. David Murray added the comment:
You don't need an eternal package, just decoding b'xn--w&' with punycode will
produce the traceback.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.o
R. David Murray added the comment:
In thinking about merging this, I realize something I should have thought about
earlier: we are proposing to raise an error where none was previously raised.
Now, any code that would hit this would be broken, but nonetheless, by our
backward compatibility
R. David Murray added the comment:
Either that or you aren't really running the make_server from
wsgiref.simple_server.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
R. David Murray added the comment:
something is wrong in your setup then. I suspect you have a mismatch between
the python version you think you are running the one you are actually running,
and/or which library code it is accessing.
--
nosy: +r.david.murray
R. David Murray added the comment:
Ping the issue again next week if I don't get to it this weekend.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Changes by R. David Murray <rdmur...@bitdance.com>:
--
nosy: -r.david.murray
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
R. David Murray added the comment:
Agreed, there's nothing for us to do here. It sounds like you may need to go
to a help forum to work through your crash.
If you learn things that you think it would be valuable to add to the docs,
please do submit a doc enhancement issue/PR
R. David Murray added the comment:
The pip issue tracker is at https://github.com/pypa/pip/issues if you want to
suggest this, but I doubt it will be accepted. The action *is* something
optional.
--
nosy: +r.david.murray
resolution: fixed -> third party
type: compile er
1401 - 1500 of 12771 matches
Mail list logo
