R. David Murray added the comment:
That sounds reasonable, if the debug output doesn't pollute the test run output.
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
I don't do much with the C API, but since your goal is to remove them from the
PyMODINIT_FUNC, I would think you could replace those entries with calls to
wrapper functions that issue the deprecation and then call the real fun
R. David Murray added the comment:
@dhess: do you want to work on the OrderedDict + correctly ordered hardcoded
lists solution?
--
___
Python tracker
<http://bugs.python.org/issue4
Changes by R. David Murray :
--
stage: test needed -> needs patch
versions: +Python 3.6, Python 3.7 -Python 2.7, Python 3.2, Python 3.3, Python
3.4
___
Python tracker
<http://bugs.python.org/iss
R. David Murray added the comment:
Our tooling and workflow is indeed dependent on github. We should repurpose
the current 'remote hg repo' to allow the entry of a non-github git repo, but
someone will have to write that code. In the meantime, if you upload a patch
generated
R. David Murray added the comment:
Ah, yes, that's a bug in our workflow we'll need to fix. The CLA signed on the
bug tracker is the ultimate authority, so we need some way to manually bypass
the bot for cases like this.
A committer should be able to bypass the problem and get
R. David Murray added the comment:
I think we are leaning strongly toward making no change here.
--
___
Python tracker
<http://bugs.python.org/issue29573>
___
___
David K. Hess added the comment:
Ok, I followed @r.david.murray's advice and decided to take a shot at this.
First, I noticed that I couldn't reproduce the non-deterministic behavior that
I reported above on the latest code (i.e. pre-3.7). After doing some research
it appears th
David K. Hess added the comment:
Pushed more commits so here's a branch compare:
https://github.com/python/cpython/compare/master...davidkhess:fix-issue-4963
--
___
Python tracker
<http://bugs.python.org/i
R. David Murray added the comment:
It's not the PSF, it's the dev team, and it is "just" a matter of tooling.
Which means help improving the tooling is welcome :)
--
___
Python tracker
<http://bug
R. David Murray added the comment:
I'm not entirely sure why some of the conversions are done they way they are,
but I do know that one goal is to make all of the line endings consistent,
whatever may be the case on disk. If you aren't modifing the mailbox, nothing
should happen.
R. David Murray added the comment:
It would be a white-box test, which I don't like, but it might be worth it to
write a test that would check that .sock is None, indicating that
close was called. You really can't check for no warning because when the
warning gets generated is e
R. David Murray added the comment:
Duh. (Smacks self on forehead).
Nevermind.
I'll approve the patch as is, since I can't see any good way to test it.
(I suppose that we could factor the __init__ method contents out into something
we could test, but I'm not going to push f
R. David Murray added the comment:
New changeset a083c8ee6cb89ca573fe10c4c1922e2fa69ceaa3 by R. David Murray
(jugglinmike) in branch 'master':
bpo-30160: Clarify intended usage of wfile (gh-1300)
https://github.com/python/cpython/commit/a083c8ee6cb89ca573fe10c4c1922e
R. David Murray added the comment:
Pinging the issue is exactly what you needed to do :) As I said on the PR, I'm
not set up to do backports yet so hopefully you or someone else will do those.
--
stage: -> backport needed
versions: +Python 3.5, Python 3.6, Py
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue29626>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
If I'm interpreted what the OP wrote correctly, he wanted the help text to not
show that the option takes an argument, but instead rely on the help text to
show that. That works for the option text, but it doesn't work for the
synopsis (the synops
R. David Murray added the comment:
The email package currently forces explicit IDNA use currently. The new
policies are supposed to support it automatically but I they currently don't.
I'm not sure we should add it to the old interface (parseaddr/formataddr) any
longer, but I do
R. David Murray added the comment:
In other words, this was a major standards screwup and we get to deal with the
consequences :(
All right, since I'm hardly likely to have time to deal with it anyway, we'll
just say that email isn't going to handle unicode domain names
R. David Murray added the comment:
Can you provide actual code that demonstrates the issue you are talking about?
--
nosy: +r.david.murray
versions: -Python 2.7
___
Python tracker
<http://bugs.python.org/issue30
R. David Murray added the comment:
That's actually a very good question. hasattr returns False, but is it
supposed to be an invariant that if dir returns a string hasattr should return
True and getattr should not return AttributeError? (Well, it might raise
AttributeError from insid
R. David Murray added the comment:
Thank you for linking to that Xiang. I had a vague memory of that discussion
but couldn't find it.
No, there is no bug here, but there is a question of whether or not there
*should* be a bug here (that is, is there a design bug) and if so how/where to
R. David Murray added the comment:
As I mentioned on the PR I think it should be a ValueError, and that the PR
also needs tests.
--
___
Python tracker
<http://bugs.python.org/issue24
R. David Murray added the comment:
replace_header has a different semantic than del-and-set (replace_header leaves
the header in the same location in the list, rather than appending it to the
end...that's it's purpose). If replace_header is throwing a key error, then I
guess we n
Changes by R. David Murray :
--
stage: -> needs patch
type: -> behavior
versions: +Python 3.6, Python 3.7 -Python 3.4
___
Python tracker
<http://bugs.python.org/i
R. David Murray added the comment:
Not only is it conforming, it is required, since the primary use (originally)
of the base64 module was in the email package, where generous interpretation of
the input is the standard.
This does not mean that adding a strict mode would be out of line, but
R. David Murray added the comment:
Actually, the API discussion may be short: we already have a 'validate' option,
whose spirit matches with this, so adding the check for the padding issue to
that of the non-alphabet characters check would seem to me to be quite
R. David Murray added the comment:
Can you provide a reproducer, please?
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue30566>
___
___
R. David Murray added the comment:
Yes, but we try to make it not possible to segfault the interpreter with pure
python code that isn't intentionally mucking with C-level stuff, so this is a
bug we would like to fix.
--
nosy: +r.david.m
Changes by R. David Murray :
--
resolution: fixed -> third party
___
Python tracker
<http://bugs.python.org/issue30572>
___
___
Python-bugs-list mailing list
Un
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
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 iss
Changes by R. David Murray :
--
nosy: -r.david.murray
___
Python tracker
<http://bugs.python.org/issue30574>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Ping the issue again next week if I don't get to it this weekend.
--
___
Python tracker
<http://bugs.python.org/is
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:
Either that or you aren't really running the make_server from
wsgiref.simple_server.
--
___
Python tracker
<http://bugs.python.org/is
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:
You don't need an eternal package, just decoding b'xn--w&' with punycode will
produce the traceback.
--
___
Python tracker
<http://bugs
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: -> resol
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
___
Pytho
Changes by R. David Murray :
--
resolution: -> not a bug
___
Python tracker
<http://bugs.python.org/issue30580>
___
___
Python-bugs-list mailing list
Un
R. David Murray added the comment:
I'm going to try to review this this weekend.
--
___
Python tracker
<http://bugs.python.org/issue27321>
___
___
Pytho
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 o
R. David Murray added the comment:
Looks like it just needs a NEWS entry.
--
___
Python tracker
<http://bugs.python.org/issue29478>
___
___
Python-bugs-list mailin
Changes by R. David Murray :
--
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
versions: +Python 3.7
___
Python tracker
<http://bugs.python.org/issue30
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 that
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
___
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
<http://bugs.python.org/is
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 ma
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
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
Change by R. David Murray :
--
nosy: +sls
___
Python tracker
<https://bugs.python.org/issue29539>
___
___
Python-bugs-list mailing list
Unsubscribe:
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
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 i
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
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:
Can you provide some links to relevant RFCs or other official documents?
--
___
Python tracker
<https://bugs.python.org/issue36
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 anywher
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:
I do, and sure. I won't be able to review it, though :(
--
___
Python tracker
<https://bugs.python.org/issue19770>
___
___
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(
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 in the
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/cpyt
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 track
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, re
R. David Murray added the comment:
Thank you. I don't believe this is a security issue.
--
___
Python tracker
<https://bugs.python.org/issue34424>
___
___
R. David Murray added the comment:
I believe so. For python3 I think it should only apply to the legacy API docs
(you would use set_content (directly or indirectly) in python3, not
set_payload). I've updated the versions.
--
versions: +Python 3.6, Python 3.7 -Python 3.2, Pytho
R. David Murray added the comment:
A better question might be: is there something in the embedding framework that
should initialize argv to the empty list? embedding framework here could have
two meanings: either the third party code, or the code that we provide for
supporting embedding
R. David Murray added the comment:
This is sounds like a variation on issue 30811.
--
nosy: +r.david.murray
___
Python tracker
<https://bugs.python.org/issue32
R. David Murray added the comment:
Given the reproducible builds angle, I'd say this was worth doing.
--
nosy: +r.david.murray
___
Python tracker
<https://bugs.python.org/is
R. David Murray added the comment:
Ah, I was just going to ask about that. I guess I'm -0 on the backport as
well. The other reproducible build stuff is only going to land in 3.7.
However, this is in a more general category than the pyc stuff, so I can see
the argument for backporti
R. David Murray added the comment:
Please provide a way to reproduce the problem you are observing. There is
insufficient information here so far to understand the problem.
--
nosy: +r.david.murray
___
Python tracker
<https://bugs.python.
R. David Murray added the comment:
I'll defer to Lukasz, but I don't believe this is a bug. An empty value and a
value of "" are equivalent in config.ini syntax, as far as I know.
--
nosy: +lukasz.langa
___
Python tracker
<
R. David Murray added the comment:
I'm not clear why we want a bug tracker issue for something that is still only
an idea. We generally *send* people to python-ideas when they propose
half-baked ideas here :) (Not actually saying your idea is half-baked, but it
clearly isn't f
R. David Murray added the comment:
This has been discussed previously. The nature of the 'name' attribute for
file objects is not really specified, so I'm not even sure what we would
document. Maybe just that it is unspecified.
--
nosy:
R. David Murray added the comment:
I believe you are correct that it is too late to modify the existing behavior.
Too many programs depend on it. As far as documenting, my point is that it is
*not specified* what the name attribute contains. It can contain literally
anything, depending on
Change by R. David Murray :
--
nosy: +pitrou
___
Python tracker
<https://bugs.python.org/issue32601>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
@guido: in roundup, by default anyone can change the issue title. I imagine he
is a new user who just didn't understand that he was doing so. (And indeed,
the account was created on 1/19).
--
___
Python tr
R. David Murray added the comment:
Ah, yes. When I said "this has been discussed previously", that's the issue I
was thinking of but couldn't find.
--
resolution: -> duplicate
stage: -> resolved
status: open -> closed
superseder: -> State clearly t
R. David Murray added the comment:
Maybe we could at least mention the issue (and perhaps link to samefile) in the
"General Properties" section?
--
nosy: +r.david.murray
___
Python tracker
<https://bugs.python.o
R. David Murray added the comment:
Could WindowsPath (as opposed to PureWindowsPath) call samefile as part of the
equality test? (I'm not familiar enough with pathlib to know if that is a
nonsense question.)
--
___
Python tracker
&
R. David Murray added the comment:
Note: I reviewed this a while ago but the review comments haven't been
addressed.
--
___
Python tracker
<https://bugs.python.org/is
R. David Murray added the comment:
Yes, it is.
--
stage: patch review -> resolved
status: open -> closed
type: crash -> behavior
___
Python tracker
<https://bugs.python.or
R. David Murray added the comment:
That isn't a bug. Python doesn't protect you from doing the wrong thing, in
general. On the other hand, it might be a worthwhile improvement to make it
read-only in this case. Especially since, as you point out, other seemingly
similar attribut
New submission from David Albert Torpey :
$ python3.5
Python 3.5.3 (v3.5.3:1880cb95a742, Jan 16 2017, 08:49:46)
[GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>>
R. David Murray added the comment:
Chason: that does look like a bug.
Mutable defaults are best to avoid, but if they are used read-only and not
passed down further it isn't a problem. send_message was modeled on sendmail,
and so copied it's use of defaults (which date from quite
R. David Murray added the comment:
Yep, this one might get closed as "as designed", too ;) cgitb has to cope with
something going wrong with trying to print out values, because there are a
number of ways to break that in Python, not just the one you are pointing to.
If you have
R. David Murray added the comment:
On Thu, 25 Jan 2018 15:18:01 +, Steven D'Aprano
wrote:
> On Thu, Jan 25, 2018 at 02:28:17PM +0000, R. David Murray wrote:
> The docstring for send_message does say
>
> If the sender or any of the recipient addresses contain non-AS
R. David Murray added the comment:
I think this requires a discussion on the python-ideas mailing list, since API
changes to Future need consideration in the asyncio context as well.
--
components: +Library (Lib) -Interpreter Core
nosy: +r.david.murray
type: -> enhancement
versi
R. David Murray added the comment:
It's probably enough to fix it. I fear that if we also change them in sendmail
we'll break someone's code, but maybe we should do that anyway, for 3.7 only.
--
versions: -Python 2.7, Python 3.4, Python
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:
I don't think this is a bug. There are many ways to lie in Python. If your
object lies, it is on your head when things break :) On the flip side, the
ability to lie is very handy in many circumstances, and is often a case of duck
typing rather than
R. David Murray added the comment:
See also issue 26923, but I think this problem is different.
--
nosy: +r.david.murray
___
Python tracker
<https://bugs.python.org/issue32
R. David Murray added the comment:
Yes.
There's this thing called Postel's Law that says you should be generous in what
you accept and careful in what you emit. So most MTAs and MUAs try very hard
to guess what a non-RFC-compliant email is trying to say, which includes
allow
R. David Murray added the comment:
What we need for this issue is someone volunteering to writing the code. Given
how long it has already been, I don't think anyone already on the core team is
going to pick it up.
--
___
Python tracker
&
Change by R. David Murray :
--
stage: -> resolved
status: open -> closed
title: The replys additional (Re.) is ok. -> spam?
___
Python tracker
<https://bugs.python.or
R. David Murray added the comment:
Yep, that's the way Python works. You are modifying the same object through
different names. Remember that in Python it is the objects that matter (which
are identified in CPython via their memory address, but that's an
implementation detail)
R. David Murray added the comment:
New changeset aa218d1649690d1c1ba86a9972f7fae646bf1a8f by R. David Murray
(jayyyin) in branch 'master':
bpo-27931: Fix email address header parsing error (#5329)
https://github.com/python/cpython/commit/aa218d1649690d1c1ba86a9972f7fa
R. David Murray added the comment:
Requested a small additional change to the new tests, and then this will be
ready to go in.
--
___
Python tracker
<https://bugs.python.org/issue27
R. David Murray added the comment:
Yes, that looks like a bug. Should be a one line bug fix, plus tests and news
item if someone wants to make a PR...
--
nosy: +r.david.murray
___
Python tracker
<https://bugs.python.org/issue32
5401 - 5500 of 12944 matches
Mail list logo
