R. David Murray added the comment:
Hmm. OK, I didn't think that's how we'd defined those terms, but then I don't
actually work with the parser much myself :) However, generator expressions
are clearly called out as a separate thing. All of the other display types get
t
R. David Murray added the comment:
In PEP 8 'CapWords" does not refer to the capwords function, as is fairly clear
from context. A big clues is that it is not spelled 'capwords', and case
matters in python function names :) I can understand your getting confused,
Change by R. David Murray :
--
nosy: +lukasz.langa
___
Python tracker
<https://bugs.python.org/issue33481>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Thanks for wanting to improve Python.
Your PR seems to contain quite a few changes that aren't obviously related to
your topic.
As for the topic, I know there are at least some cases where we really do have
to *run* the code to prove the functi
R. David Murray added the comment:
Yes, we are one of those projects that wants it to be possible to build python
without having the tools that generate build artifacts. You will note that we
also check in build artifacts that are produced by our own python scripts, to
avoid the problem of
R. David Murray added the comment:
These are actually reasonable requests, and in fact have been brought up before
and implemented:
>>> x =
>>> urlparse('http://me:myp...@example.com:800/foo;key1=value1?key2=value2#key3=value3#key4=value4')
>>> x
Pars
R. David Murray added the comment:
The fix is mostly likely correct, so we need a PR for this that includes tests.
--
keywords: +easy
stage: -> test needed
versions: +Python 3.7, Python 3.8
___
Python tracker
<https://bugs.python.org/issu
Change by R. David Murray :
--
type: crash -> behavior
___
Python tracker
<https://bugs.python.org/issue33476>
___
___
Python-bugs-list mailing list
Unsubscrib
R. David Murray added the comment:
OK, I've finally gotten around to looking at this. It looks like quopri and
binascii are not stripping trailing whitespace.
quoprimime binascii quopri preferred
b'=' '' b'
R. David Murray added the comment:
I should have just deleted the table, actually.
The only important info in it is that per RFC '=', '=\n', and '= \n' all ought
to become '='. But I don't think we should make that change, I think we should
conti
R. David Murray added the comment:
The ABCs are different from the standard types provided by python itself. The
former are a minimal subset of the methods provided by the latter. So I think
the answer is neither.
--
nosy: +r.david.murray
R. David Murray added the comment:
On the other hand, that section does reference the ABC directly, so I can see
the point of your question. So I guess I'm not sure what the answer is...I
don't think copy is an essential part of the ABC, but I&
R. David Murray added the comment:
Oh, interesting.
I could argue that that's a missing feature in Python's slice handling. The
value of text_space at that point is '+inf', and I obviously incorrectly
assumed that slicing would treat that as if it were [:]. The counter
R. David Murray added the comment:
No, the parenthesis are never part of the tuple itself, even if you can't write
syntactically correct code without them. They just syntactically group the
expression list to isolate it from the surrounding context. It's the same
principle as
Change by R. David Murray :
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
R. David Murray added the comment:
Oh, and the empty tuple is a specific syntactic construct that really is the
empty parenthesis, so that's consistent with the language definition.
--
___
Python tracker
<https://bugs.python.org/is
R. David Murray added the comment:
Please post an example, and not a zip file. Given your description (which
indeed is not enough to understand what you think the problem is by itself), I
think you should be able to post a few lines of python code into the issue in
order to explain what you
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<https://bugs.python.org/issue31145>
___
___
Python-bugs-list mailing list
Unsubscribe:
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
_
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
s
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 a
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 a
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: cra
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 tr
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
<https://bug
Changes by R. David Murray :
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
R. David Murray 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
managers. I don't remember why
R. David Murray 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 about the
R. David Murray 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
python. We *could* change it in
R. David Murray added the comment:
I'll let Steve be the one to close this, but it sounds like this isn't even a
doc bug (ie: it is standard window's practice).
--
___
Python tracker
<https://bugs.pyt
R. David Murray added the comment:
Note that in the equivalent issue raised against virtualenv, the concern was
raised that some old sh-like shells might not support this syntax, but it was
pointed out that it is part of the posix standard. I'm not arguing for or
against here, just n
R. David Murray added the comment:
Are you aware of PEP 539? (See issue 25658 for discussion.) I haven't
followed that closely, but I imagine this issue is at least related.
--
nosy: +r.david.murray
___
Python tracker
<https://bugs.py
R. David Murray added the comment:
Assuming 3.4 is packagable using msi and hg is the only problem, I presume you
could use an hg-git adapter to get an hg checkout to build from.
--
nosy: +r.david.murray
___
Python tracker
<https://bugs.python.
R. David Murray added the comment:
A system with no hostname can be considered to be improperly configured, but it
doesn't look like this would weaken the test, so I think it is OK.
--
___
Python tracker
<https://bugs.python.org/is
R. David Murray added the comment:
I think this is reasonable, but do note that this is covered in 16.4.4.2, and
the fact that help exits is actually a property of help, not parse_args. That
is, the docs are correct and complete as they stand, but I agree that it would
be helpful to have
R. David Murray added the comment:
I'm pretty hesitant to make this kind of change in python2. I'm going to punt,
and let someone else make the decision. Which means if no one does, the status
quo will win. Sorry about that.
--
Change by R. David Murray :
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
R. David Murray added the comment:
Well, it would be an "unenhancement" (reducing functionality :).
What I think it would be classed as is an API bug fix, and those generally can
be made only in feature releases. I can imagine code depending on this
ability, since we have had c
Change by R. David Murray :
--
nosy: +eric.snow
___
Python tracker
<https://bugs.python.org/issue31655>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Sorry, not broken, it just raises a type error, which is appropriate :)
--
___
Python tracker
<https://bugs.python.org/issue31
R. David Murray added the comment:
What happens when you apply a bitwise operation to two bytes objects of unequal
length?
Since the answer to that question is not obvious, we simply don't support the
operation.
If you want to make a proposal for this the python-ideas mailing list wou
R. David Murray added the comment:
virtualenv is not part of the standard library. What happens if you use venv
instead?
--
nosy: +r.david.murray
___
Python tracker
<https://bugs.python.org/issue31
R. David Murray added the comment:
We generally wait for something a bit stronger than "tentatively" before adding
a mime type (ie: an actual submission to the relevant standards channel).
--
nosy: +r.david.murray
___
Python track
R. David Murray added the comment:
3.5 is in security-fix-only mode, and we use versions to indicate which
versions we plan to fix the bug in.
--
nosy: +r.david.murray
versions: -Python 3.5
___
Python tracker
<https://bugs.python.org/issue31
R. David Murray added the comment:
Yes, redistributors sometimes backport non-security fixes if they consider them
important enough.
Note that I haven't evaluated the merits of this issue, and there is a related
issue about how 2to3 finds its fixers that this may overlap
R. David Murray added the comment:
Yes, if/when it goes in it will go in to all currently maintained versions.
I've adjusted 'versions' accordingly.
--
versions: -Python 3.4, Python 3.5, Python 3.6
___
Python tracker
<https
R. David Murray added the comment:
Yes, this conforms to Python's namespace/scoping rules: nested scopes are
allowed to reference (but not assign to) variables from the global scope even
without a 'global' declaration.
--
nosy: +r.david.murray
resolution: -&g
R. David Murray added the comment:
If you are talking about Gerhard, if he was still around you'd probably get a
similar response, but he hasn't been around much. So this is somewhat of an
orphaned module currently and it takes longer for an issue to get traction.
One of the dr
R. David Murray added the comment:
Given the title, are you saying that it works if you omit the
stderr=subprocess.STDOUT? At the beginning you say you are using an authorized
key and mux so you don't need to enter a password, and at the end you say it
works fine if the MUX is created
R. David Murray added the comment:
Based on the paragraph following the example, I don't think client_thread is a
threading.Thread, and 'run' is meant to be a generic representation of a
possible API. Since Threads do have a 'run' method, this is certainly
potenti
R. David Murray added the comment:
Or maybe instead of client_handler/run, it should be something like
handle_client_asynchronously(clientsocket).
--
___
Python tracker
<https://bugs.python.org/issue31
R. David Murray added the comment:
This is fixed in python3. Do you have a use case for 2.7 or are you just
noticing?
--
nosy: +r.david.murray
versions: -Python 3.4
___
Python tracker
<https://bugs.python.org/issue31
R. David Murray added the comment:
3.4 and 3.5 are in security maintenance mode only, and this is not a security
bug. This was fixed in master (3.7) as a result of issue 25324. The decision
there was made to not backport it because no one had complained about the
problem previously. Now
R. David Murray added the comment:
Which example? (It might be easiest to just generate a PR with your suggested
improvement.)
--
nosy: +r.david.murray
___
Python tracker
<https://bugs.python.org/issue31
R. David Murray added the comment:
Where did you get your installer? I don't find any references to 'backports'
in our repo, other than a couple of places in the docs where the word appears.
I also don't understand the relationship between your MyPackages and a
backpo
R. David Murray added the comment:
What is "the backports module"? I still don't understand what a backports
directory, that I don't think our installer creates, has to do with your
MyLibraries directory.
I'm sorry that I'm having trouble following your expla
R. David Murray added the comment:
I think there needs to be an easy way to turn off the warnings while running
tests, as well. I don't want to be bothered by those messages when testing
parts of my package that are consciously using the provisional features.
But really, I agree with
R. David Murray added the comment:
That's why I said set on by default by the test harnesses. The opt in would be
done by the standard testing tools, not directly by the programmer. That's how
deprecation warnings work now.
--
___
Pyth
R. David Murray added the comment:
I imagine we could make it controlled by the same setting that controls
deprecation warnings, with some way to differentiate them if you really need
to. I forget exactly how that warning control works, so maybe that would be
awkward, but I wouldn'
R. David Murray added the comment:
Nick says: "Neither of those situations can be encountered simply by running an
existing *application* on a newer version of Python".
I fail to see the operational difference between running an application on a
newer version of Python and d
R. David Murray added the comment:
Ah, so backports is a package on pypi. You should report this problem wherever
they do their bug tracking. It is *possible* there is some problem in 2.7 on
windows, but it is much more likely to be a bug in backports on windows. In
sort, python does not
R. David Murray added the comment:
This tracker is for reporting bugs in python. If you want to report a problem
with the tracker, please use the 'report tracker problem' link in the left
column. (That said, I thought the error message you show in the screenshot was
fixed by
R. David Murray added the comment:
I fixed the title for you, otherwise this looks like a duplicate of issue 31732.
--
nosy: +r.david.murray
title: Add TRACE level to the logging module -> Add NOTICE level to the logging
module
___
Python trac
R. David Murray added the comment:
Most likely an error in your program logic, I'm afraid. This isn't a forum for
getting help, you should try the python-list mailing list. (If you do find a
bug, you can then open an issue with details.)
--
nosy: +r.da
R. David Murray added the comment:
I'm not arguing against the rejection, but I want to mention a point in
relation to Raymond's statement "five levels have sufficed for a long and that
the need for finer distinctions almost never arises in practice". In thinking
abou
R. David Murray added the comment:
I think in the echo examples the 'with conn' block should be indented and a
'with s:' added around it.
The network sniffer should probably use a with statement with the
created socket.
The CAN example ends only on ctrl-C, and could go i
R. David Murray added the comment:
Heh, of course the socket server also only ends with ctl-C. And I misread the
CAN example, it won't spin because the read isn't wrapped in a try/except. So
yes, that should use a with on the socket as well, since the with will close
the socket
R. David Murray added the comment:
"Safely evaluate an expression node or a string containing a Python expression."
The behavior you are citing matches that documentation, as far as I can see.
1+1 is an expression involving supported literals.
--
nosy: +r.da
R. David Murray added the comment:
Does the patch in gh-3488 fix this? I think it should, or if it doesn't that's
a bug in the PR patch.
--
___
Python tracker
<https://bugs.python.o
R. David Murray added the comment:
You are correct, that is a bug. Presumably I forgot to check for non-ascii
when the parameter value doesn't need to be folded. I'm not sure when I'll
have time to look at this, unfortunately :(. If you can see how to fix it, you
could subm
R. David Murray added the comment:
Great, thank you for that research. And yes, that's exactly why __str__ uses
utf8=True, the "picture" of the message is much more readable. I will commit
that PR soon.
--
___
Python
R. David Murray added the comment:
The python standard library does not parse files, nor does it have a _parse_rfc
message. You say you reported the problem you are having to "the program's
maintainer", and that is appropriate. There does not appear to be anything in
this re
R. David Murray added the comment:
I meant the python standard library datetime package doesn't parse files, of
course :) Other parts of the stdlib certainly do parse files.
--
___
Python tracker
<https://bugs.python.org/is
R. David Murray added the comment:
It may be a proper noun, but it is conventionally spelled with a lowercase
letter when referring to the type/object. It would be spelled with an upper
case letter when referring to the *standard*.
--
___
Python
R. David Murray added the comment:
In this case I think the cost of editing for consistency may be higher than the
value, especially since as you say there are ambiguous cases.
--
___
Python tracker
<https://bugs.python.org/issue31
R. David Murray added the comment:
Ionel please give commenters the benefit of the doubt. In this case, Raymond
is merely articulating our policy: if something is in pre-PEP stage we don't
generally keep issues open in the tracker. We open issues for PEPs when they
get t
R. David Murray added the comment:
If you run
mpirun -np 4 myexe.x moreargs; echo $?
in /bin/sh, what do you see? You also might try to make sure it is the same
mpirun and the same myexe.x that is being called in both cases (it is the
mpirun return code you are seeing).
--
nosy
R. David Murray added the comment:
The patch looks good to me if someone wants to make a PR out of it. If you
wouldn't mind digitally signing the CLA, Peter, that would make PSF legal
happy, though I doubt a one sentence doc patch is really an
R. David Murray added the comment:
It is not obvious that this is a bug. Why should None be a valid value for 'in
network'?
--
nosy: +r.david.murray
___
Python tracker
<https://bugs.python.o
R. David Murray added the comment:
Duplicate of #25655. Any concrete proposals for how to make this better are
welcome.
--
nosy: +r.david.murray
resolution: -> duplicate
stage: -> resolved
status: open -> closed
superseder: -> Python errors related to failures loadin
R. David Murray added the comment:
I believe we currently have a policy that the python standard library will not
include type annotations, that those are provided by typeshed.
--
nosy: +r.david.murray
___
Python tracker
<https://bugs.python.
R. David Murray added the comment:
Yes, that's the way it works (and is intended to work, for performance
reasons). The documentation on this could be improved...while it does say
globals must be a dict and that locals can be any mapping object, it does it in
a sentence that is
R. David Murray added the comment:
>From the linked email:
> That way ad hoc scripts and the REPL will get warnings by default,
> while zipapps and packages can avoid warnings by keeping their
> __main__.py simple, and importing a CLI helper function from another
> module. Entr
R. David Murray added the comment:
I'm not sure what licensing issues you are talking about, but setting up a
buildbot shouldn't normally run into any. As long as you have a license to the
run the OS, the fact that you are using it to receive jobs from our build
master an
R. David Murray added the comment:
Can you please give examples of what you think the problem is?
--
nosy: +r.david.murray
___
Python tracker
<https://bugs.python.org/issue31
R. David Murray added the comment:
It was never about putting the interests of the app developers first, it was
about putting the interests of the users first: not being pestered by seeing
deprecation warnings they can't do anything about.
So yeah, maybe a PEP explaining the logic wou
R. David Murray added the comment:
This is a duplicate of #27794.
--
nosy: +r.david.murray
resolution: -> duplicate
stage: -> resolved
status: open -> closed
superseder: -> setattr a read-only property; the AttributeError should show
the attribute that failed
versions:
R. David Murray added the comment:
This is not something it is worth complicating the dict API or collections for.
If you want the feature in your code, implement your subclass in your own
utility library.
If you disagree with this decision, please bring it up on the python-ideas
mailing
R. David Murray added the comment:
> Why would mypy, flake8 or pip emit DeprecationWarnings?
Because they use python features that get deprecated, and the python the user
is using to run them gets upgraded. Now, those particular tools probably will
get updated quickly, but other tools w
R. David Murray added the comment:
My *personal* memory (as in, the reason I gave a sigh of relief when we made
this change) was other tools, regardless of what core's rationale was :) (If I
remember correctly it was some sysadmin-type tool I was using just about every
R. David Murray added the comment:
FWIW, I find the version without the spaces to be more readable (but I don't
find annotations to be readable in general, so my opinion may not be worth much
:)
--
nosy: +r.david.murray
___
Python tracker
&
R. David Murray added the comment:
Agreed.
--
___
Python tracker
<https://bugs.python.org/issue32018>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
It looks like Brotli is a de-facto standard (RFC 7932 is an informational RFC),
and it says the IANA registry has been updated. However, this appears to be
http-only, with no corresponding program used for compression of files, and
thus no "file exte
R. David Murray added the comment:
OK, so there are "real" filenames that have .br on the end? That wasn't clear
from the RFC and discussions I found. Based on the documentation, br is for
use in the Content-Encoding header.
What does aiohttp do when it gets a brotli enco
R. David Murray added the comment:
Note, I'm not saying we shouldn't do this, I'd just like to get good
documentation of why linked to this issue.
--
___
Python tracker
<https://bugs.pyt
R. David Murray added the comment:
Hmm. OK, the docs do say that value should be usable as a content-encoding
header.
However, absent any sort of program that actually does brotli encoding/decoding
to and from files, this would be essentially useless based on the aiohttp's
algorithm (o
R. David Murray added the comment:
Can you reproduce this without your PosArgsParser?
--
nosy: +r.david.murray
___
Python tracker
<https://bugs.python.org/issue32
R. David Murray added the comment:
OK, bouncing around from those URL I finally found this:
https://github.com/google/ngx_brotli/issues/28
That indicates unambiguously that someone does expect files to be
pre-compressed on the server and that the main brotli package provides a cli
tool (I
R. David Murray added the comment:
Ah, yes, I'd managed to forget about that issue, even though I was the one that
finally committed the fix.
So, the alternate parser will be in 3.7. In the meantime you can grab the code
from the commit and put it in a local file, I think. You'll
R. David Murray added the comment:
I think it is an interesting idea. Let see what other people think.
--
nosy: +r.david.murray
___
Python tracker
<https://bugs.python.org/issue32
3301 - 3400 of 10554 matches
Mail list logo
