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
R. David Murray added the comment:
So does default.
--
nosy: +benjamin.peterson, r.david.murray
type: -> crash
versions: +Python 2.7, Python 3.3
___
Python tracker
<http://bugs.python.org/issu
R. David Murray added the comment:
Yes, except that it would be:
class PostgressDB2Testcase(AbstractDB2Testcase, unittest.TestCasse):
The fact that other test frameworks have found it worth implementing indicates
there *might* be something worthwhile there, but unless someone makes the
R. David Murray added the comment:
Exhaustion of the iterator is easily solved by simply retaining a reference to
it and iterating that (which is what I had in mind). However, I had not
thought about the problem of an *in*exhaustable iterator, and to cover that
case len is indeed better
R. David Murray added the comment:
In this case it is not a potential security hole, since in fact the "GPF" comes
from Python explicitly calling Abort because of a situation it can't handle, as
indicated by the error message from Python. (If it were a true segfault-like
err
R. David Murray added the comment:
If you read what I wrote, I did not say that it wasn't a GPF. I said that an
Abort is different from writing into or reading from memory incorrectly (which
is what leads to security holes).
We don't have many Windows developers active enough to h
R. David Murray added the comment:
The docs are correct in Python3.
The docs for Python2 are not *wrong*, since they indicate only positional
parameters and if you use positional parameters it works as documented. (I'm
surprised that using keyword arguments works, but I haven't loo
R. David Murray added the comment:
It's not buggy, but it is also not helpful. This kind of thing is what we
introduced the 'strict' parameter for. And indeed I believe we've fixed some
of these cases thereby. So any additional fixes should go into non-str
R. David Murray added the comment:
Yes, but we don't claim to support HTML5 yet.
The best way to support HTML5 is probably a topic for python-dev.
--
___
Python tracker
<http://bugs.python.org/iss
R. David Murray added the comment:
I'm seeing this test failure in Gentoo, as well.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/i
R. David Murray added the comment:
I thought HTLM4 conformance was documented somewhere, but I could be wrong.
HTML5, from what I understand (I haven't read the spec), is explicitly or
implicitly following "what browsers really do" exactly because nobody conformed
to HTML4,
R. David Murray added the comment:
You are using Header incorrectly. It should look more like this:
th = _e_header.Header(maxlinelen=200, header_name='To')
th.append(tfc[:-1])
th.append(wtc[:-1], charset='utf-8')
th.append(tem)
This results in:
To
Changes by R. David Murray :
--
assignee: -> r.david.murray
___
Python tracker
<http://bugs.python.org/issue12649>
___
___
Python-bugs-list mailing list
Un
Changes by R. David Murray :
--
nosy: +gregory.p.smith
___
Python tracker
<http://bugs.python.org/issue12650>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Unless someone else has picked it up, BeautifulSoup is a no longer an issue
since its author has abandoned it. That doesn't change the fact that IMO it
would be nice for our library to handle input gener
R. David Murray added the comment:
You ought to be able to use either a context directive (I forget its name and
syntax), or the full reference syntax (:meth:`~threading.Thread.run`) to make
those links work without moving things around
R. David Murray added the comment:
They probably ought to be discussed in our docs :(
The only thing that may be encoded in an address is the "display name" (the
first part returned by parseaddr). (Actually the domain name could be IDNA
encoded, but we don't support that di
R. David Murray added the comment:
Interesting thread. I have my eye on supporting 5335 in the revised email
package, but it is secondary goal to getting an improved API for the
already-accepted RFCs.
You will note that the encoded word local part is *not* standard. I think the
email
R. David Murray added the comment:
Yes, exactly. It is a valid ascii token so MTA's pass it through. It's the
receiving system that needs to be willing to decode it.
--
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
It sounds like the early consensus on python-dev is that html5 support is a
good thing. I'm happy with that. I presume that means the 'strict' keyword in
3.x becomes strict-per-html5, and p
R. David Murray added the comment:
Sorry I didn't look at the patch earlier. I thought we were just *moving*
pipes.quote. Why is a new regex involved?
--
___
Python tracker
<http://bugs.python.org/i
R. David Murray added the comment:
Well, it's a micro-optimization (it would be interesting to benchmark, but not
worth it). I find the original code much more readable than the regex, but it
doesn't matter all that much. (And as far as optimization goes, using
translate mig
R. David Murray added the comment:
You aren't using a regex to replace the quotes, either.
>>> len('abcd'.translate(str.maketrans('', '', string.ascii_letters ))) > 0
False
I don't know if this is faster than the corresponding search rege
R. David Murray added the comment:
My immediate reaction is that this is too specialized. We'll see what others
think.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/is
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue10087>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by R. David Murray :
--
resolution: -> duplicate
status: open -> closed
superseder: -> Windows installer should add Python and Scripts directories to
the PATH environment variable
___
Python tracker
<http://bugs.python.or
Changes by R. David Murray :
--
resolution: -> duplicate
stage: -> committed/rejected
status: open -> closed
superseder: -> "pydoc str" works but not "pydoc str.translate"
type: -> behavior
___
Python tracker
Changes by R. David Murray :
--
resolution: -> duplicate
stage: -> committed/rejected
status: open -> closed
superseder: -> segmentation fault in listextend during install
___
Python tracker
<http://bugs.python
R. David Murray added the comment:
I'm not familiar with the parser internals (I'm nosying someone who is), but I
suspect what you are seeing at the command line is the errors being caught at a
stage later than the tokenizer.
--
nosy: +benjamin.peterson, r.da
Changes by R. David Murray :
--
nosy: +brett.cannon, ncoghlan
___
Python tracker
<http://bugs.python.org/issue12680>
___
___
Python-bugs-list mailing list
Unsub
R. David Murray added the comment:
Well, this is actually blessed by http://www.python.org/dev/peps/pep-0257/, but
if that convention were actually followed the docstring would go *after* the
assignment. But I agree that it is rarely used, and as far as I know is not
used in the stdlib at
R. David Murray added the comment:
On Tue, 02 Aug 2011 12:12:37 +0200, Stefan Krah wrote:
> I suspect many buildbots are green because they don't have tr_TR and
> tr_TR.iso8859-9 installed.
This is true for my Gentoo buildbots. Once we've figured out the
best way to handl
New submission from R. David Murray :
I think that it would be good for expectedFailure to take a message argument
like skip does. My thought is that it would be printed both when it is
triggered (the test fails as expected) so that one case from the verbose output
why the test is expected
New submission from R. David Murray :
The devguide documents the 'accepted' resolution as follows:
Submitted patch was applied, still needs verifying (for example by
watching the buildbots) that everything went fine. At that point the
resolution should be set to fix
R. David Murray added the comment:
It is not ambigous. As I said, bugs are fixed, feature requests are accepted.
--
___
Python tracker
<http://bugs.python.org/issue12
R. David Murray added the comment:
This is partly a doc issue, but there also appear to be bugs in the way the
existing functionality works (although it is hard to tell for sure since it
isn't documented :)
Try using the value argparse.SUPPRESS as the value of help= in various places
Changes by R. David Murray :
--
nosy: +lukasz.langa
___
Python tracker
<http://bugs.python.org/issue12688>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Duplicate of 1028.
--
nosy: +r.david.murray
resolution: -> duplicate
stage: -> committed/rejected
status: open -> closed
superseder: -> Tkinter binding involving Control-spacebar raises unicode error
type: crash
R. David Murray added the comment:
I'm pretty sure this was intentional. It is analogous to Skip messages and the
messages issued when a resource hasn't been enabled, which also print when
verbose is not true: the test wasn't run, and it lets you know why.
--
nosy:
Changes by R. David Murray :
--
title: Tools/Scripts/crlv.py needs updating for python 3+ ->
Tools/Scripts/crlf.py needs updating for python 3+
type: crash -> behavior
___
Python tracker
<http://bugs.python.org/i
Changes by R. David Murray :
--
resolution: -> duplicate
stage: -> committed/rejected
superseder: -> Tools/Scripts/crlf.py needs updating for python 3+
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
I don't see any such code in the 3.3 source for the context manager. There the
resource name is put in the ResourceDenied message. I think we'll need the
reproducer.
--
___
Python trac
Changes by R. David Murray :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue12694>
___
___
Python-bugs-list mailing list
Unsubscri
R. David Murray added the comment:
Well, you could consider codecs an example in the stdlib of using it, and the
doc could be changed to something like "stdlib modules that look up information
in specialized data sources may raise this error directly". Whether this is a
good i
R. David Murray added the comment:
Perhaps we should issue a warning, then, too?
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue12
R. David Murray added the comment:
Well, as long as 'accepted' is under 'resolution', I'm likely to keep using it
for feature requests, I suppose because I'm too much of a precisonist. If
someone wants to re-engineer the interface, that would be fine with me :)
R. David Murray added the comment:
I think we've moved from discussing a documentation issue to discussing a
procedural issue in the development process. I'm not sure what forum that
belongs in, though I believe in the past we have used tracker-discuss for that.
That said, I
R. David Murray added the comment:
Nope, optionals is what argparse calls them.
--
nosy: +r.david.murray
resolution: -> invalid
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
This issue is about the fact that it doesn't return (None, None). We should
probably decide what we are going to do about that before changing the docs if
they need it.
--
___
Python tracker
R. David Murray added the comment:
"optionals only" means the same thing as "options only", but 'optionals' is
what argparse calls them (as contrasted with positionals).
'optionals' is only used two places in the doc and isn't defined, but i
R. David Murray added the comment:
Vinay: you want to mark importer as a static method anyway, otherwise it won't
work with pypy. I don't know why this would show up on CPython, though.
--
nosy: +r.david.murray
___
Python trac
R. David Murray added the comment:
But what if the empty string is valid input? This change would be backward
incompatible.
I think this should instead be a feature request for exposing _QueryDialog so
that you can subclass it and provide your own getresult function.
--
nosy
R. David Murray added the comment:
Yes a new issue would be more appropriate.
--
___
Python tracker
<http://bugs.python.org/issue6203>
___
___
Python-bugs-list m
R. David Murray added the comment:
Adding an option would also be a reasonable feature request, but I think
exposing _QueryDialog would be a more general solution, since it would apply to
more than just strings.
While not backward incompatible, either of these is a new feature and so can
Changes by R. David Murray :
--
nosy: +ncoghlan
___
Python tracker
<http://bugs.python.org/issue12718>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
This is an acknowledged problem with Python narrow builds, and applies to much
more than just regex processing.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue12
R. David Murray added the comment:
I think the only way re is going to get "spiffed up" is by replacing it with
Matthew's library. This is a goal, but I'm not sure where exactly we are in
the process. The more Matthew's code gets tested (especially for compatibility
R. David Murray added the comment:
A bit of both, I think. The current function is actually 'getvalue' and is
responsible for retrieving the value, validating its type, and converting to
that type (the current ones do both in the same operation). It feels to me
like a cleaner in
R. David Murray added the comment:
Tom, note that nobody is arguing that what you are requesting is a bad thing :)
As far as I know, Matthew is the only one currently working on the regex
support in Python. (Other developers will commit small fixes if someone
proposes a patch, but no one
R. David Murray added the comment:
As a new feature, this could only go into 3.3.
--
nosy: +r.david.murray
versions: -Python 3.2
___
Python tracker
<http://bugs.python.org/issue12
R. David Murray added the comment:
In what way does 'replace' not satisfy your need to set the tzinfo?
As for utcnow, we can't change what it returns for backward compatibility
reasons, but you can get a non-naive utc datatime by doing
datetime.now(timezone.utc). (I must
R. David Murray added the comment:
Ah. Well, pre-3.2 datetime itself did not generate *any* non-naive datetimes.
Nor do you need to specify everything for replace. dt.replace(tzinfo=tz)
should work just fine.
--
resolution: -> invalid
stage: -> committed/rejected
status
Changes by R. David Murray :
--
nosy: +belopolsky
___
Python tracker
<http://bugs.python.org/issue12756>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
OK. At a minimum there is a doc issue here, so I'm reopening.
--
nosy: +belopolsky
resolution: invalid ->
status: closed -> open
title: datetime.datetime timezone problems -> datetime.datetime how to
correctly attach a timezone to an
R. David Murray added the comment:
>From a quick look at the code and docs I suspect that 'n' is an internal
>implementation detail and not meant to be exposed. Is there an use case for
>notifying waiters where n!=1 and n!=len(waiters)? If my speculation is
>correct i
R. David Murray added the comment:
Good point. Probably, then, we should just put a comment in the code that 'n'
is an internal implementation detail and leave it at that.
--
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
MAL wrote:
> As already mentioned, the diff between Linux 2.x and 3.x will
> grow over time and while there may not be much to see now,
> things will change in the coming years.
The only way I can read this argument that makes any sense to me is
R. David Murray added the comment:
Following on to Georg's comment about expressions, as a workaround, note
that:
with (
open('abc')) as foo:
works.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.pyt
Changes by R. David Murray :
--
assignee: -> r.david.murray
___
Python tracker
<http://bugs.python.org/issue12788>
___
___
Python-bugs-list mailing list
Un
R. David Murray added the comment:
That was a correct decision :)
It certainly shouldn't be simply deleted, since that would break backward
compatibility. Barry, is this something we (ie: you, in this case :) wish to
continue to maintain?
If not, we have the options of deprecatio
New submission from R. David Murray :
The attached test case fails.
--
assignee: r.david.murray
files: formataddr_paren_test.patch
keywords: easy, patch
messages: 142725
nosy: r.david.murray
priority: normal
severity: normal
status: open
title: email.utils.formataddr incorrectly quotes
R. David Murray added the comment:
Hmm. The output of formataddr is not actually incorrect, it just overquotes
compared to what is required by the RFC. Attached is a fix, but since this
isn't technically an RFC bug, I'm removing 3.2 and 2.7 from versions.
--
keywords: -
New submission from David H. Gutteridge :
I stumbled across this bug because of a misunderstanding I had about how the
pyexpat module works. I'd inferred that a given instance could be reused to
parse multiple files, which is apparently not supported. (There's already a
documen
David H. Gutteridge added the comment:
I believe this may be an OS-specific bug somehow, albeit one that affects
multiple OSes. I cannot duplicate the crash on NetBSD 5.1_STABLE/i386 with
Python 2.6.7, or on OpenSuSE 11.3 with Python 2.6.5. (It's interesting that it
doesn't cr
David H. Gutteridge added the comment:
Here's the (non-debug) trace under OS X:
Process: Python [4604]
Path:
/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python
Identifier: Python
Version: ??? (???)
Code Type:
New submission from R. David Murray :
A common problem encountered when using python3 is writing non-ascii to stdout.
This will work fine if stdout is a terminal and the terminal encoding handles
the characters, but will fail if stdout is later redirected to a pipe. The
docs for sys.stdout
R. David Murray added the comment:
Victor says it defaults to LOCALE in 3.3. The documentation should still be
expanded to mention this even in 3.3, though.
--
___
Python tracker
<http://bugs.python.org/issue12
R. David Murray added the comment:
Ah, this was actually fixed in 3.2, so it is only 2.7 where there is the
different (and long standing) problem of output of unicode to a pipe.
So, the doc issue boils down to mentioning how the encoding for stdout/stderr
is derived (LOCALE, overridden by
David H. Gutteridge added the comment:
The documentation should definitely be updated to clarify that a parser
instance is not reusable with more than one file. I had a look at the
equivalent documentation for Perl and TCL, and Perl's implementation explicitly
does not allow attemp
David H. Gutteridge added the comment:
Terry: I wasn't aware xml.parsers.expat is deprecated, though it clearly says
so in the documentation, I now see... (I'd been using it because it features
prominently in various examples in Python books, and it's lightweight.) I
have
David H. Gutteridge added the comment:
Confirming that Python 3.2.1 crashes the same way on Mac OS X 10.6.8:
Process: Python [9594]
Path:
/Library/Frameworks/Python.framework/Versions/3.2/Resources/Python.app/Contents/MacOS/Python
Identifier: Python
Version
David H. Gutteridge added the comment:
Further details:
- The original test case I'd submitted crashed on the development branch of
NetBSD as well as Mac OS X Snow Leopard, but not the most recent stable branch
of NetBSD. I've found a separate test case that crashes on both b
David H. Gutteridge added the comment:
Ned: My proposed wording is: "Note that only one document can be parsed by a
given instance; it is not possible to reuse an instance to parse multiple
files." To provide more detail, one could also add something like: "The
isfinal argume
2401 - 2500 of 12936 matches
Mail list logo
