R. David Murray added the comment:
Note also that datetime.now() gives you a naive datetime. From an API
consistency standpoint I think it makes sense that datetime.utcnow() gives a
naive datetime. It would actually be confusing (IMO) for it to return an aware
datetime. I can see why you
R. David Murray added the comment:
Note that the parser does attempt to accept obsolete syntax (registering
defects for it), so if there is a bug in the implementation of the obsolete
syntax handling it should be fixed. And yes, there have been other bugs with
whitespace handling in the
R. David Murray added the comment:
The general idea is that the string version of the header should contain all of
the original information, but the parsed elements (the things returned by
special header attributes) will contain the valid data, if any. So if the
string version of the
R. David Murray added the comment:
Yeah, I think we need a complete example here.
Note that in the general case there is no such thing as an RFC-valid email in
unicode (which is what python strings are), though with utf8=True and an email
involving only text you might get away with it. I
R. David Murray added the comment:
The policy is named 'default' because it was intended to become the default two
feature releases after the new email code became non-provisional (first:
deprecate not specifying an explicit policy, next release make default the
default policy an
R. David Murray added the comment:
That is the first step, yes. In addition to that we need to have the various
explain_to methods delete the special attributes that aren't valid for the new
Message subtype.
--
___
Python tracker
R. David Murray added the comment:
I wonder if it has something to do with range returning a special type? range
and len are very different things under the hood.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue12
R. David Murray added the comment:
Unfortunately I don't think there is any way except going through each subclass
to see what special attributes it creates.
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
Ezio, I don't see any indication in this ticket that this bug was actually
*fixed* in 3.x. Unicode doesn't cause immediate errors in 3.x, but it isn't
recognized as wordchars, etc. Am I mi
R. David Murray added the comment:
Why? The bug hasn't been fixed yet.
--
assignee: -> r.david.murray
stage: -> patch review
status: closed -> open
versions: +Python 3.2
___
Python tracker
<http://bugs.pyth
R. David Murray added the comment:
I may have, but I'd prefer to check before closing the issue. (I'm deep in
another project right now, but I'll review all these open bugs this fall some
time).
--
status: closed -> open
___
Pyt
R. David Murray added the comment:
It is python.exe on OS/X, which I've always found most odd. The reason is that
the OS/X filesystem is case insensitive by default, and there is a directory
named 'Python'.
--
nosy: +r.david.murray
___
R. David Murray added the comment:
I'm flat out right now on other projects. But if no one else gets around to
doing a final review and commit I should be able to get to it by the end of
October. If I don't, please ping me by posting
Changes by R. David Murray :
--
assignee: docs@python
components: Documentation
nosy: docs@python, r.david.murray
priority: normal
severity: normal
status: open
title: RLock support the context manager protocol but this is not documented
___
Python
R. David Murray added the comment:
Note that a C accelerator for Decimal is in the works.
--
nosy: +mark.dickinson, r.david.murray
___
Python tracker
<http://bugs.python.org/issue13
R. David Murray added the comment:
It seems to me that saying "floating point" and "mathematically correct" in the
same breath is...optimistic :) But that's why I added Mark to nosy, he knows
far more about this stuff than I do.
As far as I know the accelerator is
R. David Murray added the comment:
+1. decode_idna is likely to be useful to the email package.
--
___
Python tracker
<http://bugs.python.org/issue3232>
___
___
Changes by R. David Murray :
--
stage: -> needs patch
versions: -Python 2.6, Python 3.1, Python 3.4
___
Python tracker
<http://bugs.python.org/issu
R. David Murray added the comment:
It seems clear enough to me that when a process terminates ("the entire Python
program exits") then all of its threads must terminate. That's part of the
definition of threads, to my understanding.
I think the confusion arises from the
Changes by R. David Murray :
--
assignee: -> r.david.murray
___
Python tracker
<http://bugs.python.org/issue13080>
___
___
Python-bugs-list mailing list
Un
R. David Murray added the comment:
This looks correct to me, and it tested out fine on the test suite (and the
provided test failed without the provided fix), so I committed it.
I have a small concern that the change in output might be a bit radical for a
bug fix release, but it does seem to
R. David Murray added the comment:
Heh, you happened to post your patch at a time when I wanted something to do as
a break from something I didn't want to do...and I *thought* I understood the
problem, after reading the various links. But clearly I didn't. We don't have
R. David Murray added the comment:
Sorry. It is intended behavior. The lambda 'each' is bound to the local
'each', and by the time the lambda's execute, the value of 'each' is 'baz'.
I'm going to turn this into a doc bug, because while
Changes by R. David Murray :
--
title: setattr misbehaves when used with lambdas inside for loop -> Need
Programming FAQ entry for the behavior of closures
___
Python tracker
<http://bugs.python.org/issu
R. David Murray added the comment:
Hmm. But what I did was look up the RLock section of the manual to answer the
question "does this support the context manager protocol", and the answer
appeared to be no. In a reference manual I would expect all the important
features of an ob
R. David Murray added the comment:
I wonder if it is a bug in Windows? Have you tried similar experiments with
regular files? tempfile is really just about *where* the files are located
(and what happens when they are closed), not about their fundamental nature as
OS file objects. (I
R. David Murray added the comment:
Well, your patch is a little *too* simple: it doesn't change the function
prototype to match :)
This is a cosmetic issue rather than a bug, but it would still be nice to fix
it. Or maybe a documentation issue in the sense that Python code is (us
R. David Murray added the comment:
"This issue" is currently a collection point for specific "allow this in lax
mode" issues. Do you have one or more specific cases in point that you'd like
to talk about? (Note that the 'garbage after end of fil
R. David Murray added the comment:
This patch has caused a non-trivial regression between 3.2 and 3.2.1. The
scenario in which I observed it is poplib. I create a POP3 connection with a
timeout. At one point in its processing, poplib is reading lines until it gets
a line '.\r\n'
R. David Murray added the comment:
I don't think it is optimistic. The poplib transaction pattern is: send a
command, get a response. If the response is not properly terminated, throw it
away. Send a new command, get a response. There's no ambiguity there. In
addition, this i
R. David Murray added the comment:
How can a lack of flushes lose output? Delay it maybe, but unless your file
class is broken I don't see how data would be lost.
--
nosy: +r.david.murray
versions: -Python 2.6
___
Python tracker
R. David Murray added the comment:
Your suggestion sounds good to me.
I still think that it is a common failure mode in a client server transaction
for the server to fail to send a (complete) line that the client is expecting,
and vice versa, requiring a timeout, but not necessarily a
R. David Murray added the comment:
I'm assigning this to myself so I don't lose it, but if someone wants to work
on a patch please do. It'll be a bit before I can look at it.
--
assignee: -> r.david.murray
priority: normal -> high
s
R. David Murray added the comment:
Since this is a regression I'm upping the priority further to release blocker,
so that we don't put out another release with the regression still in it.
--
nosy: +benjamin.peterson, georg.brandl
priority: high -> re
R. David Murray added the comment:
In the case of 'lists' an object is being allocated each time through the inner
loop. In the case of simple_lists, no such allocation is being done. Your
timing issues are probably related to the memory allocation behavior of your
system.
-
R. David Murray added the comment:
Unless I misunderstand your concerns, this is a duplicate of issue 665194.
--
nosy: +r.david.murray
resolution: -> duplicate
status: open -> closed
superseder: -> datetime-RFC2822 roundtripping
___
Pytho
R. David Murray added the comment:
formatdate doesn't know anything about datetimes, so it doesn't make any sense
to me to say that it doesn't notice changes in tzinfo. That's why the fix for
issue 665194 introduces a new method for
R. David Murray added the comment:
Just a note that buildbot does work behind a firewall (mine are set up that
way). The client calls out to the master. A really restrictive corporate
firewall may need outbound holes punched, but there are no inbound connections
to the client
R. David Murray added the comment:
Yeah, I just haven't found time to do the revert yet (my first naive attempt
using hg commands failed and I haven't found time to figure it out or do the
reverse-patch method).
--
___
Python trac
R. David Murray added the comment:
We've had problems with this service going away for a while before. I think
the test was marked skip for at least a year before someone (it might have been
me) noticed that it was back and reactivated it. There's a ticket in here
somewh
New submission from R. David Murray :
The doc string for HTTPConnection.getresponse mentions (in broken English) that
the instance's response_class attribute determines what class gets instantiated
for a response. The docs do not mention this attribute, nor any other way to
control
R. David Murray added the comment:
I suspect you want to be using Python3, then. Although it is nowhere near as
simple as that...even with Python3 you still sometimes have to deal with the
fact that the wire protocol is bytes.
--
nosy: +r.david.murray
resolution: -> out of d
New submission from R. David Murray :
HTTPResponse subclasses RawIOBase, but does not provide an implementation of
readinto, only read. This means that it is not conforming to the IO spec, and
so it cannot be wrapped in a BufferedIOBase when using the C version of io.
--
components
R. David Murray added the comment:
Nope. If you want to count backward, use a negative step. Not doing anything
if end is lower than start allows code to take advantage of "don't care" edge
cases, just like 'abc'[4:] returning the empty string does. Range is often
R. David Murray added the comment:
Well, most of the point of Python3 is that the string type *is* unicode, which
is what I meant by saying that you probably wanted Python3 in order to solve
your concern :)
There are still a few bugs to work out in the wire-protocol/unicode interface
in
R. David Murray added the comment:
If you decide this is only a doc bug, please see also related issue 12832.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue6
New submission from R. David Murray :
The documentation for os.makedirs says:
If the target directory with the same mode as specified already exists,
raises an OSError exception if exist_ok is False, otherwise no exception is
raised.
This is not correct. If the file exists but the mode is
New submission from R. David Murray :
The documentation for Event.wait says:
This method returns the internal flag on exit, so it will always return True
except if a timeout is given and the operation times out.
In fact, however, if the thread that sets the flag immediately clears it, wait
R. David Murray added the comment:
Thinking about it, if the flag's state if the wait does not expire is not
guaranteed to be True, then what I really need is some way to know, when the
wait call completes, whether or not it terminated because of a timeout or not.
I can always quer
R. David Murray added the comment:
Changing the title and component to reflect Antoine's new understanding :)
--
components: +Library (Lib) -Documentation
title: Documentation for Event.wait return value is either wrong or incomplete
-> Event.wait sometimes returns False even
R. David Murray added the comment:
That particular problem will get fixed in the next version of the email package
(hopefully in Python3.3), but that isn't ready yet.
--
___
Python tracker
<http://bugs.python.org/issu
R. David Murray added the comment:
I agree with you that this is inconsistent. However, having str raise an error
is pretty much a non-starter as a suggestion. str always falls back to the
repr; in general str(obj) should always return some value, otherwise the
assumptions of a *lot* of
R. David Murray added the comment:
A diff would be great.
We try to use warnings sparingly, and I don't think this is a case that
warrants it. Possibly a .. note is worthwhile, perhaps with an example for the
bytes case, but even that may be too much.
I also wouldn't use the w
R. David Murray added the comment:
Why do you consider this to be a bug? You set posix=False and
whitespace_split=True, so it seems to me that according to the documented rules
the " inside the word ("a is as documented not recognized as a quote character.
If you use either pos
R. David Murray added the comment:
On Wed, 07 Dec 2011 18:45:27 +, wrote:
> ___
> diff --git a/Doc/library/threading.rst b/Doc/library/threading.rst
> --- a/Doc/library/threading.rst
> +++ b/Doc/library/threading.rst
> @
R. David Murray added the comment:
I'm pretty sure that what you are reporting has been fixed by the 'garbage' fix
I mentioned (which might better be called the 'more flexible handling of
comments' patch). Though not in 2.5 (or 2.6) since they are no longer in
m
R. David Murray added the comment:
"set to True, either before the wait call or after the wait starts"
--
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
And just for your information, as far as I know *no one* knows what standard
(or model) non-posix mode shlex is based on.
--
___
Python tracker
<http://bugs.python.org/issue13
R. David Murray added the comment:
Here's the patch:
http://hg.python.org/cpython/rev/cc3255a707c7/
I thought I remembered getting it in to 2.7.2, but my memory is evidently
wrong. It has been applied, but is not yet in the released version o
R. David Murray added the comment:
LGTM.
--
___
Python tracker
<http://bugs.python.org/issue13502>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
So isn't this saying that this is a problem with the distribution packaging and
not with CPython itself?
--
nosy: +barry, r.david.murray
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
Probably because I'm a threading/multiprocessing neophyte :) (Though I just
learned a bunch about programming with threads recently...)
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
I'm not sure why having a locale set to C or something invalid should be
considered a Python bug. You have to handle un-decodable filenames no matter
what you do, since things aren't always encoded in utf-8 on non-OSX unix even
when that is
R. David Murray added the comment:
> But currently everything handling filenames as unicode on
> nix needs to worry about surrogates (that can't be encoded
> as ascii) already, or it will still be passing values that
> can't be interpreted by other processes as you highli
R. David Murray added the comment:
> _My_ locale is set properly. The problem is all the other
> people in the world who do not have their locale set to match
> their files on disk; telling them each to fix it is tedious.
> But perhaps the OS is the best place to address th
R. David Murray added the comment:
What is the motivation for providing a new function?
--
___
Python tracker
<http://bugs.python.org/issue8828>
___
___
Pytho
R. David Murray added the comment:
Ah, I see, people may be depending on rename on Windows not overwriting.
I suppose a new function (and eventually deprecating the old?) would be the
most straightforward way forward, though I dislike the necessity :)
An alternative might be a flag on rename
R. David Murray added the comment:
I'm good with None/True, but that would imply that for posix rename we'll need
to implement the overwrite=False option...which would be a nice thing (the
shell mv command has -i for that).
I think a warning would be good, because a unix progr
R. David Murray added the comment:
Ah, you are right about the race of course. So yes, I agree with your
proposal. It's a weird API, but probably the best we can do.
--
___
Python tracker
<http://bugs.python.org/i
R. David Murray added the comment:
So maybe my warning idea isn't such a bad idea :)
As a unix programmer, I was very surprised to read in this thread that Windows
doesn't overwrite the file on rename. As a unix programmer, I don't check for
errors on a rename, because I ex
R. David Murray added the comment:
Actually, no, the local part cannot be in anything other than ascii (see RFC
5335, which desires to address this problem among others). Also, an encoded
word cannot occur inside quotation marks. If you correct those two bugs, you
can generate an RFC-valid
R. David Murray added the comment:
Regardless of what anybody thinks about the design, it is what it is and can't
be changed for backward compatibility reasons. The best we can do is reject
creating duplicate headers for headers that may only appear once. That feature
has already
R. David Murray added the comment:
Antoine, I marked this for Python 3.3 only because there is no good way to fix
it in 2.7/3.2. (If someone comes up with a way I'll be happy to review it,
though!)
--
versions: -Python 2.7, Python 3.2
___
P
R. David Murray added the comment:
The RFC isn't at all vague about encoded words not separated by white space.
That isn't allowed by the BNF. As you say, though, they occur in the wild and
should be parsed correctly.
In your other point I think you mean "immediatel
R. David Murray added the comment:
Well, supporting the other variants would be good (I'll review any proposed
patches), but I think the default will have to stay mboxo for backward
compatibility reasons (unless the consensus is to go through the
warning/deprecation cycle to change it)
R. David Murray added the comment:
The first argument to authenticate must be bytes. This is not well documented.
It might also be a bug, since I'm not sure anyone has done a thorough audit of
what should be bytes and what should be string in imaplib.
3.1 no longer gets bug fixes, s
R. David Murray added the comment:
Gah, I was looking at the wrong source code when I wrote that. A string first
argument is indeed valid. I'm not sure where the problem is coming from since
the internal CRAM_MD5 returns a string and that seems to
R. David Murray added the comment:
Bytes definitely. We hashed that out a while ago.
My point is that CRAM_MD5 login calls authenticate, and its authenticator
returns a string, just like your example does. So it ought to be going through
the same code path. I haven't followed the log
R. David Murray added the comment:
Well, a caution that tweaking the regex can have unexpected consequences as
past issues have proven (but by all means go for it), and a note that the
parsing strategy is going to change completely in email6 (see
http://pypi.python.org/email and http
R. David Murray added the comment:
Gah, that's what I get for not reading carefully (or looking at the patch
first). Your test change is fine, of course.
--
___
Python tracker
<http://bugs.python.org/i
R. David Murray added the comment:
Would you be interested in providing a patch that includes tests? I think
Antoine set up a test framework for testing the login as part of issue 4471.
--
___
Python tracker
<http://bugs.python.org/issue13
R. David Murray added the comment:
The content of a script tag is CDATA. Why would you expect it to be parsed?
--
nosy: +ezio.melotti, r.david.murray
___
Python tracker
<http://bugs.python.org/issue13
R. David Murray added the comment:
I believe this was fixed recently as part of issue 670664. Ezio will know for
sure.
--
___
Python tracker
<http://bugs.python.org/issue13
R. David Murray added the comment:
I think adding the word 'bitwise' in front of "or'ed" and linking it to that
section would be sufficient.
--
nosy: +r.david.murray
versions: +Python 3.2, Python 3.3
___
Python tracker
R. David Murray added the comment:
euc_jp and euc_kr seem to be backward (that is, codecs translates them to the _
version, instead of translating the _ version to the - version). I worry that
there might be other deviations from the standard email names. I would suggest
we pull the list
R. David Murray added the comment:
Hmm. Must have misread. Looks like all the common charsets do have MIME
entries in the IANA table.
--
___
Python tracker
<http://bugs.python.org/issue8
R. David Murray added the comment:
On second thought the resolution order ought to be swapped anyway: if the user
has added an ALIAS, they are going to want that used, not the one from codecs.
--
___
Python tracker
<http://bugs.python.
R. David Murray added the comment:
Thanks for the patch. Adding support for this is a good idea. There could be
a question about whether this constitutes a bug fix or a feature; I'll canvass
some other devs and see if we have a consensus on it.
It may take me a bit to find time to
Changes by R. David Murray :
--
assignee: -> r.david.murray
___
Python tracker
<http://bugs.python.org/issue12147>
___
___
Python-bugs-list mailing list
Un
R. David Murray added the comment:
asdl_c.py should not be run during a non-checkout build, since the files it
builds should already have been (re)built and checked in by the time a release
is rolled. IIUC The release building script is supposed to ensure the
timestamps of the files are
R. David Murray added the comment:
Here's another (unrelated?) failure:
http://www.python.org/dev/buildbot/all/builders/x86%20Gentoo%203.x/builds/173/steps/test/logs/stdio
[ 43/355] test_logging
Traceback (most recent call last):
File &quo
R. David Murray added the comment:
Well, it turns out that back when I opened this issue I misunderstood what the
ALIASES table was used for. it *is* used before doing a codecs lookup, but it
is also used to convert whatever charset name the programmer specifies into the
standard MIME name
R. David Murray added the comment:
And like Benjamin said, it should be enough to touch those two files. You
don't have to actually build a release tarball.
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
How about instead changing [1/4], [2/4] etc to be [1/4/0], [2/4/0], etc?
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue12
R. David Murray added the comment:
Read the description of strings and raw strings at the top of the re
documentation for the answer to your question about \\. It would probably be
better if the example regular expression was written r'(.+) \1' instead of as a
bare expression as
R. David Murray added the comment:
For background on a similar issue, see #11828, especially msg133532.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue12
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue11512>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
While I agree that it should ideally be possible to actually control this
behavior as indicated by the comment, any syslog handler that does not sanitize
the messages it receives is broken.
--
nosy: +r.david.murray
R. David Murray added the comment:
s/handler/receiver/
--
___
Python tracker
<http://bugs.python.org/issue12168>
___
___
Python-bugs-list mailing list
Unsub
R. David Murray added the comment:
Looks good to me. And I meant documenting the process for adding a directory.
--
___
Python tracker
<http://bugs.python.org/issue12
1 - 100 of 10554 matches
Mail list logo
