R. David Murray added the comment:
Yes, since the package will save the original text anyway, I think just
clamping to 59 is best.
Hmm. Maybe instead I could put in an assert that says "please report this
incident to bugs.python.org so we can argue that datetime should get support
for
R. David Murray added the comment:
Well, it turns out that this sporadic failure is not a test bug, but a real bug
in the mailbox module that the test is revealing.
This issue is the same one that motivated the changes in issue 6896. Those
changes, however, merely reduced the problem, but
Changes by R. David Murray :
Removed file: http://bugs.python.org/file21904/mailbox_mtime.patch
___
Python tracker
<http://bugs.python.org/issue11999>
___
___
Python-bug
Changes by R. David Murray :
Added file: http://bugs.python.org/file21905/mailbox_mtime.patch
___
Python tracker
<http://bugs.python.org/issue11999>
___
___
Python-bug
R. David Murray added the comment:
Isn't this a bit out of scope for the mailbox module, though? Mailbox is
getting called at irregular intervals, and a clock monitor really wants to be a
polling daemon of some sort, I think. In which case a complete application
system that use
R. David Murray added the comment:
Oh, and to be clear: the problem wasn't that the one second interval was too
short, the problem was that the times stamps of the files were being compared
to the wrong check value (the system clock instead of their previous state).
The extra one
R. David Murray added the comment:
I am open to the argument that we should make it two seconds and a bit to
support FAT, but how many people are going to use maildir on FAT?
--
___
Python tracker
<http://bugs.python.org/issue11
R. David Murray added the comment:
All right, let's make it two seconds and a bit, then.
Why do you think a tenth of second is too small? A clock with a skew of half
that much would be badly broken.
--
___
Python tracker
<http://bugs.py
alejandro david weil added the comment:
Yes it is. I copied both versions but forgot to specify the second is in 2.7.
This is read in the current (2.7) documentation:
# from: http://docs.python.org/library/functions.html?highlight=xrange#xrange
islice(count(start, step), (stop-start+step-1
R. David Murray added the comment:
Hmm. That error message is more than a bit misleading. What you need to do is
add a flush method to your FlushFile class. Something changed between 3.1 and
3.2 that causes that message to be generated instead of suppressed. Not sure
what it was. The
R. David Murray added the comment:
Now we see if the buildbots agree with me that this is fixed.
--
resolution: -> fixed
stage: -> committed/rejected
status: open -> pending
title: sporadic failure in test_mailbox on FreeBSD -> sporadic failure in
test_mailbox
type:
R. David Murray added the comment:
In 3.x, yes (the nonlocal keyword). Not in 2.7, though.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue12
Changes by R. David Murray :
--
nosy: +lukasz.langa
___
Python tracker
<http://bugs.python.org/issue12036>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from R. David Murray :
It doesn't matter which order test_os and test_ctypes run in, but if they
precede test_wait3 test_wait3 will fail. When the test is immediately re-run
it passes.
The reason ought to be interesting once we figure it out :)
Tested on linux. Do
R. David Murray added the comment:
Raymond: I haven't read the examples in detail so I don't have an opinion on
the appropriateness of the text, but I'm curious: while what you say certainly
applies to the Language Reference, does it also apply to the Tutorial?
R. David Murray added the comment:
Raymond: yes, thanks for the clear guidance. Perhaps it could be added to
Documenting Python, perhaps in the Style Guide chapter?
--
___
Python tracker
<http://bugs.python.org/issue11
R. David Murray added the comment:
Confirmed working on my box as well, and on my buildbot (where I first noticed
it).
--
___
Python tracker
<http://bugs.python.org/issue12
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue8824>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from R. David Murray :
See
http://www.python.org/dev/buildbot/all/builders/x86%20Gentoo%203.2/builds/34/steps/test/logs/stdio
Antoine says that connect_ex should be returning an error, not None, in that
situation.
--
components: Tests
keywords: buildbot
messages
R. David Murray added the comment:
My usual pattern (adopted from examples in the stdlib tests) is this:
TestSomethingBase:
tests
PyTestSomething(TestSomethingBase, TestCase):
stuff
CTestSomething(TestSomethingBase, TestCase):
stuff
Is there a reason that won't work in
Changes by R. David Murray :
--
resolution: -> accepted
stage: patch review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
AFAIK build.sh is only as out of date as the svn/hg switchover. I believe this
particular issue was dealt with, but I haven't checked.
It runs the refcount tests for 2.7 (Antoine has a separate script that runs
them fo
R. David Murray added the comment:
Antoine removed that check as part of the -j support, if I recall correctly.
The check for unexpected output was part of the support for the transition
between the old pre-unittest test suite and the unittest based test suite, and
does seem like it is
R. David Murray added the comment:
Right, that's why I said "if it is a bug" :)
FreeBSD has the same behavior, so I'd actually prefer that Apple not "fix"
this. It would be nice if FreeBSD did and Apple adopted it, though, since only
dropping the % is t
Changes by R. David Murray :
--
keywords: +buildbot
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue12096>
___
___
Python-bugs-list mailin
Changes by R. David Murray :
--
assignee: -> r.david.murray
stage: test needed -> patch review
___
Python tracker
<http://bugs.python.org/issue12009>
___
__
R. David Murray added the comment:
With these new additions, the test input is getting unwieldy. If you have the
time, I'd like to see the unit tests refactored to be more unit-testy. That
is, instead of a single test netrc file, have multiple inputs, one for each
thing being tested
R. David Murray added the comment:
Brett's been very busy with real life. Maybe someone else can commit this.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
Haypo, since you've created a new directory there are makefile (and PC build
file, I think) updates that will need to be made. (This should be documented
in the dev guide if it isn't already.)
--
nosy: +r.da
R. David Murray added the comment:
This is a long-standing design choice in the email package. If you want to
advocate for changing it, please join the email-sig mailing list (see
mail.python.org). We are in the process of developing a new version, which
will at least reject things like
R. David Murray added the comment:
See also #9921.
--
nosy: +r.david.murray
resolution: rejected -> duplicate
superseder: -> os.path.join('x','') behavior
___
Python tracker
<http
R. David Murray added the comment:
IMO 3.3 is definitely too soon. 3.4 may be too, depending on how many people
are stuck on legacy systems using 2.7.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue12
R. David Murray added the comment:
In fact, not fixing it might send a small message as to what we think about
that particular system default :)
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue12
R. David Murray added the comment:
I agree with Amaury. IMO the IOError is the correct error, since it is
bubbling up unexpectedly (from zipfile's viewpoint) from a lower layer and is
not an error specific to the zip protocol implementation. (CF the discussion
surrounding PEP
R. David Murray added the comment:
2.7 is post-3.1. This works as you expect in 3.2. This is, it is a new
feature in both 2.7 and 3.2.
(NB: this is why I wanted 3.2 to come out close to 2.7, but fortunately this is
the first report like this I think we've gotten.)
--
R. David Murray added the comment:
"first part" by itself sounds like there can only be two parts. How about
'inserts a separator between each pair of...'
Also, what does 'absolute' mean on Windows? Does it include the drive? If so,
the second sentence
R. David Murray added the comment:
The argument against adding this to the pdb docs is that if you pull in that
statement from cmd, you really ought to pull in the full description of the
__init__ arguments. And whether you do that or just pull in that single
statement, you are duplicating
R. David Murray added the comment:
I doubt that close is ever called when removehandler is called. That doesn't
strike me as sensible semantics. I suspect that what is happening is that in
2.6 calling removehandler removed all references to the handler, and python's
garbage
R. David Murray added the comment:
Thanks for diagnosis and the test patch, and welcome to the bug weekend.
Some comments:
test.support has a symbol, TESTFN, which is guaranteed to be unique for the
test run and located in an appropriate writeable location. Many tests use it
to create a
R. David Murray added the comment:
There are currently no tests in argparse that test the content of error
messages, which is fairly standard for stdlib tests since the error messages
aren't considered part of the API (only the nature of the exception is). So
there's really no exi
R. David Murray added the comment:
Just as an FYI, a similar situation exists on Solaris. I had to fix one of the
Python test suite tests once because it was naively trying to rmtree the CWD.
--
nosy: +r.david.murray
___
Python tracker
<h
R. David Murray added the comment:
unsupported locale setting is a message that comes from the C runtime, IIUC.
Does it work on windows with 2.6?
--
nosy: +lemburg, r.david.murray
___
Python tracker
<http://bugs.python.org/issue10
Changes by R. David Murray :
--
nosy: +pitrou
___
Python tracker
<http://bugs.python.org/issue10467>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by R. David Murray :
--
keywords: -easy
___
Python tracker
<http://bugs.python.org/issue5871>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
I've committed this (with the whitespace fix) in r86577. I've made myself a
note to backport it when the maint branches unfreeze.
--
assignee: nnorwitz ->
nosy: +r.david.murray
resolution: -> fixed
stage: patch review -> commit
Changes by R. David Murray :
--
versions: -Python 2.6
___
Python tracker
<http://bugs.python.org/issue1574217>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by R. David Murray :
--
keywords: -patch
stage: unit test needed -> patch review
versions: -Python 2.7
___
Python tracker
<http://bugs.python.org/iss
R. David Murray added the comment:
On the other hand, the test case in test_compileall says "test some aspects of
compileall's CLI". Since the patch completely changes the logic of CLI
parsing, having tests that cover as much as practical of the CLI would greatly
increase
R. David Murray added the comment:
Note that Benjamin's commit only addresses the posix side. Amaury, do you want
to fix the windows side?
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/i
R. David Murray added the comment:
It looks good, but as mentioned on IRC it would be nice to have a unit test
that confirmed that the headers were being correctly buffered.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.
Changes by R. David Murray :
--
stage: needs patch -> patch review
___
Python tracker
<http://bugs.python.org/issue9721>
___
___
Python-bugs-list mai
Changes by R. David Murray :
--
versions: +Python 2.7, Python 3.2
___
Python tracker
<http://bugs.python.org/issue9721>
___
___
Python-bugs-list mailing list
Unsub
R. David Murray added the comment:
Issue 1508475 has a patch, though it still needs updated.
--
resolution: -> duplicate
stage: unit test needed -> committed/rejected
status: open -> closed
superseder: -> transparent gzip compressio
Changes by R. David Murray :
--
assignee: eric.araujo -> r.david.murray
stage: needs patch -> commit review
___
Python tracker
<http://bugs.python.org/i
R. David Murray added the comment:
Patch committed with minor formatting changes and one fixed test (test_force)
in r86611. Thanks, Michele!
--
resolution: -> accepted
stage: commit review -> committed/rejected
status: open -> closed
_
R. David Murray added the comment:
Thanks for the patch and test. They look good.
A doc update is also needed, since the docs are currently written in such a way
that buffering the header lines makes the documentation no longer true.
Also, send_response_only writes directly to the output
Changes by R. David Murray :
--
stage: -> patch review
___
Python tracker
<http://bugs.python.org/issue3709>
___
___
Python-bugs-list mailing list
Unsubscri
R. David Murray added the comment:
TempdirManager is new, which is why I forgot about it. It works with the
buildbots because it is a context manager, so if things go badly the cleanup
code is still going to run and delete the cruft. Since the distutils tests are
unlikely to hang (which is
R. David Murray added the comment:
For the record, I don't find the behavior of __iter__ on a binary file at all
confusing. It's the same behavior I see if I open the file in, say, vi. So it
is in fact the behavior I expect, and I would be surprised if it didn't work.
Whethe
R. David Murray added the comment:
Senthil, I didn't clearly express my concern about send_response_only. It
doesn't look to me like, with buffering in place, that it *should* write
directly, it looks to me like it should write to the buffer. Consider
specifically the
R. David Murray added the comment:
This is fixed by r86642. The remaining failing tests were pointing to bugs in
the implementation of the linesep argument to generator.flatten. I had to add
an additional test to catch all the related bugs, though.
The tests now run the inversion tests
R. David Murray added the comment:
In investigating issue 10466 I find that getlocale on windows returns the value
that windows accepts for me. For example on my US windows system, getlocale
returns ('English_United States', '1252'), and that appears to work when passe
R. David Murray added the comment:
See also issue 1699853.
The problem here is that resetlocale calls getdefaultlocale, and
getdefaultlocale returns something that setlocale cannot consume on Windows.
For example, on my US windows system, getlocale returns ('English_United
States&#x
R. David Murray added the comment:
It is unfunny that your program fails on Windows.
Yes it is the same bug, since calendar calls getdefaultlocale.
Issue 1080864 makes very interesting reading in this context. Clearly Martin
is right, yet the OP seems to find the current behavior of
New submission from R. David Murray :
See issue 10466 for background, but in short LocaleHTMLCalendar uses
getdefaultlocale if no locale is specified, and on windows this results in a
locale that setlocale will not accept. The fix is presumably to use
setlocale(LC_DATE, '')
Changes by R. David Murray :
--
nosy: +skoczian
___
Python tracker
<http://bugs.python.org/issue10498>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
I've opened issue 10498 for the calendar bug.
--
___
Python tracker
<http://bugs.python.org/issue10466>
___
___
Pytho
R. David Murray added the comment:
Agreed on the closing. The pre-diff processing function would be a great
addition. For the record, I am currently satisfying my use case by doing this:
self.assertEqual(bstr1.split(b'\n'), bstr2.split(b'\n'))
which produces
R. David Murray added the comment:
I had a report from a user on IRC during the bug weekend that they could not
reproduce the failure on windows. So it may be dependent on the windows
version. That doesn't answer your question of why it hasn't come up before,
though, since my
R. David Murray added the comment:
These are wrappers around the posix functions. As such the unix man pages are
a better authority than the Python docs :) Still, we could certainly improve
the docs.
The getlogin error is probably a miscopy from the man page: the man page on my
system
R. David Murray added the comment:
This is working as designed. Whether or not the design is correct has been
debated in the past. If you want to re-debate it the appropriate place is
probably python-ideas.
--
nosy: +bethard, r.david.murray
resolution: -> invalid
status: o
R. David Murray added the comment:
This is a duplicate if issue 9291.
--
nosy: +r.david.murray
stage: -> committed/rejected
status: open -> closed
superseder: -> mimetypes initialization fails on Windows because of non-Latin
characters in
Changes by R. David Murray :
--
nosy: +aclover
___
Python tracker
<http://bugs.python.org/issue9291>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Please don't change the type, this issue is about the feature request of adding
this regex engine to the stdlib.
I'm sure Matthew will get back to you about your question.
--
type: behavior -> fe
R. David Murray added the comment:
For the email package I would be in favor of moving the tests to Lib/test.
I've always found it a bit inconvenient that they are in Lib/email. After
hearing of Michael's intent with unittest, and given the evolution of email5
into email5.1,
R. David Murray added the comment:
Yes, a cheeseshop package is definitely part of the plan, I didn't mean to
imply otherwise. It won't be hard to automate the packaging, and indeed I'll
wind up doing that anyway even if the tests stay inside Lib/email.
I will say that th
Changes by R. David Murray :
--
assignee: -> r.david.murray
___
Python tracker
<http://bugs.python.org/issue1079>
___
___
Python-bugs-list mailing list
Un
R. David Murray added the comment:
Note that none of your examples are valid encoded words, so given that email
currently does strict parsing, the fact that it is not attempting to decode
those words is technically correct.
However, I agree that it would be better for it to do a "
R. David Murray added the comment:
Kovid: so essentially what you are saying is that the windows platform is
broken with respect to MIME types and with respect to its security model. Why
am I not surprised? :)
You would have the same problem if software installation altered the
/etc
R. David Murray added the comment:
I would expect that it would not be people new to mimetypes that would have the
issues, but people like you for whom the behavior on Windows has changed. And
this is indeed a concern.
The people involved in making the windows mimetypes enhancement are nosy
R. David Murray added the comment:
Boštjan, please see issue 10466 for further information about your question on
fr_FR vs French. Windows, as usual, does not follow the standards.
--
___
Python tracker
<http://bugs.python.org/issue10
R. David Murray added the comment:
I think Boštjan is correct that that sentence is not parallel to the others.
If I understand correctly, at that point the installation is complete, and it
is the final 'exit or back' dialog. So I think the title should be "Complet
R. David Murray added the comment:
Committed to py3k in r86925, 3.1 in r86926, and 2.7 in r86927.
Thanks for the patch, Xuanji.
--
nosy: +r.david.murray
resolution: -> fixed
stage: commit review -> committed/rejected
status: open -&g
Changes by R. David Murray :
--
nosy: +haypo
___
Python tracker
<http://bugs.python.org/issue10603>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Much work has been done on non-ASCII paths in 3.2. Can you test this with the
3.2 alpha and let us know the results?
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue10
R. David Murray added the comment:
Are you sure testA1 is correct? It seems to me that in that case the sniffer
can indeed not determine the delimiter, but I don't really understand the
guessing algorithm. The existing behavior on unquoted strings is...interesting
:)
Also if yo
Changes by R. David Murray :
--
resolution: -> out of date
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
Committed to py3k in r86936 with minor fixups.
--
resolution: -> accepted
stage: patch review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
I've taken another look at this, and the email module is pretty consistent
about just passing through data if it can't interpret it according to
standards. I think it would lead to a cluttered API if we add support for
being strict and rais
R. David Murray added the comment:
Do you have in implementation in mind? I'm not clear how this would work.
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
Closing this in favor of 1486713, which has a patch and covers additional
issues.
--
nosy: -BreamoreBoy
resolution: -> duplicate
stage: unit test needed -> committed/rejected
status: open -> closed
superseder: -> HTMLParser : A a
R. David Murray added the comment:
I have committed a version of this patch, without the warnings, using the
keyword 'strict=True' as the default, and with a couple added heuristics from
other similar issues, in r86952.
kxroberto, if you want to supply your full name, I'll
R. David Murray added the comment:
The new strict=False mode from #1486713 handles this case.
--
nosy: +r.david.murray
resolution: -> accepted
stage: -> committed/rejected
status: open -> closed
superseder: -> HTMLParser : A auto-tolerant
R. David Murray added the comment:
Included this in the 'strict=False' mode in the issue 1486713 patch.
--
nosy: +r.david.murray -BreamoreBoy
resolution: -> accepted
stage: patch review -> committed/rejected
status: open -> closed
superseder: -> HTMLParser : A
Changes by R. David Murray :
--
title: HTMLParser fix to accept mailformed tag attributes -> HTMLParser fix to
accept malformed tag attributes
___
Python tracker
<http://bugs.python.org/issue1
R. David Murray added the comment:
Ah, I did not realize that getstatusoutput was implemented using os.popen. I
thought it already used Popen. Now, in python3, os.popen is in turn
implemented using subprocess.Popen, so removing that level of indirection seems
sensible.
The question that
R. David Murray added the comment:
A note for the curious: I changed the keyword name from 'tolerant' to 'strict'
because the stdlib has other examples of 'strict' as a keyword, but the word
'tolerant' appears nowhere in the documentation and certainly
R. David Murray added the comment:
I've decided that writing (some) errors to stdout instead of stderr is really a
bug, not a feature request, and have backported this fix to 3.1 in r87053 and
to 2.7 in r87055.
The one possible reason not to do this is that it is conceivable that it
R. David Murray added the comment:
Eric, I'm assuming you just forgot to close this. On the other hand, if you
wanted a +1 from another dev, you've got it :) Besides the considerations you
mentioned, changing this would be a significant backward incompatibility, and
is theref
R. David Murray added the comment:
So, Martin, are you then arguing that this should in fact be considered a bug
in ZipFile? The documentation for the constructor says "Open a ZIP file, where
file can be either a path to a file (a string) or a file-like object." Reading
th
3301 - 3400 of 12936 matches
Mail list logo
