David Wilson added the comment:
The original diff is attached here (per the old process) so others can find it,
and the PR+fork are closed, as carrying a fork in my GitHub for 4 months has
non-zero cost. I'm presently more interested in having a clean GH account than
carrying around
R. David Murray added the comment:
Right, those absolutely are valid addresses. A resolver will normally look up
a name with an internal dot first as if it were an FQDN, but if it does so and
does not get an answer it will then look it up again as a "local" address
(appendi
New submission from David :
Here is the link to register.
From: report=bugs.python@roundup.psfhosted.org
on behalf of Python tracker
Sent: Thursday, July 11, 2019 8:59 PM
To: davedro...@hotmail.com
Subject: Complete your registration to Python tracker
R. David Murray added the comment:
The display name is a phrase, and a phrase is a sequence of words, and a word
is either a quoted string or an atom. So it is legal to mix quoted strings and
encoded words in a display name. I'd vote to do whichever one is easier to
implement :) (I
R. David Murray added the comment:
FYI, it would have been most helpful if you had posted your example in the
issue text instead of as an attached file, as it explains the problem better
than your text does :)
Here is a minimal reproducer:
>>> m = EmailMessage(policy=strict)
&g
R. David Murray added the comment:
This problem is the whole reason "mangle_from" exists in the email library...
--
___
Python tracker
<https://bugs.python.o
R. David Murray added the comment:
Note that the reporter indicated that the message was an instance of
EmailMessage (the new API). You'd need to use policy-default to get that using
message_from_string. But yes, this was fixed in another issue.
--
stage: patch review -> resol
R. David Murray added the comment:
BareQuotedString implies the new API is being used, though that was not made
clear in the report. However, unlike the other recently closed issue, this one
was in fact fixed (and I have a vague memory of reviewing the PR):
>>> m = message_fr
R. David Murray added the comment:
The fact that the original report mentions HeaderParserError implies that the
new API is being used, though the report didn't make that clear. The problem
still exists:
>>> m = message_from_string("To: :Foo
>>> \n\n&
R. David Murray added the comment:
"But - what are we solving for here?" I'll tell you what my fairly common use
case is. Suppose I have some test infrastructure code, and I want to make some
assertions in it. What I invariably end up doing is passing 'self' into the
infr
Change by David CARLIER :
--
title: mmap module: add MAP_ALIGNED_SUPER FreeBSD constant -> mmap module: add
MAP_ALIGNED_SUPER FreeBSD and MAP_CONCEAL OpenBSD constants
___
Python tracker
<https://bugs.python.org/issu
Change by David Carlier :
--
nosy: David Carlier
priority: normal
pull_requests: 14424
severity: normal
status: open
title: mmap module add OpenBSD MADV_CONCEAL flag
versions: Python 3.9
___
Python tracker
<https://bugs.python.org/issue37
Change by David CARLIER :
--
components: Extension Modules, FreeBSD
nosy: devnexen, koobs
priority: normal
pull_requests: 14329
severity: normal
status: open
title: mmap module, adding new constant
versions: Python 3.9
___
Python tracker
<ht
David K. Hess added the comment:
Thank you Steve!
Nice to see this one make it across the finish line.
--
___
Python tracker
<https://bugs.python.org/issue4
New submission from David Carlier :
Removing little dead code part.
--
messages: 345674
nosy: David Carlier
priority: normal
pull_requests: 13959
severity: normal
status: open
title: AST - code cleanup
versions: Python 3.9
___
Python tracker
<ht
New submission from David Wang :
If you call setLevel() on a subclass of logging.Logger, it does not reset the
cache for that logger. This mean that if you make some logging calls, then call
setLevel(), the logger still acts like it still has its old level. See the
attached python file
David Jones added the comment:
I believe the issue is only triggered if you actually have some suspicious
markup in your documentation (which is why your plain build on Sphinx 2 appears
to work).
Remove some lines from Doc/tools/susp-ignored.csv to trigger it.
--
nosy: +drj
Change by David Carlier :
--
components: Interpreter Core
nosy: David Carlier
priority: normal
pull_requests: 13714
severity: normal
status: open
title: thread native id netbsd support
versions: Python 3.9
___
Python tracker
<ht
David Radcliffe added the comment:
I understand that pure mathematics is not the primary use case. But I would
expect that math.comb() would be used to implement mathematical formulas.
As a simple example, the number of edges in a complete graph on n vertices
is binomial(n, 2), and this should
David Radcliffe added the comment:
I think that binomial(n, k) should return 0 when k > n or k < 0. This is a
practical consideration. I'm concerned about evaluating sums involving binomial
coefficients. Mathematicians are often rather loose about specifying the upper
and lower
New submission from David Carlier :
Following up on bpo-36084
--
messages: 343896
nosy: David Carlier
priority: normal
pull_requests: 13549
severity: normal
status: open
title: Adding native id support for openbsd
versions: Python 3.8
___
Python
Change by David Carlier :
--
pull_requests: +13548
pull_request: https://github.com/python/cpython/pull/13654
___
Python tracker
<https://bugs.python.org/issue36
Change by David Carlier :
--
pull_requests: +13533
pull_request: https://github.com/python/cpython/pull/13633
___
Python tracker
<https://bugs.python.org/issue33
David Bolen added the comment:
Yeah, I think you're right.
It looks like without an explicit code, it won't propagate the result as the
exit code of cmd itself for those cases where cmd does exit (which would
include the buildbots
David Bolen added the comment:
I've been investigating issues with test failures on my Windows buildbots
seemingly not showing up in the master's web interface (but just showing
warnings), and it appears likely due to this change.
For example, test_urllib (a test problem from issue 36948
R. David Murray added the comment:
New changeset 0416d6f05a96e0f1b3751aa97abfffe6d3323976 by R. David Murray (Miss
Islington (bot)) in branch '3.7':
bpo-27737: Allow whitespace only headers encoding (GH-13478) (#13517)
https://github.com/python/cpython/commit
R. David Murray added the comment:
Nevermind, I was testing with the wrong version of python. This bug was
introduced somewhere after 3.4 :(
>>> from email.message import EmailMessage
>>> m = EmailMessage()
>>> m['Subject'] = 'Hello Wörld! Hello Wörld! Hel
R. David Murray added the comment:
Can you demonstrate the problem with an actual email object?
header_store_parse is not meant to be called directly.
--
___
Python tracker
<https://bugs.python.org/issue36
R. David Murray added the comment:
Thanks.
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.7, Python 3.8 -Python 3.4, Python 3.5, Python 3.6
___
Python tracker
<https://bugs.python.or
R. David Murray added the comment:
New changeset ef5bb25e2d6147cd44be9c9b166525fb30485be0 by R. David Murray
(Batuhan Taşkaya) in branch 'master':
bpo-27737: Allow whitespace only headers encoding (#13478)
https://github.com/python/cpython/commit/ef5bb25e2d6147cd44be9c9b166525fb30485be0
David Bolen added the comment:
Oh, and just for historical purposes, it looks like the root cause was that the
nturl2path.pathnametourl forces an uppercase drive letter. So that's where the
inconsistency in the test got introduced.
--
___
Python
David Bolen added the comment:
Yes, PR 13476 tested locally on the Win10 builder resolves the error.
--
___
Python tracker
<https://bugs.python.org/issue36
David Bolen added the comment:
Since this patch was introduced to the 3.x branch my Windows 7 and 10 buildbots
have been failing in test_urlopener_retrieve_file. See
https://buildbot.python.org/all/#/builders/3/builds/2661 for the first such
failure on the Win10 worker.
The problem
Change by David Lord :
--
nosy: +davidism
___
Python tracker
<https://bugs.python.org/issue35894>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
New changeset feac6cd7753425fba006e97e2d9b74a0c0c75894 by R. David Murray
(Abhilash Raj) in branch 'master':
bpo-33524: Fix the folding of email header when max_line_length is 0 or None
(#13391)
https://github.com/python/cpython/commit
R. David Murray added the comment:
I don't see that line of code in unstructured_ew_without_whitespace.diff.
Oh, you are referring to his monkey patch. Yes, that is not a suitable
solution for anyone but him, and I don't think he meant to imply otherwise
R. David Murray added the comment:
A cleaner/safer solution here would be:
tok, *remainder = _wsp_splitter(value, 1)
if _rfc2047_matcher(tok):
tok, *remainder = value.partition('=?')
where _rfc2047_matcher would be a regex that matches a correctly formatted
encoded word
R. David Murray added the comment:
Right, one of the fundamental principles of the email library is that when
parsing input we do not ever raise an error. We may note defects, but whatever
we get we *must* parse and turn in to *something
R. David Murray added the comment:
Good point about the backward compatibility. Yes I agree, I think raising the
error is probably better. A deprecation warning seems like a good path
forward...I will be very surprised if anyone encounters it, though
R. David Murray added the comment:
As for the other, I don't see the need for a custom error. It's a ValueError
in my view. I wouldn't object to it strongly, but note that this error is
content dependent. If there's nothing to encode, you can "get away with" a
shorter maxlen.
R. David Murray added the comment:
Can you demonstrate the parsing error? maxlen should have no effect during
parsing.
--
___
Python tracker
<https://bugs.python.org/issue36
R. David Murray added the comment:
Thank you. I don't believe this is a security issue.
--
___
Python tracker
<https://bugs.python.org/issue34424>
___
___
Pytho
R. David Murray added the comment:
Not a security issue, no. This isn't C where a stack overflow can give an
attacker a vector for injecting arbitrary code.
Per the Parser contract ("raise no exceptions, only register defects"), this
should, as you say, registe
R. David Murray added the comment:
Approved and merged. Cheryl, can you shepherd this through the backport
process, please? I'm contributing infrequently enough that I'm not even sure
which version we are on :)
--
___
Python tracker
<ht
R. David Murray added the comment:
New changeset 45b2f8893c1b7ab3b3981a966f82e42beea82106 by R. David Murray (Jens
Troeger) in branch 'master':
bpo-34424: Handle different policy.linesep lengths correctly. (#8803)
https://github.com/python/cpython/commit
R. David Murray added the comment:
In order to legitimately have a non-ascii localpart, you *must* be using
RFC6532 and RFC6531. In the email package you do this by using
policy=SMTPUTF8, or setting utf8=True in your custom Policy. In smtplib you do
this by specifying smtputf8
David Collins added the comment:
Sorry for being so abrupt you are correct .
The code I was working from was a university professors and not my own, I
understood better thanks steve. I wasn’t passing a return value yet and the
professors work was overwriting the list.
I do apologise
David Collins added the comment:
So what your saying is that python is unable to pass a negative number between
modules and you don’t think that this is an issue .
Sent from Mail for Windows 10
From: Terry J. Reedy
Sent: Friday, 10 May 2019 7:21 PM
To: coldy...@gmail.com
Subject
David Collins added the comment:
This is an issue with python
On Fri, 10 May 2019 at 3:52 pm, SilentGhost wrote:
>
> Change by SilentGhost :
>
>
> --
> components: -IDLE
>
> ___
> Python tracker
> <h
David Collins added the comment:
Not the coding
On Fri, 10 May 2019 at 3:53 pm, David Collins wrote:
> This is an issue with python
>
> On Fri, 10 May 2019 at 3:52 pm, SilentGhost
> wrote:
>
>>
>> Change by SilentGhost :
>>
>&
David Collins added the comment:
I have tested this in the Mac and PC versions of IDLE as well as in Spyder
using Ipython.
--
___
Python tracker
<https://bugs.python.org/issue36
New submission from David Collins :
program_data.py file contains a list
import list_function
str_list4 = ['i', 't']
str_list4 = list_function.insert_value(str_list4, 's', -1)
print(str_list4)
list_function.py file
def insert_value(my_list, value, insert_position):
counter = 0
david awad added the comment:
It's been a while since then but I really think we can get this fix merged in
the next two weeks or so.
Can someone give this another look?
I had a quick question for Serhiy Here:
https://github.com/python/cpython/pull/8319#discussion_r273539593
If we could
David Bolen added the comment:
I think I'm the wrong David for this...
--
___
Python tracker
<https://bugs.python.org/issue36749>
___
___
Python-bugs-list mailin
David Bolen added the comment:
I should mention that a high level of test parallelism on the part of my worker
might have be a contributing factor in this most recent case.
The worker was recently upgraded to a faster 4-core VM, but with limited I/O.
In a test run the test processes
R. David Murray added the comment:
This is one of the infelicities of the translation of the old API to python3:
'get_payload(decode=True)' actually means 'give me the bytes version of this
payload", which in this case is the utf-8, which is what you got.
get_payload() means &qu
David Bolen added the comment:
Ok, I've resolved this, and the linker errors did actually point at the root
issue. They show trying to link extensions against
/usr/local/lib/libpython2.7.a which was my test static build of 2.7.16.
Arguably this seems an issue in the buildbot build process
David Bolen added the comment:
Yes, it appears most likely to be the worker environment. I did upgrade the
kernel in between builds 250 (good) and 251 (bad), but reverting that still
fails, even with the same commit as in build 250.
My current suspicion is that a test I did recently
David Bolen added the comment:
I just noticed that my last message referenced the wrong commit. My test
failures were against commit f13c5c8b9401a9dc19e95d8b420ee100ac022208 (the same
as Victor).
--
___
Python tracker
<https://bugs.python.
David Bolen added the comment:
Eric, I'm also seeing the same Win7 and Win10 worker failures with commit
b75b1a350 as last time (test_multiprocessing_spawn on both, and test_io on
Win7).
For test_multiprocessing_spawn, it fails differently than Victor since no core
file is generated, but I
R. David Murray added the comment:
I do, and sure. I won't be able to review it, though :(
--
___
Python tracker
<https://bugs.python.org/issue19770>
___
___
David Chin added the comment:
OS: RHEL 6.8
I installed OpenSSL 1.1.1b from source into /usr/local. Because it's RHEL, the
libs are in /usr/local/lib64 (as set up by default with the OpenSSL "make
install") which the configure script does not seem to know about.
My workarou
David Bolen added the comment:
Ok, I've verified that on a Win7 system with SP1 but without KB2533625 I get
the expected block screen at startup.
On my worker (SP1 with KB2533625) it proceeds to the regular installation main
dialog.
I'm attaching a copy of the install log in the blocking
David Bolen added the comment:
I can help with a Win7 test of the installer, but my currently available
systems are all 32-bit - any chance at a 32-bit version of the installer?
--
___
Python tracker
<https://bugs.python.org/issue36
David Bolen added the comment:
I just wanted to acknowledge that this was breaking on my Windows 7 builder
(with a bad DLL load parameter in both pythoninfo and test steps).
It looks like I was missing the required KB2533625 (the machine is mostly a
virgin SP1 install), so I've installed
New submission from David Corbett :
In `unicodedata`, the functions `lookup` and `name` have some bugs and
inconsistencies.
`lookup` matches case-insensitively, except for the algorithmic names of Hangul
syllables and CJK unified ideographs, which must be in all caps. The
documentation does
R. David Murray added the comment:
Not sure what you mean by "depend on that structure". A quick grep
shows the only stdlib modules that use mimetimes are urllib and
http.server.
Backward compatibility will of course be a significant
R. David Murray added the comment:
That link should do for our purposes here.
The fact that it is an 'x-' mimetype means it has not been approved at
any level. There might be an in progress application to the mimetype
registry, but if so the web site doesn't mention it anywhere obvious.
I'm
R. David Murray added the comment:
Can you provide some links to relevant RFCs or other official documents?
--
___
Python tracker
<https://bugs.python.org/issue36
New submission from David Hagen :
If a dataclass is `frozen` and has `__slots__`, then unpickling an instance of
it fails because the default behavior is to use `setattr` which `frozen` does
not allow.
```
import pickle
from dataclasses import dataclass
@dataclass(frozen=True)
class
Change by David Chin :
--
nosy: +hairygristle
___
Python tracker
<https://bugs.python.org/issue35473>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from David Wilson :
Not sure if this is worth reporting..
p = os.popen('sleep 1234')
os.wait3(os.WNOHANG)
os.wait3(os.WNOHANG)
os.wait3(os.WNOHANG)
Notice struct rusage return value. When wait3() succeeds on Linux, but no child
was waiting to be reaped, is not updated
Change by R. David Murray :
--
stage: -> needs patch
___
Python tracker
<https://bugs.python.org/issue36261>
___
___
Python-bugs-list mailing list
Unsubscrib
R. David Murray added the comment:
We could also change both of them to be more correct and say something like "If
you are reading this your browser probably does not support MIME, and you will
have to find a MIME aware email client or decode the message by hand." That
demonst
R. David Murray added the comment:
I don't see "several", can you point to the other instances? I only see that
one case you mention (for reference, it is in Doc/includes/email-mime.py). The
other case of setting preamble is actually correct ("You will not see this in a
David Bolen added the comment:
If I can help with testing or builder access or anything just let me know. It
appears that I can pretty reliably trigger the error through just the
individual tests (test_daemon_threads_shutdown_std{out,err}_deadlock) in
isolation, which is definitely less
David Bolen added the comment:
I suspect changes for this issue may be creating test_io failures on my windows
builders, most notably my x86 Windows 7 builder where test_io has been failing
both attempts on almost all builds. It fails with a lock failure during
interpreter shutdown
David Ford (FirefighterBlu3) added the comment:
i have a fully built patch and personally tested (i use it 24/7) but
haven't done test_* yet as was requested
On Thu, Feb 28, 2019 at 9:16 PM Windson Yang wrote:
>
> Windson Yang added the comment:
>
> sls, are you working on this
Change by R. David Murray :
--
nosy: +sls
___
Python tracker
<https://bugs.python.org/issue29539>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Sorry, that should be #29539.
--
superseder: Deprecate string concatenation without plus -> [smtplib] collect
response data for all recipients
___
Python tracker
<https://bugs.python.org/issu
R. David Murray added the comment:
Thanks for the PR, but this is a duplicate of #29539, which I think has a
better API proposal. Since the original author never actually submitted a PR
there, perhaps you could pick up his work (after pinging the issue).
--
resolution
Change by R. David Murray :
--
versions: -Python 3.6
___
Python tracker
<https://bugs.python.org/issue34464>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
I'm afraid I don't have time to parse through the file you uploaded. Can you
produce a pull request or a diff showing your fix? And ideally some added
tests :) But whatever you can do is great, if you don't have time maybe
someone else will pick it up
R. David Murray added the comment:
Since Address itself renders it correctly (str(address)), the problem is going
to take a bit of digging to find. I'm guessing the quoted_string atom is
getting transformed incorrectly into something else at some point during the
folding
R. David Murray added the comment:
Well, "display" in the context of email includes looking at the raw email
serialized as a text file. This is something one can do in most mailers. I use
nmh as my mailer, which only shows raw headers, so I myself would be personally
affected
R. David Murray added the comment:
The rules are: lines should be less than 78 characters; and that lines may be
broken only at FWS (folding whitespace), not in the middle of words. Putting
these rules together, you get the result that the email library produces.
"Conservative in wha
R. David Murray added the comment:
Also note that you might want to switch to the new API, the folder it uses is
smarter, although in this case I think it will produce the same result because
it is the "best" rendering of the header under the cir
R. David Murray added the comment:
That is correct folding. The word is too long to fit within the 78 character
default if put on the same line as the label, but does fit on a line by itself.
If Outlook can't understand such a header it is even more broken than I thought
it was :( You can
Change by R. David Murray :
--
nosy: -r.david.murray
___
Python tracker
<https://bugs.python.org/issue20767>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
I'm closing this in favor of #35799 because someone has to first make a
remove-or-fix decision, which is mentioned there.
--
resolution: -> duplicate
stage: patch review -> resolved
status: open -> closed
superseder: -> f
R. David Murray added the comment:
I'm neutral on fixing versus removing philosophically. Since fixing is actually
the least effort in this case, I think practically I favor fixing.
--
___
Python tracker
<https://bugs.python.org/issue35
David Heiberg added the comment:
I have submitted a PR for the documentation. Hopefully this is enough to
resolve the issue and close.
--
___
Python tracker
<https://bugs.python.org/issue35
R. David Murray added the comment:
There has been considerable rewriting of the header handling code since I filed
this. I would not be surprised if the issue is no longer valid. If you want
to double check, look for the places that the headers attribute is created in
the various handlers
Change by David Heiberg :
--
nosy: +dheiberg
___
Python tracker
<https://bugs.python.org/issue5038>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Yes, the correct solution would be to write an actual parser for headers
containing message ids. All the pieces needed to do this already exist in
_header_value_parser, it "just" needs a function that glues them together in
the right order, and
R. David Murray added the comment:
Actually, thinking about it some more, you are right. If PureProxy doesn't at
least function according to the current docs it should either be fixed or we
should deprecate-and-remove it in 3.8 or 3.9 (depending on how strongly people
feel about
R. David Murray added the comment:
The mailman proxy has been abandoned for a long time now, so no fixes there. I
have some sympathy to fixing PureProxy, but since the stdlib itself doesn't use
it, not a lot :)
At some point we will start cleaning up old code (probably a while after 2.7
R. David Murray added the comment:
It is documented as deprecated, but only in the 'seealso' note at the top. I
think it would be reasonable to open an issue to add an actual 'deprecated'
ReST tag to the docs.
For your 1 and 2, the stdlib smtpd forwarding is also blocking; that code
R. David Murray added the comment:
Thanks for being willing to work on this, but smtpd is deprecated in favor of
aiosmtpd (which is not part of the stdlib). smtpd should really only be used
for internal stdlib testing, but it is retained for backward compatibility
reasons.
All
Change by David Heiberg :
--
pull_requests: +11374
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issue35701>
___
___
Python-
501 - 600 of 12771 matches
Mail list logo
