R. David Murray added the comment:
I would expect this code to report an error of some sort, not pass as an
expected failure. The expected failure should be in the test case *only*, not
in the setup or teardown methods. That is, I don't think this is a bug, I
think it is a feature
R. David Murray added the comment:
I'm working on it.
--
___
Python tracker
<http://bugs.python.org/issue10453>
___
___
Python-bugs-list mailing list
Unsubsc
R. David Murray added the comment:
Here's the test. The fix isn't as simple as making it nargs='*', though.
--
Added file: http://bugs.python.org/file19960/compileall_multidir_test.diff
___
Python tracker
<http://bug
R. David Murray added the comment:
Here is a fix. This is not finished, though, because I see that I did not do
an adequate review of the original patch. There are still bugs in the -d and
-i handling that need both tests and fixes.
--
Added file: http://bugs.python.org/file19961
R. David Murray added the comment:
I suspect this is a duplicate of issue 9614, or rather a subset of that issue.
--
nosy: +alexandre.vassalotti, amaury.forgeotdarc, janglin, pitrou, r.david.murray
___
Python tracker
<http://bugs.python.
R. David Murray added the comment:
I just tried using script_helper in a new test, so I have a couple of comments.
I don't see stdout and stderr being conflated, it looks to me like they are
returned separately, at least by the assert methods.
The assert methods return results, whi
Changes by R. David Murray :
--
nosy: +michael.foord
___
Python tracker
<http://bugs.python.org/issue9517>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Wow, I didn't realize that's how logging worked. My understanding was a module
should just get a logger and log messages, and if the application didn't do any
setup beforehand, the first logging call would cause messages to be written to
st
R. David Murray added the comment:
I have to say that it would never have occurred to me to assert a pre or post
condition and an expected failure where I expected the pre or post condition to
fail, but if you've got a real use case and it would make the code simpler, I
suppose I ha
R. David Murray added the comment:
OK, fine on the convention, but I'd still like a more memorable name for
assert_python_failure. I've been working on this issue off and on today, and
I've had to look up that name at least four times. I can remember
assert_python_ok, but I
Changes by R. David Murray :
--
stage: -> committed/rejected
type: crash -> behavior
___
Python tracker
<http://bugs.python.org/issue10643>
___
___
Pyth
R. David Murray added the comment:
If the problem is in site.py it doesn't sound like a distutils bug at all. I
remember Victor doing something that changed the error handling/reporting when
importing site.py, so I'm adding him as nosy. I thought that was only in 3.x,
though.
R. David Murray added the comment:
I believe that in the absence of other documentation the ABC is considered
authoritative.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue9
R. David Murray added the comment:
I'm not sure what bug you are reporting here. Are you saying that values using
a , are automatically getting generated by tkinter and then rejected when fed
back in? If so, I suspect this is a tk problem, not tkinter problem, but
someone would ha
R. David Murray added the comment:
On gentoo linux with tcl/tk 8.5.8, if I use the following command line:
>LC_NUMERIC=fr_FR ../release31-maint/python ListboxScrollbarLocaleIssue.py
(which runs 3.1.3+) I can move the slider without any problem. I confirmed
that locale.format_string(
R. David Murray added the comment:
Well, it sounds like you are on Windows, which is a platform I'm not all that
familiar with. I think we bundle TK for the windows installer, but I'm not
100% sure. I think to use a different version you have to recompile Python,
which on Window
R. David Murray added the comment:
As you observe, the attribute is not read only, it simply isn't referred to
when special method lookup is done. This is specified as part of the language
design for new style classes, but has only been made consistently true in
recent versions.
On o
R. David Murray added the comment:
Here is a patch that causes _assert_python to remove the refcount lines from
stderr.
--
keywords: +patch
Added file: http://bugs.python.org/file19975/script_helper_del_refcount.patch
___
Python tracker
<h
R. David Murray added the comment:
Hmm. Having posted that it occurs to me that it could be useful to have the
_remove_refcount function in test.support as remove_refcount instead.
--
___
Python tracker
<http://bugs.python.org/issue9
Changes by R. David Murray :
--
nosy: +belopolsky
___
Python tracker
<http://bugs.python.org/issue10654>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by R. David Murray :
--
nosy: +belopolsky
___
Python tracker
<http://bugs.python.org/issue10653>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
I'm still working on this, making sure the remaining options that aren't
currently tested have tests and work.
--
assignee: eric.araujo -> r.david.murray
___
Python tracker
<http://bugs.pytho
R. David Murray added the comment:
Oh, good, I'll use that then. I could have sworn I looked for that
functionality a couple weeks ago and couldn't find it.
--
___
Python tracker
<http://bugs.python.
R. David Murray added the comment:
The format support is written specifically so that it is extensible. You can
write your own string subclass that extends the formatting mini-language with
whatever features you find useful. There are too many variations on what might
be useful with
R. David Murray added the comment:
OK, here is what I hope is a comprehensive set of CLI tests, and fixes for the
bugs revealed thereby. Except for the new test added by Georg after the
original patch here was committed, all of the tests either pass using the old
compileall module or fail
R. David Murray added the comment:
for what it is worth, I am +1 on having completion and history file work by
default. The sqlite3 command line does this, for example. I think it is what
unix user expect nowadays, and I think it is reasonable.
Looking at my home directory, it would appear
R. David Murray added the comment:
This class was added by the fix for issue 1486663 in r53509. Adding Georg as
nosy since he committed it, but it seems like it would be worth fixing it in
case someone else uses the class in an additional test in the future.
--
nosy: +georg.brandl
Changes by R. David Murray :
--
versions: +Python 3.1, Python 3.2
___
Python tracker
<http://bugs.python.org/issue10668>
___
___
Python-bugs-list mailin
R. David Murray added the comment:
My guess is "it shouldn't", and "yes", but I've added the multiprocessing
maintainers as nosy and they can answer definitively.
--
nosy: +asksol, jnoller, r.david.murray
___
Python tr
Changes by R. David Murray :
--
nosy: +benjamin.peterson
___
Python tracker
<http://bugs.python.org/issue10674>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
I think this is the kind of thing where you are *much* better off writing a
specialized assert method that exactly fits your use case. There are too many
variations on this theme, IMO, for it to make sense as an stdlib method.
--
nosy
R. David Murray added the comment:
Committed the patch_flush_mmap patch to 3.1 in r87163 and 2.7 in r87164.
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue
R. David Murray added the comment:
What do you mean by "there is a test for this case in csv.py"? If I run
sniffer against "abcde\ndefgh\n" I get a delimiter of 'e'. If I run it against
'a\nb\n', I get the could not determine delimiter error.
Attach
R. David Murray added the comment:
Forgot to attach the patch.
--
Added file: http://bugs.python.org/file20006/csv_delimiter_tests.patch
___
Python tracker
<http://bugs.python.org/issue10
R. David Murray added the comment:
Upon reflection I think the risk of breaking apparently working programs is
higher than the benefit to be obtained from backporting this.
--
___
Python tracker
<http://bugs.python.org/issue1574
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:
Yeah, obviously wrong. I forgot to finish editing the comment.
I think a fallback of ',' makes more sense than ''. What would a delimiter of
nothing mean? I don't think the unquoted case can be changed for backward
compatibility
R. David Murray added the comment:
I like the suggestion of turning it into a warning, myself, but you are right
that at the least the error message should be improved.
--
resolution: invalid ->
stage: committed/rejected -> needs patch
status: closed -
R. David Murray added the comment:
mktime_tz is documented as turning the input into a *UTC* timestamp. That's
what your example shows it doing.
There is an open issue elsewhere in this tracker for providing a way to
round-trip RFC2822 timestamps.
--
nosy: +r.david.m
R. David Murray added the comment:
My guess is people don't read warnings when they are a common occurrence. A
working Python should not emit any warnings, and a properly working Python
program (post 2.6/3.1 (or whenever it was we decided to suppress deprecation
warnings by default)) s
Changes by R. David Murray :
--
nosy: +mark.dickinson
___
Python tracker
<http://bugs.python.org/issue10682>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by R. David Murray :
--
nosy: +brian.curtin, tarek, tim.golden
___
Python tracker
<http://bugs.python.org/issue10684>
___
___
Python-bugs-list mailin
R. David Murray added the comment:
The tests are failing on windows:
http://www.python.org/dev/buildbot/all/builders/x86%20XP-4%203.x/builds/3770/steps/test/logs/stdio
==
ERROR: test_mkdtemp_failure
R. David Murray added the comment:
There's also a typo in the issue number in your commit message (10888 instead
of 10188).
--
___
Python tracker
<http://bugs.python.org/is
Changes by R. David Murray :
--
priority: -> normal
___
Python tracker
<http://bugs.python.org/issue10367>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by R. David Murray :
--
priority: -> normal
___
Python tracker
<http://bugs.python.org/issue4391>
___
___
Python-bugs-list mailing list
Unsubscri
R. David Murray added the comment:
On balance I think this would be a backward incompatible change that has
insufficient benefit to be worth doing. People who have working code will be
depending on the existing defaults of the two methods, and changing this out
from under them would be
New submission from R. David Murray :
This is a followon to Issue 4661. The fix for that issue introduced a way to
parse messages containing 8bit bytes. When Generator is called on a model
containing 8 bit bytes, it converts it to 7bit clean. There is, however, a bug
in this conversion
R. David Murray added the comment:
I've opened a issue 10686 to address improving the RFC conformance by using
unknown-8bit encoded words for 8bit bytes in headers.
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: ope
R. David Murray added the comment:
The wording was clarified for 3.2 as part of the fix for issue 4661. This does
not help the 3.1 docs, so if someone wants to suggest a patch for the 3.1 docs
we can reopen the issue.
--
resolution: postponed -> fixed
stage: -> committed/re
R. David Murray added the comment:
Committed a simpler fix in r87196, backported to 3.1 in r87195, and 2.7 in
r87196.
--
resolution: -> fixed
stage: unit test needed -> committed/rejected
status: open -> closed
___
Python track
R. David Murray added the comment:
This is a duplicate of issue 2029.
--
nosy: +r.david.murray
resolution: -> duplicate
stage: -> committed/rejected
status: open -> closed
superseder: -> "python -m pydoc -g" fails
___
R. David Murray added the comment:
OK, I've studied this more, and it looks to me like the legacy address format
allows multiple atoms separated by white space in the local part of the
address. This means that the correct parse would be
('', 'merwok w...@rusty.com'
R. David Murray added the comment:
Updating patch because the assertTestRegexMatches name was updated.
--
Added file: http://bugs.python.org/file20029/compileall_cli_revisited.patch
___
Python tracker
<http://bugs.python.org/issue10
Changes by R. David Murray :
Removed file: http://bugs.python.org/file19989/compileall_cli_revisited.patch
___
Python tracker
<http://bugs.python.org/issue10453>
___
___
Changes by R. David Murray :
Removed file: http://bugs.python.org/file20029/compileall_cli_revisited.patch
___
Python tracker
<http://bugs.python.org/issue10453>
___
___
Changes by R. David Murray :
Added file: http://bugs.python.org/file20030/compileall_cli_revisited.patch
___
Python tracker
<http://bugs.python.org/issue10453>
___
___
R. David Murray added the comment:
I'm not sure why you would be seeing a test failure on OSX when we aren't
seeing it on other platforms, but the cause of the bug is known. It should be
fixed by the last patch attached to issue 10453. If you could test that patch
it would be
Changes by R. David Murray :
--
nosy: +cartman
___
Python tracker
<http://bugs.python.org/issue10453>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by R. David Murray :
Removed file: http://bugs.python.org/file20030/compileall_cli_revisited.patch
___
Python tracker
<http://bugs.python.org/issue10453>
___
___
Changes by R. David Murray :
Added file: http://bugs.python.org/file20031/compileall_cli_revisited.patch
___
Python tracker
<http://bugs.python.org/issue10453>
___
___
R. David Murray added the comment:
Where does the non-telnet part of your trace come from? How did you produce
it? Does this error still occur using 2.7? (Python 2.6 is in security fix
only mode at this point.)
--
nosy: +eric.smith, r.david.murray
stage: -> unit test needed
t
R. David Murray added the comment:
Ned, did you mean issue 9763?
--
nosy: +r.david.murray
status: pending -> open
___
Python tracker
<http://bugs.python.org/issu
Changes by R. David Murray :
--
status: open -> pending
___
Python tracker
<http://bugs.python.org/issue10690>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by R. David Murray :
--
resolution: -> invalid
stage: unit test needed -> committed/rejected
___
Python tracker
<http://bugs.python.org/i
R. David Murray added the comment:
It looks to me like the critical parts of this have been done, so I'm
downgrading the priority.
--
nosy: +r.david.murray
priority: critical -> high
versions: +Python 3.2 -Python 3.1
___
Python tracke
R. David Murray added the comment:
Drat, missed this one when I was reviewing my issues for feature requests
because I didn't change the type :(
--
versions: +Python 3.3 -Python 3.2
___
Python tracker
<http://bugs.python.org/i
Changes by R. David Murray :
--
nosy: -BreamoreBoy
___
Python tracker
<http://bugs.python.org/issue6302>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by R. David Murray :
--
title: email.header.decode_header data types are inconsistent and incorrectly
documented -> Add decode_header_as_string method to email.utils
type: behavior -> feature request
___
Python tracker
R. David Murray added the comment:
Bump. This bug has priority high and it sounds like the patch is ready for
commit.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue9
Changes by R. David Murray :
--
versions: -Python 2.5, Python 2.6
___
Python tracker
<http://bugs.python.org/issue10340>
___
___
Python-bugs-list mailin
R. David Murray added the comment:
"Might even make sense" to backport doesn't sound like a definite, so I've
removed 2.6 and 2.5 from versions. You'll want to ask the release managers for
a decision if you want to backport.
---
R. David Murray added the comment:
Take another look at the documentation.
http://docs.python.org/dev/library/urllib.parse.html
>>> import urllib.parse
>>> o = urllib.parse.urlsplit("http://foo.bar.com:80/blarg?a=1&b=2";)
>>> o
SplitResult(scheme=
Changes by R. David Murray :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue10696>
___
___
Python-bugs-list mailing list
Unsubscri
R. David Murray added the comment:
The repr gives the primary components defined by the URL. The subfields are
provided as attributes of the result. This is documented in the example at the
top of the chapter, but it is not, IMO, well documented in the rest of the
chapter.
I'm not
Changes by R. David Murray :
--
nosy: +jackdied
___
Python tracker
<http://bugs.python.org/issue10695>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Thanks. Fixed in r87216.
--
nosy: +r.david.murray
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
type: -> behavior
___
Python tracker
<http://bugs.python
R. David Murray added the comment:
Committed the default-to-utf8 fix in r87217, splitting up the tests as
suggested by Barry. Backported to 3.1 in r87218. Updated the documentation
for 2.7 in r87219.
--
resolution: -> fixed
stage: patch review -> committed/rejected
status
R. David Murray added the comment:
Thanks. Fixed in py3k in r87221. I'll backport it when I backport my other
doc updates.
FYI, 'trunk' is no longer a live branch. Development trunk is now py3k. 2.6
only gets security fixes.
--
nosy: +r.david.murray
resolution:
Changes by R. David Murray :
--
title: [patch] fix incorrect help doc with time.tzset -> fix incorrect help doc
with time.tzset
___
Python tracker
<http://bugs.python.org/issu
Changes by R. David Murray :
--
stage: -> unit test needed
type: -> behavior
___
Python tracker
<http://bugs.python.org/issue2226>
___
___
Python-bugs-
R. David Murray added the comment:
Committed in r87225, r87226, and r87227. Thanks, Daniel.
--
nosy: +r.david.murray
resolution: -> fixed
stage: needs patch -> committed/rejected
status: open -> closed
___
Python tracker
<http://bug
Changes by R. David Murray :
--
stage: -> unit test needed
type: -> behavior
___
Python tracker
<http://bugs.python.org/issue9775>
___
___
Python-bugs-
Changes by R. David Murray :
--
stage: -> needs patch
type: -> behavior
versions: +Python 3.2
___
Python tracker
<http://bugs.python.org/issue6696>
___
___
R. David Murray added the comment:
The randomly failing tests seem to have been the high priority issue. The
remaining, eponymous issue seems to be of rather lower priority, so I'm setting
it to normal. Although Tim wanted a separate issue for the pickling problem, I
think there'
Changes by R. David Murray :
--
type: -> behavior
versions: +Python 3.1, Python 3.2 -Python 2.6
___
Python tracker
<http://bugs.python.org/issue4180>
___
_
Changes by R. David Murray :
--
nosy: +eric.araujo
stage: -> unit test needed
type: -> behavior
___
Python tracker
<http://bugs.python.org/issue6377>
___
__
Changes by R. David Murray :
--
stage: -> unit test needed
type: -> behavior
versions: -Python 2.6
___
Python tracker
<http://bugs.python.org/
Changes by R. David Murray :
--
stage: -> needs patch
type: -> behavior
___
Python tracker
<http://bugs.python.org/issue10541>
___
___
Python-bugs-list
Changes by R. David Murray :
--
title: [PATCH]add pass_fds paramter to subprocess.Popen() -> add pass_fds
paramter to subprocess.Popen()
type: -> feature request
___
Python tracker
<http://bugs.python.org/
R. David Murray added the comment:
This feature request should be submitted to the Sphinx tracker, since the docs
search facility is provided by Sphinx.
--
nosy: +r.david.murray
resolution: -> invalid
stage: -> committed/rejected
status: open -> closed
type: -> fea
R. David Murray added the comment:
Well, in that case your telnet session doesn't tell us all that much, since you
are using IMAP4_SSL in the Python but regular non-SSL in the telnet session.
Are you sure it is even the same server running on the SSL
R. David Murray added the comment:
By the way, an SSL login runs just fine for me against my Courier-IMAP server.
Does regular IMAP work for you?
--
___
Python tracker
<http://bugs.python.org/issue10
Changes by R. David Murray :
--
stage: -> patch review
type: -> feature request
___
Python tracker
<http://bugs.python.org/issue8863>
___
___
Python-bugs-
Changes by R. David Murray :
--
versions: +Python 3.3 -Python 3.2
___
Python tracker
<http://bugs.python.org/issue8863>
___
___
Python-bugs-list mailing list
Unsub
R. David Murray added the comment:
What's the status of this? It sounds like it something that should be taken
care of before the 3.2 release, but I know there has been other activity in
this area and I haven't looked closely enough to understand the issues involved.
-
Changes by R. David Murray :
--
type: -> feature request
___
Python tracker
<http://bugs.python.org/issue10530>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by R. David Murray :
--
type: -> feature request
versions: +Python 3.3 -Python 3.2
___
Python tracker
<http://bugs.python.org/issue6731>
___
___
Py
R. David Murray added the comment:
Yes, for backward compatibility reasons it is better to make the change that
fixes the thing that doesn't work and leave the rest alone. Probably the
change wouldn't break *much* existing user code, but why break anything when
there doesn't
R. David Murray added the comment:
Starttls support was only added in Python 3.2. Apparently your server is set
to disallow non-SSL connections.
Have you confirmed that the same server is listening on port 993 as is
listening on port 143? The debug info from imaplib makes it look like
3401 - 3500 of 12938 matches
Mail list logo
