R. David Murray added the comment:
OK, I've looked at the docs and code, and as far as I can see this bug does not
exist in Python3. Or at least in 3.4, which is the only place I'd feel safe
about making a change to the exception type.
To summarize: in 3.4 socket logic is based on
R. David Murray added the comment:
Should there be a mention in whats new in case any external tools are (still)
looking at it and thinking it is meaningful?
--
nosy: +nedbat, r.david.murray
___
Python tracker
<http://bugs.python.org/issue19
R. David Murray added the comment:
You are looking for the (new in Python 3) 'validate' option of b64decode:
>>> base64.b64decode(b"GET
>>> http://www.google.com.hk/search?q=hotels+near+airport&pws=1&igu=1&ip=0.0.0.0&safe=images&a
R. David Murray added the comment:
I believe that this is because once you execute the first line, 'a' exists as a
name in the 'lib' namespace, so 'from . import a' sees that 'a' already exists,
and does nothing. The same import sequence in abc.py wil
Changes by R. David Murray :
--
resolution: -> invalid
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
Looking at the source, the suppression of errors is clearly intentional.
Looking at the change that added the TypeError check, we see this from Jeremy
Hilton in March 2002 (9c2ca37bdeec):
It appears that getcomments() can get called for classes defined
R. David Murray added the comment:
Updating the patch to address Stephen's review comments (thanks, Stephen!).
The biggest change is adding a MIMEPart class, and renaming MIMEMessage to
EmailMessage. Other significant changes are: only moving 'Content-*' headers
in 'm
R. David Murray added the comment:
Serhiy's review comments were addressed by changes made on the master patch
issue.
Closing this one in favor of that one.
--
resolution: -> out of date
stage: patch review -> committed/rejected
superseder: -> Master patch for c
Changes by R. David Murray :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue18785>
___
___
Python-bugs-list mailing list
Unsubscrib
R. David Murray added the comment:
Closing in favor of the master patch issue 18891.
--
resolution: -> out of date
stage: patch review -> committed/rejected
status: open -> closed
superseder: -> Master patch for content manager addtion to e
R. David Murray added the comment:
Closing in favor of the master patch issue 18891.
--
resolution: -> out of date
stage: patch review -> committed/rejected
status: open -> closed
superseder: -> Master patch for content manager addtion to e
R. David Murray added the comment:
Nothing stops us from have a post-mortem discussion on a closed issue :)
The rationale for only doing the check for .netrc is that that is
backward-compatibility-wise fairly safe, because other tools will already be
insisting on the same security. But for
Changes by R. David Murray :
--
Removed message: http://bugs.python.org/msg199343
___
Python tracker
<http://bugs.python.org/issue19212>
___
___
Python-bugs-list m
Changes by R. David Murray :
--
status: open -> closed
title: Invitation to connect on LinkedIn -> Spam
___
Python tracker
<http://bugs.python.org/i
R. David Murray added the comment:
You might expect that, but platform.linux_distribution is basing its report on
what is in /etc/xxx-version or xxx-release. Most likely this is an Oracle
"bug", although they might be providing both their own version file and the
version file
Changes by R. David Murray :
--
nosy: +pitrou
___
Python tracker
<http://bugs.python.org/issue19215>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Oops, I was too quick with that nosy. This bug is fixed in io.StringIO, which
means it is fixed in Python3. And sorry to say, it shouldn't be fixed in a
maintenance release, since it is a behavior change that could break working
programs.
--
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue19216>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Added some review comments. Summary: I think we should just make it a dotted
attribute test, and forget about the 'time' thing, which was just used because
that's what the available network test used. (I find it odd that
allow_dotted_names
R. David Murray added the comment:
It occurs to me, looking at the docs, that there are doc changes also required
for this patch. And given that there are doc changes, this clearly can't be
treated as a bug fix.
If there is no objection to fixing it in 3.4, though, I'd like to
R. David Murray added the comment:
There is definitely a bug in set_payload here, and (obviously :) no test for
that case (passing an 8bit charset to set_payload).
--
___
Python tracker
<http://bugs.python.org/issue19
R. David Murray added the comment:
Yes, good point, those tests should definitely be added, which means the test
work doesn't go to waste :)
Note, however, that getsource *does* raise.
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
Well, I'm not certain, to tell you the truth.
However, the only non-backward-incompatible change that will work is to
introduce a new command that gives one access to the "real" print function, and
that to me feels really really ugly a
R. David Murray added the comment:
python-list is a mailing list, so you would subscribe and post your questions
and examples there. There are very good reasons for the existing behavior, and
python-list would be a good place for you to learn about them (by asking
questions).
The file case
R. David Murray added the comment:
I applied the patch (with doc and test changes) in d4d886620a00, before I saw
your patch. But your patch fixes the main 'p' docs, which I somehow missed, so
I applied it, too.
So, thanks Connor, and I think this is done.
A couple notes if you ar
R. David Murray added the comment:
Thanks, Vajrasky. I simplified your test a bit further still.
It occurs to me that nowadays (unlike when the file was written), we can use
resources to skip individual test classes or even individual tests. So we
could open a new issue to move the last
R. David Murray added the comment:
Running test_socket test_ssl test_multiprocessing_fork
test_multiprocessing_forkserver test_multiprocessing_spaw under -F on the
buildbot, I got the following failure during the second loop:
[ 10] test_multiprocessing_spawn
Traceback (most recent call last
R. David Murray added the comment:
Here is a more useful traceback:
[394] test_multiprocessing_spawn
Timeout (1:00:00)!
Thread 0xb76a16c0:
File "/home/rdmurray/p34/Lib/multiprocessing/popen_fork.py", line 30 in poll
File "/home/rdmurray/p34/Lib/multiprocessing/popen_fork.
R. David Murray added the comment:
That's great, but without a patch it doesn't help me debug *this* failure :)
Any suggestions for getting more information out of that test (I'm not familiar
with multiprocessing...I'm already confused by the fact th
R. David Murray added the comment:
Final doc edits done. I will commit this next week if there are no objections,
in order to get it in to alpha 4.
--
Added file: http://bugs.python.org/file32055/master_content_manager.patch
___
Python tracker
R. David Murray added the comment:
See also issue 19154. For consistency with the rest of Python it should
probably raise ValueError. But at this point it has done what it does for a
long time (which is to return what the underlying posix function returns), so
we should probably just
R. David Murray added the comment:
Updated patch to address Serhiy's review comments. Also noticed a bug and
fixed it, adding a new 'is_attachment' attribute to EmailMessage/MIMEPart to do
so.
--
Added file: http://bugs.python.org/file32069/master_conten
R. David Murray added the comment:
My guess would be you are dealing with memory fragmentation issues, but I'll
let someone more knowledgeable confirm that before closing the issue :)
--
nosy: +r.david.murray
___
Python tracker
R. David Murray added the comment:
In 2.7 unexpected output is a test failure, yes.
In 3.x we removed that check. But I wonder if that was wise :) (We did it for
technical reasons when adding other features to regrtest).
Yes, using captured_stdout and checking for the expected warnings
R. David Murray added the comment:
Not really. But locals() is not reliably modifiable, and the vars
documentation also notes this.
--
nosy: +r.david.murray
resolution: -> invalid
stage: -> committed/rejected
status: open -> closed
_
R. David Murray added the comment:
Ethan, why did you reopen the issue? Do you have a different opinion, or was
it just an issue-update error?
--
___
Python tracker
<http://bugs.python.org/issue19
R. David Murray added the comment:
So don't make it random, use a hash of the code object :)
(I'm not sure I'm serious, the thought just popped into my head...)
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.pyt
R. David Murray added the comment:
Gah. Well, by good fortune 'o' comes before 'r' in the alphabet, so it should
be enough to just add 'oracle' to the list of _supported_dists in platform.py.
Can you test that and confirm it?
--
R. David Murray added the comment:
Yes, in this context ingnore, suppress, and silence all have essentially the
same problem, or lack of it, depending on your point of view.
Catch would be fine with me :)
Please note that someone *reading the thread* on python-dev misunderstood what
ignore
R. David Murray added the comment:
To be clear: I do think 'suppress' is better than 'ignore', for the reasons
Nick articulated.
--
___
Python tracker
<http://bug
R. David Murray added the comment:
It looks like test_wave is still failing on PPC64 PowerLinux:
http://buildbot.python.org/all/builders/PPC64%20PowerLinux%203.x/builds/850/steps/test/logs/stdio
--
___
Python tracker
<http://bugs.python.
New submission from R. David Murray:
See eg
http://buildbot.python.org/all/builders/AMD64%20Snow%20Leop%203.x/builds/158/steps/test/logs/stdio
--
keywords: buildbot
messages: 200104
nosy: r.david.murray
priority: normal
severity: normal
status: open
title: test_site is failing on AMD64
New submission from R. David Murray:
In issue 18891, Stephen Turnbull wondered if adding a datatype to represent
mime types would be worthwhile.
I think it would be. A mimetype is a pair (maintype/subtype), and while one
may test the subparts independently in logic, the representation and
R. David Murray added the comment:
Thanks everyone for the reviews. I've opened up a new issue for Stephen's
mimetype object suggestion (issue 19280).
I'm still planning to add some examples to the docs, so I'm going to leave this
open until I do that, but I wanted to
R. David Murray added the comment:
I fixed the out of space last night. (Someday I'll get around to figuring out
which test it is that is leaving a bunch of data around when it fails, but I
haven't yet).
I've installed strace and gdb on the bots, please send me your public ke
Changes by R. David Murray :
--
Removed message: http://bugs.python.org/msg200151
___
Python tracker
<http://bugs.python.org/issue19277>
___
___
Python-bugs-list m
R. David Murray added the comment:
Hmm. Looks like the name of the temp files used by the failing test (which is
in bsddb, by the way) have changed, so my delete command didn't delete them.
So now /tmp is definitely clean, and the next build on that bot should work
(crosses fi
R. David Murray added the comment:
Hmm. Looks like the name of the temp files used by the failing test (which is
in bsddb, by the way) have changed, so my delete command didn't delete them.
So now /tmp is definitely clean, and the next build on that bot should work
(crosses fi
R. David Murray added the comment:
Based on Marc-Andre recommendation at the end of issue 11678, I plan to commit
this as a bug fix, and add arch to 2.7 while I'm at it. Unless there are
objections.
--
nosy: +anikom15, eric.araujo, georg.brandl, pitrou, python-dev, terry.
R. David Murray added the comment:
Well, it's about backward compatibility, and the email module already uses str
subclasses for headers in the new code, for backward compatibility reasons. I
hope this does not prove fragile in practice, but I have no way of knowing for
sure, of course
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue19331>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
A complete fix is going to require setting a flag that we have a pending
non-local, and check that flag when the code input is complete to raise the
SyntaxError at that point if the non-local hasn't been set.
--
nosy: +r.david.m
R. David Murray added the comment:
Perhaps it would be better to say that "the argument may be any object with a
__len__, such as the commonly used Python sequence and container types str,
bytes, tuple, list, dict, and set". After all, there are other built in types
it works
R. David Murray added the comment:
I thought we were talking about the reference guide, not the tutorial?
--
___
Python tracker
<http://bugs.python.org/issue19
R. David Murray added the comment:
The only change on the buildbot for some months now was increasing the size of
the in-memory /tmp filesystem, which I did yesterday. That also involved a
reboot, though, and it is conceivable that there were software changes made
since the last reboot and
R. David Murray added the comment:
Are you saying that because you've lost interest, or because you think we have?
Sometimes things get lost here for a while, but picked up again later...
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
Nick: I agree with your reasoning. I don't know why I said what I did on the
other issue.
--
___
Python tracker
<http://bugs.python.org/is
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue19411>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by R. David Murray :
--
nosy: +dmalcolm
___
Python tracker
<http://bugs.python.org/issue19415>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
In the meantime the issue should be closed. It can be reopened if consensus is
reached.
--
nosy: +r.david.murray
resolution: -> postponed
stage: -> committed/rejected
status: open -> closed
___
Pytho
R. David Murray added the comment:
Indeed, you can see in the original posting that the \ is already gone from the
dollar in sys.argv, so argparse has nothing to do with it.
And it is indeed the shell doing the unescaping:
rdmurray@session:~>cat test.sh
#!/bin/bash
echo "$@"
rdm
R. David Murray added the comment:
Indeed, you can see in the original posting that the \ is already gone from the
dollar in sys.argv, so argparse has nothing to do with it.
And it is indeed the shell doing the unescaping:
rdmurray@session:~>cat test.sh
#!/bin/bash
echo "$@"
rdm
Changes by R. David Murray :
--
Removed message: http://bugs.python.org/msg201627
___
Python tracker
<http://bugs.python.org/issue19430>
___
___
Python-bugs-list m
R. David Murray added the comment:
Yes, it is a linux vserver VM. I would think we would want tests to not fail
in VMs, though, in this day and age.
--
___
Python tracker
<http://bugs.python.org/issue19
R. David Murray added the comment:
Also, unless people haven't been reporting other errors, these buildbots have
been stable up until recently, with the exception of the multiprocessing hangs
that plague all the buildbots as far as I know. (My impression could be
mistaken, t
R. David Murray added the comment:
See http://www.python.org/dev/peps/pep-0294/ for some background on this. The
unexpected thing is actually that the types module still exists at all in
Python3 :)
That said, its documentation could, indeed, use some improvement to address
this kind of
R. David Murray added the comment:
What could cause a VM clock problem on a machine that hasn't been modified, but
the VMs have been rebooted recently (ie: it isn't stale state inside the VM
itself). Anything you can suggest
R. David Murray added the comment:
I'm going to reboot the host just to see if that makes any difference. It's
been up for 105 days.
--
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
I would argue that the TypeError is correct (field names must be strings), even
though the way it is generated is a bit unorthodox :)
Let's see what others think.
--
nosy: +r.david.murray
___
Python tracker
R. David Murray added the comment:
Rereading my post I disagree with myself. ValueError is probably better in
this context (the difference between ValueError and TypeError is a bit grey,
and Python is not necessarily completely consistent about it
R. David Murray added the comment:
Python often defaults to the practical over the strictly-conforming (unless
there is a 'strict' flag :) We generally follow the lead of the browsers in
implementing our web related modules.
The situation here appears to be a real mess.
R. David Murray added the comment:
> But why should the field names have to be strings in the first place?
> Everything else is passed through str before being written anyway...
Good point.
--
___
Python tracker
<http://bugs.python.org/i
R. David Murray added the comment:
Yes, I said that link only dealt with the DNS side of things...where there are
also incompatibilities.
I don't think that strictly adhering to the URI RFCs would clear things up.
What about those domains that have _s and want to run web services on
R. David Murray added the comment:
msg.as_string should not be producing a CTE of 8bit. I haven't looked at your
patch so I don't know what you mean by having as_string produce 8bit data, but
it can't be right :)
To clarify: as_string must produce valid unicode data, and th
Changes by R. David Murray :
--
Removed message: http://bugs.python.org/msg201791
___
Python tracker
<http://bugs.python.org/issue19458>
___
___
Python-bugs-list m
Changes by R. David Murray :
--
status: open -> closed
title: Invitation to connect on LinkedIn -> spam
___
Python tracker
<http://bugs.python.org/i
R. David Murray added the comment:
cte base64 I think (see below).
Basically, set_payload should be putting the surrogateescape encoded utf-8 into
the _payload (which it should now be doing), and probably calling set_charset.
The cte will at that point be 8bit, but when as_string calls
R. David Murray added the comment:
as_bytes should be producing the raw utf8 bytes with cte 8bit.
--
___
Python tracker
<http://bugs.python.org/issue19
Changes by R. David Murray :
--
components: +email
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue19460>
___
___
Python-bugs-list mailing list
Unsub
R. David Murray added the comment:
A configurable option is probably the only way forward, due to backward
compatibility reasons, but Łukasz will know for sure. If so, it can only go in
the *next* version of Python, and while we haven't hit beta yet on 3.4 it may
be too late for anyo
R. David Murray added the comment:
Does conflict_handler='resolve' address your use case? It sounds like it
should.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
This was changed to %r by Benjamin Peterson in 27e470952085.
--
resolution: -> out of date
stage: needs patch -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
Here's my suggestion.
--
Added file: http://bugs.python.org/file32442/fcntl-doc.patch
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
I'm not sure how appropriate it is to "validate" a header using the Header
object. Header is for *composing* internationalized headers, and does no
validation to speak of. However, if you'd like to write a patch to add this
check, I w
R. David Murray added the comment:
It may be simple but as Ezio has pointed out, it has already been rejected :)
The problem with being generous in what you accept in this context is that the
parsing is using a specific format string, and the semantics of that format
string are based on
R. David Murray added the comment:
It's not my conclusion. It's Guido's and the other developers who designed
datetime. Argue with them. (I'd guess it would be better argued on
python-ideas rather than python-dev, but use your own judgement.)
--
st
R. David Murray added the comment:
I suppose in an ideal world the csv module would have some sort of hookable
serialization protocol, like the database modules do :)
--
___
Python tracker
<http://bugs.python.org/issue19
R. David Murray added the comment:
In the maintenance releases you should leave tagfind_tolerant defined with its
old value, with a comment that it is internal, no longer used, and has been
removed in 3.4.
--
___
Python tracker
<h
R. David Murray added the comment:
With the --git option, the rietveld service only tries against the default
branch. Without the --git option, it can figure out the changeset the patch is
based against and use that.
--
nosy: +r.david.murray
R. David Murray added the comment:
Vajrasky: FYI, you can select the 'email' component for tickets like this, and
I'll be automatically made nosy (as will Barry Warsaw).
--
components: +email
nosy: +barry
type: -> behavior
versions: +Pyth
R. David Murray added the comment:
It is there so that Python implementations (other than cPython) that do not
have ElementTree accelerator modules can fall back on the pure python version.
You can import the pure python version in cPython by blocking the import of the
C accelerator
R. David Murray added the comment:
Vajrasky: what do you think of my version? Is it clear enough?
I wonder if we want to document the constants someday.
--
stage: -> patch review
versions: +Python 2.7, Python 3.3
___
Python tracker
&l
R. David Murray added the comment:
Thanks, Vajrasky. Looks like this was a cut and paste error when Barry updated
the docs for 3.3, since it is correct in the 2.7 module.
--
resolution: -> fixed
stage: -> committed/rejected
status: open -&g
R. David Murray added the comment:
Thanks, Vajrasky. I modified the patch slightly since I prefer the term "bytes
object" to just "bytes" (I think it reads better in English).
--
resolution: -> fixed
stage: needs patch -> committed/rejec
R. David Murray added the comment:
Yes, you have to do the sys.modules set at the start of your application.
The python module is what gets imported, it is just that the C classes override
some of the classes from the Python module when they are imported. So no,
there's no way to mak
Changes by R. David Murray :
--
assignee: docs@python ->
nosy: +ncoghlan
___
Python tracker
<http://bugs.python.org/issue19487>
___
___
Python-bugs-list mai
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue19454>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Thanks, Vajrasky. I elected to apply this only to default, since it hasn't
caused any real-world problems. The (small but non-zero) chance of breaking
someone's code in the maintenance releases doesn't seem justified by the nat
Changes by R. David Murray :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue18678>
___
___
Python-bugs-list mailing list
Unsubscrib
R. David Murray added the comment:
Then for 3.3 you are bug fixing the regex, so anyone using it ought to want the
change, right? :)
If the same is true for 2.7, then creating an alias would probably be fine. I
haven't looked at the details, so I'll leave it to your judgment. I
5601 - 5700 of 10554 matches
Mail list logo
