R. David Murray added the comment:
I think it is a good idea, but someone has to set one up.
--
___
Python tracker
<http://bugs.python.org/issue7449>
___
___
R. David Murray added the comment:
Georg can correct me if I'm wrong, but I believe we generally only rewrap lines
when we change the text for some other reason. My observation was that Georg
re-wraps doc text to 79 chars, so that's what I've been doing. PEP 8 really
only ap
R. David Murray added the comment:
No, I meant demense (I even looked up the spelling). The word is related to
domain, but has a somewhat more precise shading of meaning :)
A lord's chief manor place, with that part of the lands
belonging thereto which has not been granted o
R. David Murray added the comment:
Your patch looks good, thank you.
I just realized that Barry isn't nosy on this issue. I've checked, and the
code in question dates back to email version 1.0...code of that long standing
that exists specifically to implement the behavior we
R. David Murray added the comment:
I think that's because encodestring tacks a 'courtesy newline' on to the end of
the output it returns. textwrap.fill does't, and I'm guessing that's the code
path that your installation is taking.
--
components: +Libr
Changes by R. David Murray :
--
versions: +Python 2.7, Python 3.1, Python 3.2
___
Python tracker
<http://bugs.python.org/issue8086>
___
___
Python-bugs-list mailin
Changes by R. David Murray :
--
nosy: +janssen
___
Python tracker
<http://bugs.python.org/issue8086>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
OK, patch (with comment tweaks to refer to this issue), and email minor version
bump, applied to trunk in r78778. It turns out that bdecode was already
deleted in email 5 in py3k. I did port the test in r78780.
Thanks Joaquin Cuenca Abela, and you now
R. David Murray added the comment:
On the other hand, having a facility somewhere in the stdlib to pass a Message
object to SMTP sendmail would be handy. I've made a note of this in my working
notes for email6 to see if there's something we want to do about it.
-
R. David Murray added the comment:
I meant issue 8096.
--
nosy: +mtschopp
___
Python tracker
<http://bugs.python.org/issue6656>
___
___
Python-bugs-list mailin
Changes by R. David Murray :
--
___
Python tracker
<http://bugs.python.org/issue6656>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/m
R. David Murray added the comment:
Eric, the patch for this issue contains a fix for issue 8094. The only reason
I haven't applied it is the fear of breaking existing correct behavior because
there aren't enough tests. Maybe you can see an easy way to reuse the % test
suit
R. David Murray added the comment:
Are you running this on windows?
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue8094>
___
___
Pytho
R. David Murray added the comment:
See issue 6656. This bug isn't a quite a duplicate of that bug, but I did
discover (and fix) the bug this one reports in the process of creating a patch
for that one, so I'm closing this one as a duplicate anyway.
--
nosy: +r.da
Changes by R. David Murray :
--
nosy: +eric.smith
___
Python tracker
<http://bugs.python.org/issue6656>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Unless I'm missing something, this appears to be a bug in your code. You
redefine import_hook in your subclass, but you don't give it a level parameter.
--
components: +Library (Lib) -Extension Modules
nosy: +r.david.murray
priority:
Changes by R. David Murray :
--
___
Python tracker
<http://bugs.python.org/issue6656>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/m
R. David Murray added the comment:
Eric, the patch for this issue contains a fix for issue 8096. The only reason
I haven't applied it is the fear of breaking existing correct behavior because
there aren't enough tests. Maybe you can see an easy way to reuse the % test
suit
Changes by R. David Murray :
--
components: +Documentation -Library (Lib)
priority: -> normal
stage: -> needs patch
type: crash -> behavior
versions: +Python 2.6, Python 2.7, Python 3.2
___
Python tracker
<http://bugs.python.o
Changes by R. David Murray :
--
keywords: +easy
nosy: +jnoller
priority: -> normal
stage: -> test needed
___
Python tracker
<http://bugs.python.org/
Changes by R. David Murray :
--
priority: -> normal
resolution: -> invalid
stage: -> committed/rejected
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
Probably it should use platform.system() == 'Windows' instead.
--
keywords: +easy
nosy: +dino.viehland, michael.foord, r.david.murray
___
Python tracker
<http://bugs.python.
Changes by R. David Murray :
--
nosy: +vinay.sajip
___
Python tracker
<http://bugs.python.org/issue8117>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
I suspect that what Antoine is referring to is the fact that Python 3.1 has
this behavior. Whether or not it is explicitly documented is a secondary issue.
We're having a similar issue in the unittest package, where there's a new
R. David Murray added the comment:
A patch with tests would be an excellent thing to have.
--
nosy: +r.david.murray
priority: -> normal
type: crash -> behavior
___
Python tracker
<http://bugs.python.org/
R. David Murray added the comment:
You may well be correct. But just because no one reported a bug does not mean
that no one is using the API. The person using it may find it perfectly
logical (and may be writing py3 only code, not porting py2 code).
However, regardless of whether we
R. David Murray added the comment:
Well, Benjamin pointed out to me that it would be a bad thing if array.tostring
produced a string. True, the method is named wrong, but it is less broken than
returning a string. I suspect that that is the same argument Fredrik is
making: that returning
R. David Murray added the comment:
Per the RFC, this is the correct behavior. An encoded word *must* begin and
end either at the field boundary or with whitespace. So ...?=Arobase, with no
whitespace between the = and Arobase, makes your first example into an invalid
encoded word, and thus
R. David Murray added the comment:
If I understand correctly, the problem with doing an import in a function is
that there is an import lock which can cause various problem depending on how
an application imports various things. I've added Brett to the nosy list to
see if he
R. David Murray added the comment:
This is a duplicate of issue 1729305.
--
nosy: +r.david.murray
priority: -> normal
resolution: -> duplicate
stage: -> committed/rejected
status: open -> closed
superseder: -> test_doctest fails when run
R. David Murray added the comment:
Would you care to submit a patch? The docs are in the svn repository in the
'Doc' subdirectory. See http://www.python.org/dev for how to get a checkout
and create a patch.
That said, note that 2.7/3.2 will have argparse, which is pretty much a
Changes by R. David Murray :
--
priority: -> normal
stage: -> test needed
type: crash -> behavior
___
Python tracker
<http://bugs.python.org/issue8160>
___
___
R. David Murray added the comment:
It does not crash on Gentoo, either:
rdmur...@maestro:~>uname -a
Linux maestro 2.6.31-gentoo-r3 #1 SMP PREEMPT Thu Oct 22 20:13:19 EDT 2009 i686
Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz GenuineIntel GNU/Linux
rdmur...@maestro:~/python/release26-maint>./
R. David Murray added the comment:
I don't think this patch satisfies Raymond's request. It is explicitly
checking for a __missing__ attribute, but Raymond was talking about a more
general facility whereby you can pass in an arbitrary object that implements
the mapping interface.
R. David Murray added the comment:
I agree that this should be fixed, since we presumably want to be "strictly
conforming" to the posix standards, but it looks like this is a regression in
either linux or glibc. From the standard's rational section:
Early proposals required
Changes by R. David Murray :
--
status: closed -> open
___
Python tracker
<http://bugs.python.org/issue2698>
___
___
Python-bugs-list mailing list
Unsubscri
R. David Murray added the comment:
I think it is actually pretty straightforward to write a *unit* test for this.
We just need to check that the logic works correctly given the expected
presence or absence of the environment variables. That doesn't test whether or
not the right
R. David Murray added the comment:
I believe that backporting this change to 2.6 is inappropriate. It will more
than likely cause perfectly correct code to stop working, and that is not
something we like to do in a maintenance release.
I believe that the bug on the debian/ubuntu side is
R. David Murray added the comment:
I cannot reproduce this with python 2.6.4 or trunk on linux.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue8
Changes by R. David Murray :
--
stage: -> test needed
versions: +Python 2.7, Python 3.1, Python 3.2 -Python 3.0
___
Python tracker
<http://bugs.python.org/iss
R. David Murray added the comment:
Well, actually os.popen in Python3 is implemented by calling subprocess.Popen.
So, Bob, how does it fail?
--
nosy: +r.david.murray
priority: -> normal
stage: -> test needed
___
Python tracker
R. David Murray added the comment:
A short snipped of example code that works in python2 and fails in python3
would be helpful in deciding whether or not this is a bug that needs fixing in
python3. Something that doesn't involve gnuplot, just python i
R. David Murray added the comment:
Victor, since this is a real,fixable bug but nobody has stepped forward with a
patch, I think it is better make its status 'languishing' with the reason 'no
one has stepped forward with a patch'. This kind of thing is exactly what we
in
R. David Murray added the comment:
Patches applied to trunk in r79294, py3k in r79298. Should this be backported?
--
keywords: -needs review
stage: patch review -> commit review
___
Python tracker
<http://bugs.python.org/iss
R. David Murray added the comment:
On linux: on Py3 (trunk and 3.1) I get the recursion depth exceeded message,
but on py2 trunk I get the segfault if I use 10 for the range. So somebody
fixed this crasher in py3, somehow.
--
nosy: +r.david.murray
resolution: wont fix ->
st
Changes by R. David Murray :
--
resolution: accepted -> fixed
stage: commit review -> committed/rejected
status: open -> closed
versions: -Python 2.6, Python 3.1
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
Senthil documented epilog in issue 8209.
--
___
Python tracker
<http://bugs.python.org/issue8158>
___
___
Python-bugs-list m
R. David Murray added the comment:
See also issue 8158.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue8209>
___
___
Python-bugs-list m
R. David Murray added the comment:
Note that it works with shell=True. Which is what you would expect if it works
in the shell. Without shell=True, the program name is being passed to
CreateProcess directly. Popen("foo") results in the same cannot find file error
for me if t
R. David Murray added the comment:
In order to do that someone will need to confirm that this affects all versions
of windows, and whether or not it is a bug in windows or the expected behavior
of CreateProcess.
--
___
Python tracker
<h
R. David Murray added the comment:
A recipe for reproducing the problem would be the most useful thing. I suspect
the windows error report is pretty much useless in this context.
--
nosy: +r.david.murray
priority: -> normal
stage: -> test
R. David Murray added the comment:
I can't reproduce this on 2.6 maint on Linux 32 bit (Gentoo).
Did you try doing a make distclean before redoing the configure/make?
--
nosy: +benjamin.peterson, r.david.murray
priority: -> high
___
Python
R. David Murray added the comment:
Crash is for interpreter segfaults, changing to type 'behavior'. Setting stage
to 'test needed' because if this is a valid bug the test will need to be turned
into a unit test.
--
nosy: +jnoller, r.david.murray
priority: ->
Changes by R. David Murray :
--
components: +Extension Modules -Library (Lib)
nosy: +giampaolo.rodola
___
Python tracker
<http://bugs.python.org/issue8
Changes by R. David Murray :
--
priority: -> normal
stage: -> test needed
type: -> behavior
___
Python tracker
<http://bugs.python.org/issue8240>
___
R. David Murray added the comment:
"test needed" is in reference to your assertion that you weren't sure your test
would fail reliably. A test that fails some times and passes some times
is...suboptimal when dealing with a buildbot testing infrastructure :)
--
nosy:
R. David Murray added the comment:
The problem with using textwrap is that you'd have to identify paragraph
boundaries and example code to avoid messing up the meaning of the doc string.
At that point, one might as well go for full ReST markup parsing, and I don't
think that is a
R. David Murray added the comment:
I think you are incorrect about the comma after element. Without the comma
'the first matching element or the default value' are tightly bound, meaning
that if either of those is true, then the default value is returned. That's
obviously
R. David Murray added the comment:
Whatever the solution to this issue is, it certainly looks like a bug that the
return value of that function isn't being checked for errors.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.py
R. David Murray added the comment:
This appears to be working as designed, and so is probably a doc issue. Python
3, which only has one integer type, has the same behavior:
>>> x = 2677691728509 << 2147483648
Traceback (most recent call last):
File "", line 1, in
R. David Murray added the comment:
'is' may be technically correct, however it will sound wrong to a native
speaker's ear, at least in America.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.py
R. David Murray added the comment:
I imagine the problem exists in 3.x as well (unless someone proves otherwise),
so I'm adjusting the versions to the places it can be fixed.
Does the patched test still work with the older zlib?
--
nosy: +r.david.murray
priority: -> norm
R. David Murray added the comment:
Python is used to build python. Theoretically you should be able to avoid that
rebuild. cf the following thread:
http://mail.python.org/pipermail/python-dev/2006-April/063511.html
and the referenced issue 1465408. asdl_c.py is going to be importing
R. David Murray added the comment:
That sounds like the likely explanation.
--
resolution: -> works for me
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
You are correct, this is the expected behavior. Name mangling happens only at
compilation time (see
http://docs.python.org/reference/expressions.html#atom-identifiers). A doc
note for get/setattr would probably be useful.
(I removed 3.3; that version
R. David Murray added the comment:
Actually, the list Terek posted a link to is a public doc page, and as was made
clear in the recent issue about the check_warnings helper, we do have to
maintain backward compatibility.
There (should be) undocumented stuff in test_support, purposely left
R. David Murray added the comment:
Nick's point is that we should be testing both the value 0 and the value -1,
but that we should expect 0 to fail only if zlib.ZLIB_VERSION is less than
1.2.4. So you'll need to update your patch to keep the 0 test but put it
inside an a
R. David Murray added the comment:
Are we safe using string comparison here? How likely is zlib to get into
double digit release numbers? (Too bad the version comparison stuff Tarek is
working on isn't already available.)
--
___
Python tr
Changes by R. David Murray :
--
nosy: +lemburg
___
Python tracker
<http://bugs.python.org/issue8271>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
The else branch of the test should also check that 0 does *not* raise an error.
--
___
Python tracker
<http://bugs.python.org/issue8
R. David Murray added the comment:
cmp is gone. It's chances of coming back are close enough to zero that an
assertAlmostEqual test will pass :). The rest of the discussion should move to
one of the general python lists.
--
nosy: +r.david.m
R. David Murray added the comment:
Removed [patch] from title as patch is set on the keywords. Removed 2.5 from
versions because it is in security fix only mode (we use versions for where
things will be fixed, not where they are broken). Changed component to Library
as this is not a bug in
Changes by R. David Murray :
--
dependencies: +doctest should normalize tabs when comparing output
title: [patch] difflib should separate filename from timestamp with tab ->
difflib should separate filename from timestamp with tab
___
Python trac
R. David Murray added the comment:
I imagine this affects 3.1 and 3.2 as well, but I haven't added them to
versions since that hasn't been confirmed.
--
keywords: +easy
nosy: +brian.curtin, loewis, r.david.murray
priority: -> low
stage: -> needs patch
type: ->
R. David Murray added the comment:
I do know something about web development, so I did a more extensive edit. I'm
not saying I've brought it completely up to date or fixed any inaccuracies, but
I did change the tone here and there, tightened up a bunch of the language,
clari
R. David Murray added the comment:
Please target argparse rather than optparse, or better yet in addition to
optparse. And I'm +1 for making it easier to write completion scripts.
--
nosy: +bethard, r.david.murray
___
Python tracker
R. David Murray added the comment:
I think I can see how it would cause confusion, and in general it shouldn't be
necessary to use real tabs in a doctest. So as you say the output should be
fixed to match.
However, I don't think the patch is quite correct. It looks to m
R. David Murray added the comment:
Your last patch looks the best to me. I agree both that a tab should not be
emitted if there is no date (which is what git, for example, does), and that
ISO 8601 timestamps should be promoted as the preferred format.
As you pointed out, issue 7583 needs to
R. David Murray added the comment:
Having thought about it some more, I see why you did the patch the way you did.
The fact that there are two completely different ways to expand tabs in the
output that are equally valid and have their advantages and disadvantages makes
me wonder if this
R. David Murray added the comment:
We could avoid the 7583 problem by making the doctests use NORMALIZE_WHITESPACE
and moving the real *tests* into the unittests for the module. I think that
would be a good thing to do anyway.
--
___
Python
Changes by R. David Murray :
--
resolution: -> wont fix
stage: test needed -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
Any chance you could create a unit test for this? (The current set of tests
is...pretty minimal.) Also, having the patch in unified diff format relative
to the top of the source three would be helpful (although this one is small
enough we could certainly
R. David Murray added the comment:
@andyharrington: No, crash is when the interpreter segfaults.
I'm making it priority high, though, since it is a hang during an operation
that is likely to happen fairly frequently. Senthil may want to bump it up
even higher.
@neologix: Thanks for fig
R. David Murray added the comment:
Hmm. The patch didn't apply to my current trunk checkout. I'll look into why
later.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.
R. David Murray added the comment:
Committed in r79778. We'll see how the buildbots fare.
--
stage: patch review -> commit review
___
Python tracker
<http://bugs.python.or
New submission from R. David Murray :
==
FAIL: test_ulonglong (ctypes.test.test_callbacks.Callbacks)
--
Traceback (most recent call last):
File
"/
R. David Murray added the comment:
The ubuntu and debian sparc buildbots show the same failure, none of the other
buildbots do.
--
___
Python tracker
<http://bugs.python.org/issue8
R. David Murray added the comment:
Committed in r79803. I changed the assert_ to an if not m/fail, since assert_
is deprecated and I think the if makes it clearer than the assert_ what it is
that is being checked.
--
components: +Tests
priority: -> normal
resolution: ->
R. David Murray added the comment:
It's not inappropriate, since the facilities *in* the email package are
supposed to support other MIME use cases (such as HTML). That it isn't clear
how to convert is certainly a doc bug at the very least. However, I wouldn't
be entirely su
Changes by R. David Murray :
--
keywords: +easy
nosy: +orsenthil
priority: -> normal
stage: -> test needed
___
Python tracker
<http://bugs.python.org/
R. David Murray added the comment:
Depending on the feature, I might agree with that, but I wasn't involved in
that decision.
If email only supports something structured with proper MIME headers and
multifile is more general (which I *think* is the case, but I haven't actually
tr
R. David Murray added the comment:
The buildbots seem happy.
--
resolution: -> fixed
stage: commit review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
Why do you think issue 3770 is not relevant? It looks from the traceback like
the built version of multiprocessing decided that sem_open wasn't functional.
So this sounds like a lucid packaging problem to me.
--
components: +Extension Modules
R. David Murray added the comment:
I'm guessing Matthias might have some insight into this on the Ubuntu side. so
I'm adding him as nosy. I'm thinking this isn't a Python problem, but I could
be wrong.
--
nosy: +doko
title: Cannot import name SemLock -> Cannot
R. David Murray added the comment:
Making the stage test needed, since we need to get the test into the test suite
as a unit test.
--
nosy: +r.david.murray
stage: needs patch -> test needed
title: zipfile DeprecationWarning Python 2.5/2.6 -> zipfile DeprecationWarning
Python
R. David Murray added the comment:
Well, as I said, I think it would be better to delete the conditional instead.
(That is, that fixing the typo is more likely to lead to a bug).
--
assignee: barry -> r.david.murray
___
Python tracker
&l
R. David Murray added the comment:
After tracing the code further I now understand what the original patch is
doing, and yes the spelling correction is the correct fix. (The issue is that
there are two different encodings involved: the input encoding in which the
body is encoded when
R. David Murray added the comment:
This is a feature request, so it only applies to unreleased versions. It'll be
up to Benjamin whether it can go into 2.7, if the change is approved, since 2.7
is now technically in feature freeze.
The patch also needs unit tests.
I do like the id
R. David Murray added the comment:
The unit test passes on trunk for me without the fix applied.
--
___
Python tracker
<http://bugs.python.org/issue7559>
___
___
R. David Murray added the comment:
Great, thanks. I'll check this in when the branch is unfrozen.
--
dependencies: -doctest should normalize tabs when comparing output
___
Python tracker
<http://bugs.python.org/i
2001 - 2100 of 10554 matches
Mail list logo
