R. David Murray added the comment:
The support. ClawsMail is broken, IMO.
--
___
Python tracker
<http://bugs.python.org/issue22319>
___
___
Python-bugs-list m
R. David Murray added the comment:
If there is a way to resolve the lock issue we can consider it. But (without
looking at the code again) I suspect the locking is too deeply embedded in the
mbox logic for this to be a safe change.
--
___
Python
Changes by R. David Murray :
--
resolution: -> not a bug
___
Python tracker
<http://bugs.python.org/issue30087>
___
___
Python-bugs-list mailing list
Un
R. David Murray added the comment:
Just create a subdirectory inside the tempdir to hold your Maildir folder. I
think it is not worth complicating the API for this use case, since it does
have a simple solution.
--
versions: -Python 2.7, Python 3.5, Python 3.6
R. David Murray added the comment:
Right. Which is why you get an error if you try to use an empty directory as
if it was a maildir :)
create=True creates the *directory* and initializes it. That seems clear to
me, and exactly what I would expect. "The mailbox" is the directo
R. David Murray added the comment:
I don't think your specialized error message adds anything. The the most
common mistake, IMO, is going to be not realizing that run_coroutine_threadsafe
don't return one of the acceptable types. So being told that
concurrent.future.Future is not
Changes by R. David Murray :
--
components: +Library (Lib) -Extension Modules
___
Python tracker
<http://bugs.python.org/issue30103>
___
___
Python-bugs-list m
Changes by R. David Murray :
--
type: behavior -> enhancement
versions: +Python 3.7 -Python 3.4
___
Python tracker
<http://bugs.python.org/issue30103>
___
_
R. David Murray added the comment:
Numpy is not part of the Python standard library. You'll need to engage with
the numpy community on this question. (I say engage with them on the question,
not report a bug to them, because I highly doubt this is a bug...there's
probably some
R. David Murray added the comment:
Well, part of the point of the tests is to make sure the module's behavior
doesn't change when doing the conversion to argparse. But "behavior changing"
doesn't extend to the exact format of the output...that can change, as long
Changes by R. David Murray :
--
resolution: -> duplicate
stage: -> resolved
status: open -> closed
superseder: -> keyword module missing async and await keywords
___
Python tracker
<http://bugs.python
R. David Murray added the comment:
Please close the redundant PRs. I've commented on pr1228.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
To be clear: backport PRs should be created only after a PR has been approved.
--
___
Python tracker
<http://bugs.python.org/issue30
R. David Murray added the comment:
Also, please review the (newly rewritten) section in the devguide about PRs. I
see now that there were changes made from the original here already, but I
don't see the commits that made those changes. The history of changes should
be kept duri
R. David Murray added the comment:
Yes, please do provide an example. Your final words do not make a convincing
case that this is a problem in python3 :)
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue30
R. David Murray added the comment:
I think you are missing a re.escape around text. Text is otherwise not a valid
replacement pattern.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue30
R. David Murray added the comment:
Good point, re.escape is for literal text you want to insert into a matching
pattern, but the replacement template isn't a matching pattern. Do we need a
different escape function? I guess the function solution is e
R. David Murray added the comment:
Then you have a broken copy of 3.5.1. There is nothing OS-specific about that
file.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue30
R. David Murray added the comment:
You don't appear to have successfully attached the script. Can you try again
please?
The patching in the issue you point to does not patch __and__, it just sets it
equal to __rand__.
--
nosy: +r.david.m
R. David Murray added the comment:
re.escape was escaping too much previously, and this has been fixed in 3.7 (and
only 3.7, because it may cause testing issues such as you have observed). See
issue 29995.
A note needs to be added to the 'porting' section of whats new cov
R. David Murray added the comment:
I would like to say that the latter interpretation is "obviously" correct,
except that it clearly wasn't obvious to you. The fact that it "contains the
output stream" I would have thought was pretty clear: if you are writing to it,
R. David Murray added the comment:
You've closed stderr.
--
nosy: +r.david.murray
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<http://bugs.pyth
R. David Murray added the comment:
If it is a bug that indicates there is at least one missing unit test :) Maybe
the OP will contribute a test.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue30
R. David Murray added the comment:
Considering that in the cpython test suite we avoid using docstrings in
unittests because of this "feature" of unittest, I doubt anyone on the core
team is going to be motivated to fix this :) That doesn't mean we won't accept
a PR, b
R. David Murray added the comment:
My impression is that the sentence is there because you are acting directly on
the raw byte stream, which you are not in the other cases. (Well, rfile, but
that's reading, so what you do there doesn't affect the wire protoco
R. David Murray added the comment:
Setting up an imap server on pythontest is the "right" answer. Somebody has to
do the work, though :)
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
For backward compatibility reasons, history will win.
I'm not sure if documenting the additional restrictions of the concrete stdlib
types in the ABC docs makes sense, either, since the ABCs are intentionally the
minimal requirements for a concrete ty
R. David Murray added the comment:
I suppose someone could propose a set of tests that an implementation of an ABC
type should pass, to complement the stdlib type tests. There would probably be
a lot of bikeshedding involved in such tests though, so I don't hold out great
hope anything
R. David Murray added the comment:
Indeed, it sounds like wine is claiming to be Windows 7 but then implementing
(as not implemented) later-than-windows-7 apis. That definitely sounds like a
bug in wine.
--
nosy: +r.david.murray
___
Python tracker
R. David Murray added the comment:
We generally don't do this kind of type checking in the standard library. The
message may not be clear, but it is accurate and decipherable, especially given
the fact that the write parameter name is 'buffer'. I don't think anything
R. David Murray added the comment:
I think Benjamin is the only one who has done any work on it so far. I think
you'd ask the infrastructure team for access if you want to do so.
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
You are depending on a non-portable feature of os.rename there, so I'm not
convinced this makes a good use case for the Python stdlib.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
Yes, and I'm saying his example doesn't work on Windows (on windows, it does
not accomplish his goal). So I'm not sure it is a use case appropriate for the
standard library. I'm not saying it definitely isn't,
R. David Murray added the comment:
Not only is not something to be surprised about, it would be surprising for it
to be absent. So the user cognitive overhead of removing it is quite possibly
higher than that of it being there.
--
nosy: +r.david.murray
R. David Murray added the comment:
If these objects have been exposed in the past, we won't simply delete them.
At a minimum there would need to be a deprecation period, but is there a real
motivation for deleting them?
--
nosy: +r.david.m
R. David Murray added the comment:
Sorry, by "real motivation" I meant something beyond just cleaning up the
API...that's a real motivation, it may just not be enough.
--
___
Python tracker
<http://bugs.pyt
R. David Murray added the comment:
Why do you think this is a bug?
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue30268>
___
___
Pytho
R. David Murray added the comment:
To clarify my question, I don't think it is a bug, but the fact that you do
might mean there needs to be a doc clarification. Or it might not. Or, there
might be a desirable enhancement here, maybe relating to the pathlike pro
R. David Murray added the comment:
That's the same motivation, not a new one :) Someone somewhere may be using
them for something, they've been around for a long time. I hope not, though.
--
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
If it is there for debugging, why would we want to remove it?
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue30
R. David Murray added the comment:
No, I'm arguing purely from a generic backward compatibility perspective.
There does not seem to be me be sufficient benefit to removing them to justify
doing it.
--
___
Python tracker
<http://bugs.py
R. David Murray added the comment:
They are not part of the API, that is why they are not documented. The
convention of "always" using _ prefixed names for non-API stuff is (relatively)
recent. It used to be we just didn't document the non-API stuff.
Your second arg
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>
___
___
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:
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(
3101 - 3200 of 10554 matches
Mail list logo
