R. David Murray added the comment:
I think the text is OK as it stands. The first sentence is a technical
description of the result of setting the attribute, the last sentence is a
conceptual discussion of why you would want to set the attribute.
--
nosy: +r.david.murray
R. David Murray added the comment:
Since the TESTFN file is created only in this test, rather than use a tearDown
method, it would be better to use addCleanup in the test method itself.
--
nosy: +r.david.murray
___
Python tracker
<h
R. David Murray added the comment:
Turns out even with as_string accepting a policy keyword, the example still
failed. It needs to be generating a bytes object, not a string. Before I even
realized that, though, I decided I wanted to add as_bytes (and __bytes__). So
the attached patch does
R. David Murray added the comment:
Committed with changes pointed out by Antoine (thank you Antoine).
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
Thanks, Claudio.
--
resolution: -> fixed
stage: test needed -> committed/rejected
status: open -> closed
versions: +Python 3.3
___
Python tracker
<http://bugs.python.o
Changes by R. David Murray :
--
Removed message: http://bugs.python.org/msg194816
___
Python tracker
<http://bugs.python.org/issue8112>
___
___
Python-bugs-list m
R. David Murray added the comment:
Thanks, Popa.
--
___
Python tracker
<http://bugs.python.org/issue8112>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
It seems to me (having checked) that the current language is correct. The fact
that PyQt5 is available under the GPL isn't really relevant to the FAQ as it
currently exists (it doesn't mention the GPL anywhere else). Keep in mind that
Python&#x
R. David Murray added the comment:
Pydoc uses DumbWriter.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue18644>
___
___
Python-bug
R. David Murray added the comment:
My gut reaction to this is that it feels dangerous. That doesn't mean my gut
is right, I'm just reporting my reaction :)
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
This is not what we use keyword only arguments for. The standard practice in
the stdlib is that arguments are arguments unless there is a good reason to
make one keyword only. So I'm -1 on this proposal.
--
nosy: +r.david.m
R. David Murray added the comment:
Ach. I didn't read carefully enough (not awake yet, I guess).
Yes, boolean parameters are one of the things keyword only arguments are
appropriate for.
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
What is it that doesn't fail? The expression in the title is the beginning of
a triple quoted string with no closing triple quote.
If you mean '' % [1] not falling, it has been that way forever (well, python2.4
is as far back as I can tes
R. David Murray added the comment:
haypo: str % dict is a feature:
>>> "%(a)s" % {'a': 1, 'b': 2}
'1'
--
___
P
R. David Murray added the comment:
Yes, I suspect you are right that that is a bug...and a long standing one :)
--
___
Python tracker
<http://bugs.python.org/issue18
R. David Murray added the comment:
Hmm. The linked issue says the PyMappingCheck behavior is new in Python3, but
this problem exists in Python2 (back to 2.4 at least) as well. Perhaps it is a
different bug in Python2.
--
___
Python tracker
<h
R. David Murray added the comment:
Why do you think this is a bug? (You may well be right; I'm not familiar with
the intricacies of XML. But on its face the behavior looks reasonable.)
--
nosy: +r.david.murray
___
Python tracker
R. David Murray added the comment:
For what it is worth, I am currently writing some email tests and it would
certainly be convenient to have this. Of course I *can* define it locally in
the the test file.
--
___
Python tracker
<h
R. David Murray added the comment:
Not a problem, these things are often subtle. And now there is a record of it
in the tracker if anyone else questions it in the future.
--
stage: -> committed/rejected
___
Python tracker
<http://bugs.pyth
New submission from R. David Murray:
In 2.7:
>>> import pdb
>>> from email import message_from_string as m
>>> x = m("To: me\nfrom: you\n\ntest\n")
>>> pdb.set_trace()
--Return--
> (1)()->None
(Pdb) print x
>From nobody Fri Aug 16 19:06:5
R. David Murray added the comment:
Well, it does say that QUOTE_MINIMAL is the default for the dialect 'quoting'
attribute. What it doesn't say is that the default dialect (excel) is exactly
the documented default values for all the dialect parameters. (Although having
sai
R. David Murray added the comment:
Based on your response to the review (I haven't looked at the new patch) I say
go ahead and apply it.
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
OK, now I have a place in the non-test email code where using this would lead
to easier-to-read code.
--
___
Python tracker
<http://bugs.python.org/issue18
R. David Murray added the comment:
If you mean the code in Charset's __init__, if you change that you'll have
backward compatibility issues. As the code currently stands it is legal to
pass in a charset name that is bytes. And the string path of that if checks
that it contains
R. David Murray added the comment:
The comment, however, is clearly no longer appropriate :)
--
___
Python tracker
<http://bugs.python.org/issue18778>
___
___
R. David Murray added the comment:
The answer to the question about "alphanumerics" versus "alphanumeric
characters" is that is is mostly likely context-dependent, so I'd have to see
particular examples to say which I though read better. So, there is no One
True An
R. David Murray added the comment:
Yeah, if I could have a do-over of the 3.0 port, I'd probably drop the
acceptance of byte strings. Maybe we can deprecate it.
--
___
Python tracker
<http://bugs.python.org/is
New submission from R. David Murray:
I'm working on completing the API changes for the email package for 3.4. This
means I'm adding some more stuff to the current provisional API, which I will
then aim to make non-provisional in 3.5.
I've made a complete proposal to the emai
R. David Murray added the comment:
I think the essential use case is using a python program in a unix pipeline.
I'm very sympathetic to that use case, despite my unease.
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
I believe the module already supports sorting by time and cumulative time
(determining the top consumers of cpu is a major part of the point of the
profile module, after all).
What exactly is the change that you are proposing? If you post a diff instead
R. David Murray added the comment:
It would be clearer, I think, to call it average time. I must admit to not
being sure why that is useful. I'm also worried there might be backward
compatibility issues with changing the ordering of the data structure. If new
fields are going to be
R. David Murray added the comment:
"A lot of false alarms" means usually it works, but then sometimes it doesn't.
So just testing it on a couple of platforms isn't sufficient, unfortunately.
--
nosy: +r.david.murray
___
P
R. David Murray added the comment:
Backward compatibility is a concern. However, having the flags test true when
present, which they don't currently, should be considered a bug fix, I think.
So, I added a some tests to confirm the current behavior, and wrote a new patch
that *just* fixe
R. David Murray added the comment:
Woops, corrupted patch, and I see a bug...
--
___
Python tracker
<http://bugs.python.org/issue16611>
___
___
Python-bugs-list m
Changes by R. David Murray :
Removed file: http://bugs.python.org/file31403/cookie_flags.patch
___
Python tracker
<http://bugs.python.org/issue16611>
___
___
Python-bug
R. David Murray added the comment:
Corrected patch.
--
Added file: http://bugs.python.org/file31405/cookie_flags.patch
___
Python tracker
<http://bugs.python.org/issue16
R. David Murray added the comment:
There may not be a problem. I'm not familiar enough with the pstats code to
review the patch for real without some study.
--
___
Python tracker
<http://bugs.python.org/is
Changes by R. David Murray :
--
nosy: +ncoghlan, pmoody
___
Python tracker
<http://bugs.python.org/issue18802>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
In this expository context, I prefer the issue18326.that.diff version, but the
index link to the keyword-only_parameter ref should still be added to it (on
"only be passed by keyword").
--
___
Pyth
R. David Murray added the comment:
Documentation fixes are always backported.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue18
R. David Murray added the comment:
Thanks, Vajrasky. The v2 patch was almost correct. What you couldn't know
without being as deeply enmeshed in this code as I am is that the test failures
from the encoders module were actually invalid. We'd previously "fixed" them,
R. David Murray added the comment:
If you pipe the ls (eg: ls >temp) the bytes are preserved. Since setting the
escape handler via PYTHONIOENCODING sets it for both stdin in and stdout, it
sounds like that solves the sysadmin use case. The sysadmin can just put that
environment varia
R. David Murray added the comment:
The email package needs has_escaped_bytes. Currently it tries to encode to
ascii to find out if there are any, which we proved by microbenchmark is the
fastest way to do it as things stand.
What does replace do? Replace it with the unknown character code
R. David Murray added the comment:
The email package uses surrogateescape to store unknown bytes in unicode
strings, just as with the handle-bad-data-from-os API surrogateescape was
introduced for. (For the same reason: the source data may have improperly
encoded bytes that we must
R. David Murray added the comment:
I think a fully logical fix could be implemented for 3.4 (after I commit this),
because as you say it is *unlikely* that anyone is relying on the behaviors
mentioned as "backward compatibility issues" in the added tests. However, it
is *possible*
R. David Murray added the comment:
I agree that the 2.7 message is somewhat confusing, but I'm not sure it is
worth changing at this point in 2.7's life cycle.
For Python3, the message is correct and unambiguous: a bytes object is not a
string.
However, in 3.3, we have a
R. David Murray added the comment:
I forgot to address the comment about accepting bytes in python3: the delimiter
really is a unicode character. In python3, non-ASCII delimiters are handled
correctly. So no, it isn't a byte anymore, it really is a string. Terry's
comment about
R. David Murray added the comment:
Fix committed. Thanks, Julien.
If you want to propose a new patch the makes the behavior more
consistent/useful with respect to what browsers and servers actually do, feel
free to propose one. I'm going to close this issue, though.
--
resol
R. David Murray added the comment:
Then you catch KeyboardInterrupt and present your alternate text. I'm not
following what the problem is. In particular, once you've caught
KeyboardInterrupt, a second ctl-C *should* cause a normal program break,
otherwise you've locked
R. David Murray added the comment:
For anyone who wants to look in to this: according to the stack overflow
question and comments, this is a behavior change between python2 and python3.
--
nosy: +r.david.murray
___
Python tracker
<h
R. David Murray added the comment:
I wonder if you could achieve what you want (which I always hope programs I use
never do[*]) by writing your own signal handler.
In any case, I don't believe there is a bug here. This is working as designed.
[*] There are many times I have found m
R. David Murray added the comment:
Unless I'm completely misunderstanding (which I don't think I am), this is not
a race condition, it is how the language is designed to operate. The change
you are proposing is a language-design level change that would require a PEP.
The appropr
Changes by R. David Murray :
--
nosy: +michael.foord
___
Python tracker
<http://bugs.python.org/issue18848>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Unless it is a security issue, this seems like the kind of fix that shouldn't
be applied to maintenance releases.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/is
Changes by R. David Murray :
--
nosy: +gregory.p.smith, pitrou
versions: +Python 3.4
___
Python tracker
<http://bugs.python.org/issue18851>
___
___
Python-bug
R. David Murray added the comment:
In that case, the fix needs to be applied to 3.2 and 2.6 as well. Or at least
considered for application. It could be that this will break working (though
dangerous) programs. I'll leave it to folks more knowledgeable in this
particular area than
New submission from R. David Murray:
A 'message' part is not, in fact, a multipart in RFC terms. (Only 'multipart'
messages are multiparts.) The email package models 'message' parts by making
them single-element "multipart" messages, with th
R. David Murray added the comment:
I don't think __doc__ can ever not exist, so that code is just wrong :)
--
keywords: +easy
nosy: +r.david.murray
stage: -> needs patch
title: Problem with pyreadline -> site.py does not handle readline.__doc__
R. David Murray added the comment:
There is no easy way to merge accounts in roundup. If you've submitted the
agreement, your "*" should show up in a bit :)
--
___
Python tracker
<http://bugs.pyt
R. David Murray added the comment:
In Python the str of a None value is indeed 'None', just as the str of a True
value is 'True'. Unless the protocol to which you are encoding supports null
values, you shouldn't be using None values in the input to the serializatio
Changes by R. David Murray :
--
dependencies: +Add get_body and iter_attachments to provisional email API
___
Python tracker
<http://bugs.python.org/issue18
New submission from R. David Murray:
Here is a patch, layered on top of the patch in issue 18785, to add the content
manager support. This patch contains only the base ContentManager class, not
the proposed functional registries.
--
components: email
files: contentmanager.patch
R. David Murray added the comment:
subtests don't satisfy my use cases. You can't run an individual subtest by
name, and I find that to be a very important thing to be able to do during
development and debugging. At the moment at least I'm fine with just having my
parameteri
Changes by R. David Murray :
--
nosy: +r.david.murray
versions: -Python 3.1, Python 3.2, Python 3.5
___
Python tracker
<http://bugs.python.org/issue18
R. David Murray added the comment:
See also issue 3948 for another variation of this problem with
getsignal/setsignal.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue18
R. David Murray added the comment:
This seems to be producing a test failure in test_doctest. eg:
http://buildbot.python.org/all/builders/AMD64%20FreeBSD%209.0%20dtrace%203.x/builds/1920
--
___
Python tracker
<http://bugs.python.org/issue11
R. David Murray added the comment:
I don't think it is even "won't fix". Your "workarounds" are just the way you
need to feed non-latin1 text into Python2. Since the default source encoding
in python2 is latin-1, and that is documented, I'm not sure what
R. David Murray added the comment:
Looks OK to me. Do we want to also recommend more explicitly that the tests be
run with -uall?
--
___
Python tracker
<http://bugs.python.org/issue18
R. David Murray added the comment:
Heh. Obviously I've forgotten some things about python2. I could have sworn
the default was latin-1, but perhaps that was just the stdlib standard for
coding cookies? I don't use python2 muc
Changes by R. David Murray :
--
nosy: +pitrou
versions: +Python 3.4 -Python 3.1, Python 3.2
___
Python tracker
<http://bugs.python.org/issue18876>
___
___
Pytho
R. David Murray added the comment:
Hi, Erik. I changed the versions because we use versions in this tracker to
indicate which versions we intend to *fix* the problem in. I left 2.7 and 3.3
marked for the moment, but I have a feeling that this will need to be a
feature-release-only change
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue18879>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
I'm curious how this error gets triggered. I build python --with-pydebug on
Gentoo all the time, albeit from a checkout, and I've never seen it. I'm
imagining that means it is a Gentoo bug. Well, not even really a bug, since
Gentoo doesn&#
R. David Murray added the comment:
Python2 doesn't support the limited ABI, so that flag is a noop for 2.7.
--
___
Python tracker
<http://bugs.python.org/is
New submission from R. David Murray:
ByteGenerator will assume that it can change any linesep characters to the
linesep being used for the general message serialization, even if the content
transfer encoding is 'binary'. This is incorrect, as existing \r and \n
characters in bi
R. David Murray added the comment:
We have to be careful, since while Windows may no longer care about \r\n, the
RFCs certainly do, and the email package is very concerned with the RFC.
However, neither of these tests are testing linesep discipline, so it is fine
to fix them. I've
New submission from R. David Murray:
This is the third of three layered patches that introduce a new content
management API to the email package. This patch is layered on top of the patch
in issue 18860. Unfortunately the fact that these patches are layered (which I
did in hopes of making
Changes by R. David Murray :
--
dependencies: +Add content manager API to email package
___
Python tracker
<http://bugs.python.org/issue18890>
___
___
Python-bug
New submission from R. David Murray:
Since the only way to get a rietveld review link for all the changes is to post
a single complete patch, I'm doing so in this issue. Feel free to review based
on either this or the separate patches posted in issue 18785, issue 18860, and
issue
R. David Murray added the comment:
Looks good to me, go ahead and push it.
--
___
Python tracker
<http://bugs.python.org/issue12037>
___
___
Python-bugs-list m
R. David Murray added the comment:
What happens if you actually call commit()?
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue18
R. David Murray added the comment:
Sorry, I didn't mean to be cryptic. Yes, Peter has figured out what I was
trying to say.
--
___
Python tracker
<http://bugs.python.org/is
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue18896>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
For test_email, the fix was correct because the *test* didn't care about what
line ending the source file had. I can't speak for sax.
--
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
It's an interesting thought. It bothered me to be handling them as pure
strings when writing the code. It just felt wrong somehow :)
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
Suggesting using a 3rd party library in order to explain how to use the python
standard library to do something isn't going to work.
Would you like to propose an alternate article or an improvement to the howto,
using only stdlib facilities?
(Note tha
R. David Murray added the comment:
The article is *explaining* basic auth, thus the pedegogy of the presentation,
and why it is a "see also" and not part of the docs proper.
I'll admit I don't understand the first part of that comment, since the second
part says yo
R. David Murray added the comment:
Thanks. I suspect someone will indeed latch on to this soon enough.
We use the 'versions' to track what version we are going to fix the bug in. So
I've removed 3.2, since that only gets security fixes, and 3.5, since that
doesn't exis
Changes by R. David Murray :
--
dependencies: +In imaplib, cached capabilities may be out of date after login
___
Python tracker
<http://bugs.python.org/issue11
R. David Murray added the comment:
I agree that this would be a good idea, but it is not a bug in the current
implementation. The only place imaplib itself uses the cached capabilities is
*before* login, in the starttls method, and there it refreshes it after
starttls succeeds.
Although it
R. David Murray added the comment:
It seems to me that 2080 (per the accepted answer to your [3]) is indeed "a
rather small len(x)", and that the docs are correct as written.
I wonder if it would be worth adding a footnote that explains how to calculate
that example 2080 numbe
R. David Murray added the comment:
Alternatively, you would have to supply (or supply a pointer to) a mathematical
proof of your thesis.
--
___
Python tracker
<http://bugs.python.org/issue18
R. David Murray added the comment:
I have project in which that would be useful, so +1 from me for the general
concept.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue18
R. David Murray added the comment:
Hmm. It seems to me that that document is indeed not clear as to what is
really going on. My understanding has always been that there is only one
Python interpreter, but that it behaves differently when invoked through the
symlink in the venv. I suppose
Changes by R. David Murray :
--
nosy: +vinay.sajip
___
Python tracker
<http://bugs.python.org/issue18940>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by R. David Murray :
--
nosy: +vinay.sajip
___
Python tracker
<http://bugs.python.org/issue18941>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Done. Thanks, Berker.
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
type: -> behavior
___
Python tracker
<http://bugs.python
R. David Murray added the comment:
Why do you think that? Can you provide a test case that fails?
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue18
R. David Murray added the comment:
Netaddr is not an stdlib module. Please report the bug to the netaddr
maintainers.
--
nosy: +r.david.murray
resolution: -> invalid
stage: -> committed/rejected
status: open -> closed
versions: +3rd party -P
R. David Murray added the comment:
You have understood correctly, after reading the now-existing documentation.
Do you have a suggestion for how they could be further improved, given that
they currently seem to convey accurate information?
For the "autonomy" question, as far as
3901 - 4000 of 10554 matches
Mail list logo
