R. David Murray added the comment:
Well, sys.stdout and sys.stderr don't have to be real file objects. You could
substitute a file-like object (one that implements the methods that get called
during the interpretation loop) that does your multiplexing. That kind of
trick is one o
R. David Murray added the comment:
No, that's correct. In python 2.x the 'bytes' stuff is just a portability aid.
In 2.x, bytes and string are the same type. In Python 3 they aren't, so by
using the 'fake' classes in python2 you can often make your code work
R. David Murray added the comment:
I think we'll have to wait for Micheal to double check, but it looks to me like
there is a bug in unittest.TextTestResult. TestResult's init expects the three
arguments the OP is talking about, but defaults them to None. TextTestResult
accepts t
Changes by R. David Murray :
--
title: unittest.TextTestResult.__init__ breaks under complex __mro__ ->
unittest.TextTestResult.__init__ does not pass on its init arguments in super
call
versions: +Python 3.2, Python 3.3
___
Python tracker
&l
R. David Murray added the comment:
I know this is closed so the comment may not be relevant, but the byte/string
issues with email should be sorted out in the code that is in 3.2/3.3 at this
point. That is, it is possible once again to work with binary data, using the
correct (new) classes
R. David Murray added the comment:
In another issue Georg came up with the idea of creating an availability
directive that would auto link to the appropriate text. This would then apply
to all our different availability types.
--
___
Python
R. David Murray added the comment:
I don't believe we have any desire to support unix systems that do not define
'python', and 'python3' executables in the path. If the distribution wishes to
do that they'll have to patch everything to accommodate it.
That h
R. David Murray added the comment:
rdmurray>python2.6 py27-str-unicode-bytes.py
type(b)=
Traceback (most recent call last):
File "py27-str-unicode-bytes.py", line 17, in
unicode_str += b # this line will throw UnicodeDecodeError on Python 2.7
UnicodeDecodeError: '
R. David Murray added the comment:
To clarify: if I convert your program to using strings pre2.6, it still fails
with a UnicodeDecodeError, as one would expect. bytes are strings in 2.x.
--
___
Python tracker
<http://bugs.python.org/issue12
R. David Murray added the comment:
And finally, your program does *not* succeed on Python3, except in the trivial
sense that on python3 you never attempt to add the string and bytes data. It
is exactly this kind of programming error that Python3 is designed to avoid:
instead of sometimes
R. David Murray added the comment:
But senthil already demonstrated in the previous issue that it does not become
a unicode string unless you use unicode input.
You also claimed that your test program here succeeded in python2.6, but it
does not. This casts a little bit of doubt on your
R. David Murray added the comment:
The problem isn't with getpass, the problem is that getpass is generating a
warning message on first call and idle isn't handling that correctly. Your
suggested fix is probably correct.
--
nosy: +r.david.murray, terry.reedy
stage: ->
Changes by R. David Murray :
--
nosy: +orsenthil
___
Python tracker
<http://bugs.python.org/issue12439>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Hmm. I thought Antoine got rid of the output checking when he added -j
support. Well, he was the one who did it, anyway, so there may be a change set
you could backport to get rid of the output checking if you want to backport
this to 2.7
R. David Murray added the comment:
Thanks for taking a crack at this. IMO the thing that needs to be fixed here
is that receiving an invalid cookie makes it difficult to receive the valid
cookies. I'd love to accept your patch, but "silently ignore" sounds like a
bad idea a
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue12448>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Well, it's been a while since I looked at the cookie code, and I didn't review
it when I reviewed your patch. But some time after I hit submit on my message
the issue about some stuff getting ignored anyway occurred to me. So given
that we ar
R. David Murray added the comment:
Well, it's unnoficially configurable pre-3.2 (set _MAXCACHE on the module).
The lru_cache implementation doesn't have such an undocumented way of tweaking
the limit. In neither case, however, is it true that "nothing is ever cached".
R. David Murray added the comment:
Grr. "it is *not* true that nothing is ever cached".
--
___
Python tracker
<http://bugs.python.org/issue7846>
___
___
R. David Murray added the comment:
Well, three occurrences means you only have three methods to patch (and two of
them are trivial). But I agree that copying the non-trivial method doesn't
look fun from a maintenance perspective.
You could also try using an object that is not a subcla
R. David Murray added the comment:
Well, judging by your test it isn't capitalize that's the issue. capitalize
produces Content-md5, whereas debug is showing urllib2 sending Content-Md5. So
something else is massaging the header na
R. David Murray added the comment:
A feature request for a way to control this is reasonable. However, new
features can only go into 3.3.
--
stage: -> needs patch
title: urllib2 Request() forces capitalize() on header names, breaking some
requests -> urllib2 forces titl
R. David Murray added the comment:
If I ssh in to a machine, python should not *crash* if I run gui stuff. The
test suite might generate errors rather than skips (although I would argue that
it should generate skips), but it should not crash.
On the other hand I agree that fixing the
R. David Murray added the comment:
Inner classes can't be pickled (see the pickle docs for what can be pickled).
Whether or not there is a bug in the repr of the inner class is an interesting
question.
--
nosy: +r.david.murray
type: crash ->
R. David Murray added the comment:
Quoting http://tools.ietf.org/html/rfc2068#section-4.2:
Field names are case-insensitive.
Which is only logical, since they are modeled on email headers, and email
header names are case insensitive. So, the server in question is broken, yes,
but that
R. David Murray added the comment:
Yeah, that's why I had reopened the issue...hopefully it is fixed now.
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.
R. David Murray added the comment:
I guess I'm just really bad at regexes.
http://www.python.org/dev/buildbot/all/builders/x86%20XP-4%203.x/builds/4885/steps/test/logs/stdio
--
status: closed -> open
___
Python tracker
<http://bugs
R. David Murray added the comment:
Well, it's not applicable to 2.x, since it is a feature request. As such it
could only go into 3.3. I don't have an opinion on the merits of the
suggestion.
--
nosy: +r.david.murray
versions: +Python 3.3 -Python 2.6,
R. David Murray added the comment:
I'm going to be an optimist and close this again.
--
status: open -> closed
___
Python tracker
<http://bugs.python.org
Changes by R. David Murray :
--
stage: commit review -> committed/rejected
___
Python tracker
<http://bugs.python.org/issue12442>
___
___
Python-bugs-list mai
R. David Murray added the comment:
I tweaked the patch a bit (mostly style/cosmetic) and added some additional
tests. Thanks, Nicolas!
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
___
Pytho
R. David Murray added the comment:
Indeed, Victor's comments on his patch say that he changed code that was in the
posted patch to say 'line.startswith(b'--')', and the original patch did use
b'--', but the code he checked in is missing the 'b'.
Changes by R. David Murray :
--
nosy: +ncoghlan
___
Python tracker
<http://bugs.python.org/issue12475>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
But pypy passed the attribute access tests in the test suite?
--
___
Python tracker
<http://bugs.python.org/issue12
R. David Murray added the comment:
You are correct that this is a feature request as written. I think there is
also a doc bug (the docs should probably mention that changing delimiter after
class creation is a no-op).
To add this feature the computation of the regex would need to be moved
R. David Murray added the comment:
As an experienced Python programmer, I think of 'attribute' as meaning any
attribute (method or non-method) of an object or class. I sometimes do use it
imprecisely (to my mind) to mean "non-method attribute", and it is usually
clear
Changes by R. David Murray :
--
components: +Library (Lib) -None
nosy: +giampaolo.rodola
___
Python tracker
<http://bugs.python.org/issue12523>
___
___
Python-bug
Changes by R. David Murray :
--
type: crash -> behavior
___
Python tracker
<http://bugs.python.org/issue12523>
___
___
Python-bugs-list mailing list
Unsubscri
R. David Murray added the comment:
OK, I found the other issue and it looks like we agreed to use 'attributes and
methods' where the reference was inclusive. I still think that it is less
precise to think this way, but it is clearer exposition given the lack of a
good term for
R. David Murray added the comment:
The email module header parser handles this correctly (if you make it a real
header). For whatever that's worth :)
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
Unless you can point to a place where the behavior that was fixed is actually
documented, this is classed as an implementation detail that was changed (or,
more likely, a bug that was fixed). If this were less obscure or had been in
existence for longer
R. David Murray added the comment:
You are better off opening a new issue as a feature request. Do add at least
belopolsky as nosy on the new issue.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue1
R. David Murray added the comment:
This is not a bug fix, but a feature request. In Python3 the classes are of
course new style. So there's nothing to do here, sorry.
--
nosy: +r.david.murray
resolution: -> out of date
stage: -> committed/rejected
status: ope
New submission from R. David Murray :
Consider the following traceback:
Traceback (most recent call last):
File "/home/rdmurray/python/email6/Lib/email/message.py", line 466, in
__getattr__
return getattr(self._headers, key)
AttributeError: '_Header_List' obj
New submission from R. David Murray :
The mailbox module has a method _become_message that copies attributes from an
object that is an email.message.Message subclass to the calling object (which
is also a subclass of email.message.Message). This method is very fragile in
the face of any
R. David Murray added the comment:
I think the reason the chained tracebacks look backward to me is twofold: I'm
used to the last one in the list being the *only* one I get (in python2), and
the last one in the list is often the one I want to deal with first. This is
especially true
R. David Murray added the comment:
One can argue that it is necessary to read the traceback in reverse order, so
that reading the chain in reverse order is a logical extension of that. So I
guess I have no serious objection to this being rejected
R. David Murray added the comment:
To set the value of an immutable type you must use the __new__ method. By the
time __init__ is called the value has already be established, and in the case
of int it defaults to 0.
--
nosy: +r.david.murray
resolution: -> invalid
st
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue12485>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Maybe they don't support all Sequence operations? They don't support slicing,
certainly, but I can't tell from the collections ABC docs if Sequence is
required to support slicing.
--
nosy: +r.david.mur
R. David Murray added the comment:
This isn't going to get fixed in 2.x (shlex doesn't support unicode in 2.x, and
doing so would be a new feature). In 3.x all strings are unicode, so the
problem you are seeing doesn't exist. This issue is about the broader problem
of what c
R. David Murray added the comment:
This should do what you want:
from email import charset
charset.add_charset('utf-8', charset.SHORTEST, charset.QP)
This will override the default handling of utf-8 (which is BASE64, as you note).
If this doesn't solve your problem pl
New submission from R. David Murray :
Most MTA/MTUs these days can handle 8bit just fine. I think that the CTE for
MIMEText parts should default to 8bit unless policy.must_be_7bit is set. This
will require adding support for this CTE to Charset. The Policy docs imply
that this is already
R. David Murray added the comment:
Opened issue 12553 for the 8bit feature request.
--
___
Python tracker
<http://bugs.python.org/issue12552>
___
___
Python-bug
R. David Murray added the comment:
Good point. In 2.x that will work, and will give you the 8bit CTE at need, as
long as you pass encoded text to MIMEText (as opposed to unicode...which it
doesn't really handle correctly if I recall
R. David Murray added the comment:
Michael, if you have no objection to this patch I'm willing to commit it.
--
___
Python tracker
<http://bugs.python.org/i
R. David Murray added the comment:
That can't be done. If an import fails, it fails. But if it succeeds, the
module is loaded, and there is no reason to unload it. After all, import in
python is idempotent (doing it a second time has no effect other than adding
the name to the
R. David Murray added the comment:
OK, here is a new patch proposal. As suggested by Alexander, it adds two
functions to email.utils: format_datetime and parsedate_to_datetime. Adding
these does not require having localtime. In fact, with this patch you can get
an aware datetime
R. David Murray added the comment:
Yes, that's exactly my point. The loading of a module into sys.modules is a
separate issue from the creation of a pointer to that module in the local name
space. Once the former succeeds, it has succeeded and won't be done again.
When the modul
R. David Murray added the comment:
In fact, to hopefully make perfectly clear what is going on here, let me
demonstrate that *any* executable statement in the module that fails to load is
executed if it occurs before the error that causes the load failure:
rdmurray@hey:~/python/p32>
Changes by R. David Murray :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue12548>
___
___
Python-bugs-list mailing list
Unsubscri
R. David Murray added the comment:
The tracker is a place to report bugs not get help. (We don't have the
manpower to provide help services here.) Please try the python-list mailing
list (gatewayed to comp.lang.python) or the python-tutor mailing list.
--
nosy: +r.david.m
R. David Murray added the comment:
FYI 'crash' is for segfault. A traceback is "just a bug" :)
I'm not sure that this it is worth having this as a separate bug from #10647,
but I'll let someone with tk knowledge decide that.
--
nosy: +kbk, r.david.
Changes by R. David Murray :
--
nosy: +gpolo
___
Python tracker
<http://bugs.python.org/issue12558>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by R. David Murray :
--
superseder: scrollbar crash in non-US locale format settings ->
___
Python tracker
<http://bugs.python.org/issue12558>
___
_
R. David Murray added the comment:
spam
--
nosy: +r.david.murray
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue12563>
___
___
Python-
R. David Murray added the comment:
spam
--
nosy: +r.david.murray
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue12566>
___
___
Python-
R. David Murray added the comment:
spam
--
nosy: +r.david.murray
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue12565>
___
___
Python-
R. David Murray added the comment:
spam
--
nosy: +r.david.murray
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue12564>
___
___
Python-
R. David Murray added the comment:
This is a purity versus practicality argument. I agree with both sides :)
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue11
R. David Murray added the comment:
I haven't reviewed your tests, but a couple quick comments: we generally prefer
duck typing to the use of isintance or ABCs, but sometimes the latter is better
(it's a judgement call). I haven't done a deep dive in the code you modified,
but
Changes by R. David Murray :
--
nosy: +orsenthil
___
Python tracker
<http://bugs.python.org/issue12581>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Also, are you using a linux3 kernel?
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue12582>
___
___
R. David Murray added the comment:
No. We know we have some issues with platform stuff on linux3 kernels, though,
which why I asked.
--
___
Python tracker
<http://bugs.python.org/issue12
R. David Murray added the comment:
Well, at this point we have no idea. It works fine for us. This part is all
controlled by the Makefile, maybe you can do some debugging on it.
--
___
Python tracker
<http://bugs.python.org/issue12
Changes by R. David Murray :
--
Removed message: http://bugs.python.org/msg59741
___
Python tracker
<http://bugs.python.org/issue1221>
___
___
Python-bugs-list m
R. David Murray added the comment:
Woops, hit a button wrong and managed to delete a message. It just said:
See Issue1025395
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue1
R. David Murray added the comment:
Thank you both for your work on this. The patch I committed is a combination
of my _addr_only, Filipe's tests, and Catalin's modifications to those tests.
quoteaddr, although in the __all__, is not documented and is really an
implementation det
R. David Murray added the comment:
Don't short change yourself. This bug would still be open if it hadn't been
for your work, regardless of how much of it wound up in the final patch :)
--
versions: +Python 3.3 -Python 2.6, Python 3.1
New submission from R. David Murray :
The work I've been doing on email6 has reached a stage where I'm confident
about the overall plan of the new code, and am ready for people to review it
and make suggestions. The patch represents a working state of the code, but
with several
Changes by R. David Murray :
--
keywords: +patch
Added file: http://bugs.python.org/file22699/b22698463737.diff
___
Python tracker
<http://bugs.python.org/issue12
Changes by R. David Murray :
Added file: http://bugs.python.org/file22700/README.txt
___
Python tracker
<http://bugs.python.org/issue12586>
___
___
Python-bugs-list mailin
R. David Murray added the comment:
Yes, there are ways other than an import statement that a module can get
imported (the __import__ function, for example, and the imp module for another,
as well as importlib).
If you want to try your hand at writing a patch to do the post mortem you will
R. David Murray added the comment:
This isn't a problem with ConfigParser, it's a problem with the text file
object returned by Subprocess. You can reproduce the bug by trying to iterate
over the TextIOWrapper returned by subprocess.
(It is true, however, that the ConfigParser d
R. David Murray added the comment:
It might. Although I did miss your message about the flag, my point really was
that you'll find that import is very complicated when you try to write the
patch to do it. There may not be one central place you can set and query that
flag, because o
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue7897>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Brian, if you don't have time to work on it in the next little while, maybe you
could post your partial patch in case someone else wants to work on it? Might
be a good project for someone on the mentoring list.
Unless someone sees a clever way to impl
R. David Murray added the comment:
Michael, would your "single test" clearly indicate all the individual failures
by name? If not, then I would not find it useful. I can already easily
"parameterize" inside a single test using a loop, it's the detailed reporting
R. David Murray added the comment:
The reporting piece, and ideally being able to use the arguments to unittest to
run a single one of the parameterized tests. (I can get the reporting piece
now using the locals() hack, but that doesn't support test selection). Does
test selection su
R. David Murray added the comment:
Fixed a bug (parsedate_to_datetime wasn't producing naive datetimes for -)
and checked this in.
Note that I have added Alexander's 'localtime' function to email.utils in my
feature branch/pypi release, to facilitate testing date he
R. David Murray added the comment:
If the load produces the same result, why does it matter that what is on disk
differs?
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue12
R. David Murray added the comment:
Well, if the test doesn't fail before applying the remainder of the patch, then
it doesn't test the bits that haven't been applied yet.
I don't know enough about aifc to construct a test that fails or to understand
the remainder of th
R. David Murray added the comment:
I'm not sure what your example is trying to achieve, but the list(tuple(...))
looks redundant.
Your initial example could be written:
b = [[0] for i in range(3)]
--
nosy: +r.david.murray
___
Python tr
R. David Murray added the comment:
Personally I would be happy if I could pass in a dictionary that maps names to
argument tuples, or an iterator yielding (name, (argtuple)) pairs, and just
have the failure report the name. That is, make me responsible for generating
meaningful names, don&#
R. David Murray added the comment:
Note that this is fairly simple to do now via subclassing, so any proposed API
would need to show a clear benefit over that approach to be worth the extra
complexity in the unittest code base.
--
___
Python
R. David Murray added the comment:
Please implement name+argtuple first and build auto-naming on top of that.
Nick's approach would not allow me to specify a custom (hand coded) name for
each set of arguments, which is my normal use case. I also would not like the
arguments auto-gene
Changes by R. David Murray :
--
Removed message: http://bugs.python.org/msg140810
___
Python tracker
<http://bugs.python.org/issue7879>
___
___
Python-bugs-list m
R. David Murray added the comment:
Please implement name+argtuple first and build auto-naming on top of that.
Nick's approach would not allow me to specify a custom (hand coded) name for
each set of arguments, which is my normal use case. I also would not like the
arguments auto-gene
R. David Murray added the comment:
Oh, I see. Make the name the first element of the argtuple and then strip it
off. Well, that will work, it just seems bass-ackwards to me :)
And why is it 'case'? I thought we were talking a
R. David Murray added the comment:
So this is a doc bug in subprocess? Explaining this clearly doesn't sound like
much fun...
--
___
Python tracker
<http://bugs.python.org/is
301 - 400 of 10554 matches
Mail list logo
