Richard Jones richardjo...@optushome.com.au added the comment:
Merged mock socket from test_smtpd.py and committed.
--
resolution: - accepted
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2423
Richard Jones richardjo...@optushome.com.au added the comment:
The smtpd module now has a test suite. Please add your unit tests to
test_smtpd.py
--
nosy: +richard
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8739
Ronald Oussoren ronaldousso...@mac.com added the comment:
On 2 Aug, 2010, at 21:49, Bill Janssen wrote:
Bill Janssen bill.jans...@gmail.com added the comment:
So the problem is in the _mac_ver_xml() routine in Lib/platform.py, which
says:
machine = os.uname()[4]
if machine
Ronald Oussoren ronaldousso...@mac.com added the comment:
Some else backported to 3.1 (that is, 3.1 already contained the fix when I
tried the svnmerge)
Backported to 2.7 in r83643
Backported to 2.6 in r83650
--
Added file: http://bugs.python.org/file18336/smime.p7s
Changes by Ronald Oussoren ronaldousso...@mac.com:
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7900
___
___
Ronald Oussoren ronaldousso...@mac.com added the comment:
Fixed in r83644 (3.x), r83645 (3.1), r83646 (2.7), r83651 (2.6)
I'm not yet closing the issue, I want to check the buildbots later today.
--
resolution: - fixed
stage: - committed/rejected
status: open - closed
versions:
Changes by Trundle andy-pyt...@hammerhartes.de:
--
nosy: +Trundle
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1748064
___
___
Python-bugs-list
Éric Araujo mer...@netwok.org added the comment:
Is this a behavior bug or a doc bug?
--
nosy: +merwok
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9458
___
Changes by Florent Xicluna florent.xicl...@gmail.com:
--
nosy: +effbot, flox
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9458
___
___
Éric Araujo mer...@netwok.org added the comment:
And if you don’t allow hooks on other commands, people can still subclass them
to add hooks support. I guess it’s best to keep it a consenting adults matter
and not adding a restriction that can easily be circumvented.
--
W. Trevor King wk...@drexel.edu added the comment:
And while we're at it, we should also
.replace('', 'amp;').replace('', quot;).replace('', 'lt;')
which would have to go at the beginning to avoid double-escaping the ''.
We could use xml.sax.saxutils.escape to do all the escaping rather
Changes by Éric Araujo mer...@netwok.org:
--
nosy: +merwok
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6517
___
___
Python-bugs-list mailing
Georg Brandl ge...@python.org added the comment:
The 3.2 docs now don't mention ConfigParser prominently anymore (as part of a
different patch that added some features). Could be done in other branches as
well.
--
___
Python tracker
Changes by Éric Araujo mer...@netwok.org:
--
nosy: +lukasz.langa, merwok
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6751
___
___
Éric Araujo mer...@netwok.org added the comment:
Why is it needed to add varargs and kwargs instead of only a new “default”
argument?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6751
Changes by Éric Araujo mer...@netwok.org:
--
nosy: +lukasz.langa
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1410680
___
___
Python-bugs-list
Łukasz Langa luk...@langa.pl added the comment:
Yes, so the patch part is already solved. The thing that is still open to
discussion is whether we should do something like this:
1. Pending-Deprecate naked the ConfigParser class in 3.2.
2. Deprecate it in 3.3.
3. Remove it in 3.4 and rename
Michael Foord mich...@voidspace.org.uk added the comment:
+1 for deprecation. Nobody *should* be using ConfigParser anyway, and of those
who are 99% either wouldn't notice or would have bugs in their code *fixed* by
the rename, so I can't see much of a downside.
--
Éric Araujo mer...@netwok.org added the comment:
If ConfigParser is not documented first, the name “SafeConfigParser” becomes
strange—safe compared to what? These names have an historical motivation and
could become clearer if renamed, but I don’t know if python-dev will agree with
this
Łukasz Langa luk...@langa.pl added the comment:
If ConfigParser is not documented first, the name “SafeConfigParser” becomes
strange—safe compared to what?
The first sentence is Derived class of ConfigParser that implements a sane
variant of the magical interpolation feature. I think it's
Georg Brandl ge...@python.org added the comment:
Agree with Michael, +1.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6517
___
___
Changes by Antoine Pitrou pit...@free.fr:
--
keywords: +easy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9292
___
___
Python-bugs-list mailing
Ray.Allen ysj@gmail.com added the comment:
Doc review: Small typo, Flase vs False. Also, exceptions are raised rather
than thrown in Python land (same for the docstring). Both exception
references should be :exc:`OSError`.
Here fixed these doc problems. Thanks for reviewing! Besides,
Georg Brandl ge...@python.org added the comment:
Thanks for bringing that up, I've now fixed all these instances of throw that
should be raise.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9299
Éric Araujo mer...@netwok.org added the comment:
The first sentence is Derived class of ConfigParser that implements
a sane variant of the magical interpolation feature. I think it's
enough for an explanation.
True.
but I don’t know if python-dev will agree with this deprecation.
I wrote
Éric Araujo mer...@netwok.org added the comment:
Are 2.6 docs built by an older Sphinx version? I wonder why the text uses “the
:func:`quoteattr` function in the :mod:`xml.sax.saxutils` module” and not
“:func:`~xml.sax.saxutils.quoteattr” to get a direct link (or even just
“consider using
Georg Brandl ge...@python.org added the comment:
No, that's just a relic from the olden LaTeX days, and I've not paid attention
enough to fix it :)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9061
Łukasz Langa luk...@langa.pl added the comment:
Eric, while I agree that would be nice as well, renaming each and every parser
in the module will be more problematic for sure.
*** TO ALL: WHAT DO YOU SAY TO A PATH LIKE THIS ***
1) In 3.2 we add an alias:
InterpolatingConfigParser =
Fred L. Drake, Jr. fdr...@acm.org added the comment:
2010/8/3 Łukasz Langa rep...@bugs.python.org:
1) In 3.2 we add an alias:
InterpolatingConfigParser = SafeConfigParser
I'd rather see the class renamed and SafeConfigParser made the alias in 3.2.
Otherwise, +1 for this plan (msg 112589),
Michael Foord mich...@voidspace.org.uk added the comment:
I'd be happy with aliasing SafeConfigParser to ConfigParser in 3.2. Can we just
do this without a deprecation process?
--
___
Python tracker rep...@bugs.python.org
Fred L. Drake, Jr. fdr...@acm.org added the comment:
Making ConfigParser an alias for SafeConfigParser creates a silent
behavioral change. An application developer may not realize that
users rely on the full ConfigParser anti-glory and end up breaking
their configurations without so much as
Łukasz Langa luk...@langa.pl added the comment:
Unfortunately, I have to agree with Fred here. We'll stick to renaming and the
deprecation process.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6517
Fred L. Drake, Jr. fdr...@acm.org added the comment:
Such constructs are notoriously tedious to grep for; patches are welcome.
--
nosy: +fdrake
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9061
Michael Foord mich...@voidspace.org.uk added the comment:
Sorry - I misunderstood your earlier suggestion Fred.
configparser.ConfigParser is the *natural* name for SafeConfigParser. I'm
strongly +1 on moving towards that. (I doubt there would *actually* be any real
code breakage if we did it
Michael Foord mich...@voidspace.org.uk added the comment:
By the way, given that deprecation warnings are silent I am strongly -1 on
removing the ConfigParser name altogether. That would cause far more breakage.
As ConfigParser should not be used at all, and SafeConfigParser provides its
Steven Bethard steven.beth...@gmail.com added the comment:
Yep, I'm fine with you committing this (after adding the prefix=+-/ you
suggested). I don't have time right now to test the patches, but the code looks
about right, and the tests ran fine for you, so I'm fine with it.
--
Éric Araujo mer...@netwok.org added the comment:
Agree on the proposal of Łukasz, with the caveat mentioned by Fred (rename the
class and make the old name an alias, for pickle and all). I’ll let Michael and
Fred decide if the name ConfigParser has to go or not, I’m happy enough that
the
Changes by Meador Inge mead...@gmail.com:
--
nosy: +minge
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4188
___
___
Python-bugs-list mailing list
Barry A. Warsaw ba...@python.org added the comment:
Hi Ezio, what's the status on this issue for 2.6.6rc1?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7092
___
Changes by Meador Inge mead...@gmail.com:
--
nosy: +minge
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5248
___
___
Python-bugs-list mailing list
Changes by Meador Inge mead...@gmail.com:
--
nosy: +minge
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1172711
___
___
Python-bugs-list mailing
Changes by Dirkjan Ochtman dirk...@ochtman.nl:
--
nosy: +djc
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7828
___
___
Python-bugs-list mailing
Changes by Dirkjan Ochtman dirk...@ochtman.nl:
--
nosy: +djc
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7225
___
___
Python-bugs-list mailing
Changes by Dirkjan Ochtman dirk...@ochtman.nl:
--
nosy: +djc
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7186
___
___
Python-bugs-list mailing
Changes by Dirkjan Ochtman dirk...@ochtman.nl:
--
nosy: +djc
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7141
___
___
Python-bugs-list mailing
Changes by Dirkjan Ochtman dirk...@ochtman.nl:
--
nosy: +djc
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8450
___
___
Python-bugs-list mailing
Changes by Dirkjan Ochtman dirk...@ochtman.nl:
--
nosy: +djc
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8867
___
___
Python-bugs-list mailing
Changes by Dirkjan Ochtman dirk...@ochtman.nl:
--
nosy: +djc
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8906
___
___
Python-bugs-list mailing
Changes by Łukasz Langa luk...@langa.pl:
Removed file: http://bugs.python.org/file18329/issue9452.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9452
___
LRN lrn1...@gmail.com added the comment:
Here's an alternative patch that enables Python building with MinGW/MSys
I've skimmed rpetrov's patch, and it seems that my patch is more about building
Python than about distutils (i've patched distutils only as far as the
compilation of Python itself
Changes by Dirkjan Ochtman dirk...@ochtman.nl:
--
nosy: +djc
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8138
___
___
Python-bugs-list mailing
Changes by Dirkjan Ochtman dirk...@ochtman.nl:
--
nosy: +djc
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6785
___
___
Python-bugs-list mailing
Łukasz Langa luk...@langa.pl added the comment:
Updated patch after discussion on #python-dev:
- PEP8 compliant names used: read_file, read_string, read_dict. readfp has been
PendingDeprecated
- documentation updates
- option validation is now optional with the use of `strict=` argument in the
Łukasz Langa luk...@langa.pl added the comment:
FTR, some people questioned the purpose of read_dict(). Let me summarize this
very briefly here:
- the API is using dictionaries similar to those in defaults= but has one level
of depth more (sections)
- initializing a parser with a dictionary
Michael Foord mich...@voidspace.org.uk added the comment:
Getting *rid* of the name ConfigParser would be annoying and cause *gratuitous*
code breakage.
If we are going to keep the name but get rid of the unsafe version then we
can only replace it with what is now SafeConfigParser - as it is
Łukasz Langa luk...@langa.pl added the comment:
There IS one more option that seems to be better than all of the above:
1. Add an interpolation=True argument to RawConfigParser __init__ and move the
interpolating functionality from SafeConfigParser to it.
2. Rename RawConfigParser to
Catherine Devlin fredv8vi...@liquidid.net added the comment:
Attaching a test to verify parse failure on mismatched prefix (-abc or +abc).
Steven's patch makes it pass.
--
nosy: +catherine
versions: -Python 2.7, Python 3.2
Added file:
Catherine Devlin fredv8vi...@liquidid.net added the comment:
Updated Steven's patch; no changes, but now it knows the new context so that
``patch -p0`` won't fail.
--
Added file:
http://bugs.python.org/file18343/multiple_short_same_prefix_new.patch
Mark Dickinson dicki...@gmail.com added the comment:
Leaks in replace_history_item and remove_history_item fixed in r83667 (py3k),
r83668 (release31-maint) and r83669 (release27-maint).
--
versions: +Python 2.7, Python 3.1
___
Python tracker
New submission from R. David Murray rdmur...@bitdance.com:
In python3 if an error is raised from ErrorRaisingArgumentParser that is not
caught by an assertRaises, unittest prints out the traceback, which is a
chained traceback including the SystemExit that the argparse test suite catches
in
Mark Lawrence breamore...@yahoo.co.uk added the comment:
Should this now go to d...@python or is it best left with Christian?
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7003
Mark Lawrence breamore...@yahoo.co.uk added the comment:
@Daniel there's far chance of this happening if you could provide a patch.
--
nosy: +BreamoreBoy
versions: -Python 2.7
___
Python tracker rep...@bugs.python.org
Changes by Mark Lawrence breamore...@yahoo.co.uk:
--
assignee: georg.brandl - d...@python
nosy: +d...@python
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7186
___
R. David Murray rdmur...@bitdance.com added the comment:
I can't find anyway to actually do what I suggested. There doesn't seem to be
any way to break the traceback chain.
--
___
Python tracker rep...@bugs.python.org
Catherine Devlin fredv8vi...@liquidid.net added the comment:
Some basic unit tests for parse_known_args on a subparser.
--
keywords: +patch
nosy: +catherine
Added file:
http://bugs.python.org/file18344/test_subparser_parse_known_args.patch
___
Mark Lawrence breamore...@yahoo.co.uk added the comment:
I'm assuming that this is still an issue, sorry I don't have gcc 4.3.2 to try
it out on.
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7225
Mark Dickinson dicki...@gmail.com added the comment:
I've fixed this leak in r83670 through r83672. It's still using the old,
inefficient method (get the state, read the length, free the state), because
without good tests I don't want to disturb things too much. In particular,
it's not
Mark Dickinson dicki...@gmail.com added the comment:
The other leaks have now been fixed too; see issue 8065 for details.
--
assignee: - mark.dickinson
resolution: - fixed
stage: needs patch - committed/rejected
status: open - closed
___
Python
Changes by Antoine Pitrou pit...@free.fr:
--
assignee: georg.brandl - d...@python
nosy: +d...@python, haypo
versions: -Python 2.6, Python 2.7
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7828
Changes by Catherine Devlin fredv8vi...@liquidid.net:
Removed file:
http://bugs.python.org/file18344/test_subparser_parse_known_args.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9340
___
Antoine Pitrou pit...@free.fr added the comment:
Here is a simple patch.
--
keywords: +patch
nosy: +pitrou
Added file: http://bugs.python.org/file18345/serve.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8867
Antoine Pitrou pit...@free.fr added the comment:
Fixed in r83673.
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8867
___
Catherine Devlin fredv8vi...@liquidid.net added the comment:
Some simple unit tests for parse_known_args on a parser with a subparser. They
are indeed failing on the trunk.
--
Added file:
http://bugs.python.org/file18346/test_subparser_parse_known_args.patch
New submission from Michele Orrù maker...@gmail.com:
The attached patch tests Lib/rlcompleter.py.
--
components: Tests
files: testrlcompleter.patch
keywords: patch
messages: 112636
nosy: ezio.melotti, maker
priority: normal
severity: normal
status: open
title: Unittests for
New submission from Mark Dickinson dicki...@gmail.com:
On OS X 10.6, with a 64-bit build of Python, regrtest -L is showing leaks from
test_ssl. Here are the first few lines of the output; I've also attached the
full output.
newton:py3k dickinsm$ ./python.exe -m test.regrtest -L test_ssl
Fred L. Drake, Jr. fdr...@acm.org added the comment:
It doesn't make sense to make any of these changes to Python 2; this
really should have been separate from the documentation issue. That's
probably understood by everyone, but explicit is better.
Merging implementations
Terry J. Reedy tjre...@udel.edu added the comment:
Intermittent bugs involving 3rd-party packages are hard to even confirm, let
alone fix. 2.6.6rc will be out today, so no fix for that. IDLE on 3.1.2 is more
stable than it was on 3.0, so I will not assume that the problem still exists
on the
Changes by Łukasz Langa luk...@langa.pl:
--
versions: -Python 2.6, Python 2.7, Python 3.1
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6517
___
Changes by Terry J. Reedy tjre...@udel.edu:
--
versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.5, Python 2.6, Python
3.0
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3362
___
Changes by Terry J. Reedy tjre...@udel.edu:
--
status: open - closed
versions: -Python 2.4, Python 3.0
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2620
___
Antoine Pitrou pit...@free.fr added the comment:
From a quick look the patch looks nice, thanks!
There's a typo (builtinis namespace).
--
nosy: +pitrou
versions: +Python 2.7, Python 3.1
___
Python tracker rep...@bugs.python.org
Changes by Antoine Pitrou pit...@free.fr:
--
nosy: +r.david.murray
stage: - patch review
type: feature request - behavior
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9496
___
Terry J. Reedy tjre...@udel.edu added the comment:
Is this still an issue in 2.7 or 3.x?
Or should it be closed?
--
nosy: +tjreedy
versions: +Python 2.7 -Python 2.5, Python 2.6
___
Python tracker rep...@bugs.python.org
Terry J. Reedy tjre...@udel.edu added the comment:
Is this still an issue for 2.7 or 3.x?
Is it actually a Python issue or should it be closed?
--
nosy: +tjreedy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1758146
Michael Foord mich...@voidspace.org.uk added the comment:
If we merge the functionality in a single class with a new name then I guess
that is fine as it will simplify the documentation rather than complexify it
(good word hey). We still need to *mention* the old names so that people
finding
R. David Murray rdmur...@bitdance.com added the comment:
Committed (with the additional test) to py3k in r83657, and 2.7 in r83676.
--
stage: commit review - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
Mark Dickinson dicki...@gmail.com added the comment:
From a bit of experimentation, ssl._ssl._test_decode_cert seems to be the call
that's leaking. I haven't studied the source to see if I can pinpoint the
cause yet.
--
___
Python tracker
Mark Dickinson dicki...@gmail.com added the comment:
The new tests pass on OS X, using both GNU readline (v6.1) and the system
libedit.
--
nosy: +mark.dickinson
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9496
Terry J. Reedy tjre...@udel.edu added the comment:
With 3.1.2, cgi.parse_header gives the same correct response as
cgtest.parse_header, so I will assume that the same is true in 2.7 until
demonstrated otherwise.
--
nosy: +tjreedy
resolution: - fixed
status: open - closed
Terry J. Reedy tjre...@udel.edu added the comment:
Martin, should this be closed? fixed? won't fix? out-of-date?
The link to Modules/Setup does not work for py3k branch.
--
nosy: +tjreedy
___
Python tracker rep...@bugs.python.org
Changes by Terry J. Reedy tjre...@udel.edu:
--
resolution: - out of date
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4956
___
Terry J. Reedy tjre...@udel.edu added the comment:
Is this still a problem with 2.7-3.2?
GP, what state do you think either patch is in?
--
nosy: +tjreedy
stage: - patch review
versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.5, Python 2.6
Terry J. Reedy tjre...@udel.edu added the comment:
The docs say that the locale arg should be None, tuple, or string, so I take
that to mean that Unicode should be OK for 2.x, and that would help porting to
3.x. If bytes are rejected in 3.x, there should be TypeError raised, not
ValueError,
Mark Dickinson dicki...@gmail.com added the comment:
The fix turned out to be as simple as adding a single X509_free call to
_test_decode_cert.
Fixed in revisions r83677 (py3k), r83679 (release31-maint), r83680
(release27-maint) and r83686 (release26-maint). [The last with Barry's
Terry J. Reedy tjre...@udel.edu added the comment:
EM and MB seemed to agree on closing this.
--
nosy: +tjreedy
resolution: - wont fix
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3511
Changes by Terry J. Reedy tjre...@udel.edu:
--
versions: -Python 2.5, Python 2.6, Python 3.0
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2200
___
Changes by Terry J. Reedy tjre...@udel.edu:
--
resolution: - out of date
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1978
___
Uli Kunitz uli.kun...@googlemail.com added the comment:
I believe handling of TextIOWrapper streams is broken in
xml.etree.ElementTree.ElementTree.write().
First example:
import sys
from xml.etree import ElementTree
element = ElementTree.fromstring(foobarfoobar/bar/foo)
element_tree =
Terry J. Reedy tjre...@udel.edu added the comment:
In 3.1.2, a2b_uu() now raises
TypeError: a2b_uu() takes exactly 1 argument (0 given)
as it should. I assume the same of 2.7.
The manual claims, in effect, that a2b_uu(b2a_uu(data))== data.
The behavior of a2b_uu with any other input (not from
Changes by Terry J. Reedy tjre...@udel.edu:
--
versions: -Python 2.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5504
___
___
Python-bugs-list
1 - 100 of 263 matches
Mail list logo
