Ezio Melotti added the comment:
Can this be closed then?
--
nosy: +ezio.melotti
status: open - pending
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11656
___
Roundup Robot added the comment:
New changeset 2889f71c9e20 by Ezio Melotti in branch 'default':
#15121: document the email component.
http://hg.python.org/devguide/rev/2889f71c9e20
--
nosy: +python-dev
___
Python tracker rep...@bugs.python.org
Ezio Melotti added the comment:
I documented the email component, and removed the None component.
I'm still not sure what to do about Cross-build -- maybe it should be removed
as well. Its name is self-explanatory, so even if it's not removed and it's
not documented I don't think it's a big
Nick Coghlan added the comment:
I hadn't noticed that type.__new__ copied the contents (it surprises me that it
does both that *and* restricts the input type to a true dict instance).
The Extending a class example should still work as shown, since the magic of
that happens while the body of
Senthil Kumaran added the comment:
Reviewed the patch - the logic looks okay to me - namely verifying that the
changeset the merged with the next +0.1, 3.x branch or default.
I tested.
2.7 - push - success.
3.1 - push - fail - merge to 3.2 - fail - merge to default - success.
Looks like a
Changes by Ezio Melotti ezio.melo...@gmail.com:
Removed file: http://bugs.python.org/file29394/issue14468-new-faqs.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14468
___
Ezio Melotti added the comment:
The attached patch fixes the typo and mentions ``hg heads branch``.
I think a version of your 6 step display would be helpful. It was for me.
The FAQ already describes the general approach (merge heads in each branch and
then merge branches as usual). The
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
stage: patch review - commit review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11479
___
___
Ezio Melotti added the comment:
I left a review on rietveld.
--
nosy: +ezio.melotti
stage: - patch review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17232
___
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
keywords: +easy
nosy: +ezio.melotti
stage: - test needed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17403
___
Ezio Melotti added the comment:
Closing this as duplicate of #13963.
--
resolution: - duplicate
stage: needs patch - committed/rejected
status: open - closed
superseder: - dev guide has no mention of mechanics of patch review
___
Python tracker
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
stage: - patch review
versions: +Python 3.4 -Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11454
___
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
versions: +Python 3.4 -Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1243730
___
___
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
keywords: +easy
versions: +Python 3.4 -Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6640
___
Helmut Jarausch added the comment:
The problem is caused by the new format_exception in Python's traceback.py
file. It reads
def format_exception(etype, value, tb, limit=None, chain=True):
list = []
if chain:
values = _iter_chain(value, tb)
else:
values = [(value, tb)]
for
Ezio Melotti added the comment:
This can be in a general Mercurial section before the section specific
to committers, or else spread throughout (e.g. in the FAQ).
FWIW I'm leaning towards making the committing.rst page for committers only,
and move general instructions for non-committers
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
keywords: +easy
nosy: +ezio.melotti
stage: - needs patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15575
___
Ezio Melotti added the comment:
Should this still be backported on 2.7?
--
keywords: +easy
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10872
___
R. David Murray added the comment:
Because the second argument to format_traceback is supposed to be (is
documented to be) an exception object. The fact that it used to work anyway in
Python2 if you passed a string was an accident of the implementation.
Likewise, settrace is documented to
New submission from Chris Angelico:
The timeit module is commonly used via the convenience function timeit.timeit,
which is listed in the documentation as the recommended Python Interface:
http://docs.python.org/3/library/timeit.html
However, this function is not listed in __all__, meaning
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti, terry.reedy
stage: needs patch - patch review
versions: +Python 3.4
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14515
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
assignee: - docs@python
components: +Documentation
keywords: +easy
nosy: +docs@python, ezio.melotti
stage: - needs patch
versions: +Python 2.7, Python 3.2, Python 3.4
___
Python tracker
Ezio Melotti added the comment:
What's the status of this?
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13604
___
___
Ezio Melotti added the comment:
Since 3.1 is no longer maintained I'm going to close this.
--
nosy: +ezio.melotti
resolution: - out of date
stage: needs patch - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
Ezio Melotti added the comment:
there's an issue about that.
That would be #8273. See also #17037 and PEP 399.
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9104
Ezio Melotti added the comment:
Perhaps __qualname__ could be used in the traceback.
--
keywords: +easy
nosy: +ezio.melotti, pitrou
stage: - needs patch
versions: +Python 3.4 -Python 3.2
___
Python tracker rep...@bugs.python.org
New submission from Gurmeet Singh:
This is the first time I am creating an issue. I may be doing something wrong.
I will correct that if you make me aware about it!
Issue with documentation:
Documentation page: http://docs.python.org/3/library/os.path.html
Entry: os.path.normpath(path)
New submission from Gurmeet Singh:
Source page: http://docs.python.org/3/library/os.html
Entry: os.walk(...)
Ambiguity Source: Name of the argument TopDown and / or its description.
The TopDown name is misleading to me. I would suggest BFS or DFS instead.
TopDown false would imply to me that
Giampaolo Rodola' added the comment:
I wasn't aware of this issue (sorry) and I have already fixed this back in cset
422169310b7c for the 3.4 branch.
2.7, 3.2 and 3.3 branches can still be fixed though.
--
versions: +Python 2.7 -Python 3.4
___
New submission from Gurmeet Singh:
Source page: http://docs.python.org/3/library/os.html
Entry: os.walk(...), os.fwalk()
These functions seems to be a generator functions. An expert like yourself may
have no trouble to make this out. But for novice (or for people out of touch)
like myself
Vinay Sajip added the comment:
I don't believe this is logging-related - it relates to how you can rename open
files on POSIX. Both loggers use the same file, until rollover - thereafter,
they use different files, resulting in the behaviour you saw. To illustrate,
run the following script on
Vinay Sajip added the comment:
BTW in the example script I do fa.flush() a couple of times when I meant to do
fb.flush() (in the i == 3 clause). The result is the same after correcting this.
--
___
Python tracker rep...@bugs.python.org
Piotr Dobrogost added the comment:
I don't understand whether you are proposing to include the patch into Python
as-is;
I think Richard is well aware of the constraints you specify and current patch
was meant as a proof of concept; to show that all tests pass with such a
change. Of course
Berker Peksag added the comment:
+skip_if_dont_write_bytecode = unittest.skipIf(
+sys.dont_write_bytecode,
+test meaningful only when writing bytecode)
Maybe this could be added to the test.support module?
--
nosy: +berker.peksag
___
Anuj Gupta added the comment:
I'm a new contributor so, not sure if I'm missing anything:
The issue seems straightforward to me, the exports should definitely be
included in both - the docstring and __all__. Also, default_timer is documented
and should be imported as well.
I've contributed a
bagrat lazaryan added the comment:
good. thank you.
i'm not sure about the architecture. i understand it's not crucial for most of
the users. i would like to have it though.
--
___
Python tracker rep...@bugs.python.org
Changes by Jeroen Demeyer jdeme...@cage.ugent.be:
--
nosy: +jdemeyer
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1222585
___
___
Martin v. Löwis added the comment:
Am 14.03.13 03:31, schrieb Piotr Dobrogost:
forces programs which would like to open a file being opened at the
same time by Python code (by means of built-in open() or os.open()
with default arguments) to either use O_TEMPORARY when using msvcrt
or to go
Changes by Martin v. Löwis mar...@v.loewis.de:
--
resolution: - wont fix
status: pending - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11656
___
alef added the comment:
The same happens with AIX 6.1 using xlc 10.1. Using -P implies removing -o
output_file. The resulting _configtest.i is anyhow empty, even using -qppline.
--
nosy: +alef
___
Python tracker rep...@bugs.python.org
Changes by alef alessandro.for...@eumetsat.int:
--
nosy: +alef
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11188
___
___
Python-bugs-list
Changes by alef alessandro.for...@eumetsat.int:
--
nosy: +alef
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11192
___
___
Python-bugs-list
Changes by alef alessandro.for...@eumetsat.int:
--
nosy: +alef
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11190
___
___
Python-bugs-list
Changes by alef alessandro.for...@eumetsat.int:
--
nosy: +alef
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15477
___
___
Python-bugs-list
Changes by alef alessandro.for...@eumetsat.int:
--
nosy: -alef
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15477
___
___
Python-bugs-list
Changes by alef alessandro.for...@eumetsat.int:
--
nosy: +alef
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9920
___
___
Python-bugs-list mailing
Richard Oudkerk added the comment:
On 14/03/2013 1:00pm, Martin v. Löwis wrote:
That's why I was asking for an actual patch. The proposed change may
well not be implementable. If os.open continues to create CRT handles,
a way needs to be found to get a CRT handle that as the
Stefan Krah added the comment:
I agree with won't fix for the original issue. These locale functions
are in effect superseded by PEP 3101 formatting.
For decimal locale specific formatting, use:
format(Decimal(1729.1415927), n)
IOW, I don't think new formatting functions should be added to
New submission from Gurmeet Singh:
Incompletely explained documentation at 2 places:
1. http://docs.python.org/3/library/functions.html#open
The buffering argument is not correctly explained when setting to a positive
argument in binary mode.
2.
Cédric Krier added the comment:
locale.atof is not about formatting but parsing string into float following the
locale.
For now, the only ways I see to parse a string to get a Decimal is to first
convert it into float (which is not good if precision matters) or to use the
undocumented
Stefan Krah added the comment:
Cédric Krier rep...@bugs.python.org wrote:
locale.atof is not about formatting but parsing string into float following
the locale.
You're right. Sorry, I never use these locale functions. My impression is
that locales are often buggy or differ across platforms
James Kesser added the comment:
My approach was just as outlined in the first few paragraphs here, just naming
loggers for each module using __name__:
http://docs.python.org/2/howto/logging.html#logging-advanced-tutorial
If this is not recommended the documentation should be updated to
James Kesser added the comment:
Thanks for quick response!
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17407
___
___
Python-bugs-list mailing
New submission from Sergio Callegari:
When installing a package by calling setup you have a --user option to install
the package for a single user in his disk area.
E.g.,
python setup.py install --user
A similar possibility should be offered via the windows installer
An exe created by
New submission from Sergio Callegari:
When creating an installer with bdist_wininst, any unicode characters in the
description and long_description fields get mangled when running the installer.
--
messages: 184172
nosy: Sergio.Callegari
priority: normal
severity: normal
status: open
Andreas Kloeckner added the comment:
Thanks for the suggestion. Since 3.2 and 3.3 will be with us for a while, I've
implemented the workaround you've suggested. Works, too. :)
--
___
Python tracker rep...@bugs.python.org
paul j3 added the comment:
If nargs=2, type=float, an argv like '1e4 -.002' works, but '1e4 -2e-3'
produces the same error as discussed here. The problem is that
_negative_number_matcher does not handle scientific notation. The proposed
generalize matcher, r'^-.+$', would solve this, but
Martin v. Löwis added the comment:
Would you like to work on a patch?
--
nosy: +loewis
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17419
___
___
Martin v. Löwis added the comment:
Would you like to work on a patch?
--
nosy: +loewis
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17420
___
___
Evgeny Kapun added the comment:
The way how argparse currently parses option arguments is broken. If a long
option requires an argument and it's value isn't specified together with the
option (using --option=value syntax), then the following argument should be
interpreted as that value, no
Eric V. Smith added the comment:
Evgeny: I completely agree. It's unfortunate that argparse doesn't work that
way.
However, I think it's too late to change this behavior without adding a new
parser. I don't think existing argparse can be changed to not operate the way
it does, due to
Roundup Robot added the comment:
New changeset 8a0b5c9f04c2 by Serhiy Storchaka in branch '2.7':
Issue #17299: Add test coverage for cPickle with file objects and general IO
http://hg.python.org/cpython/rev/8a0b5c9f04c2
--
nosy: +python-dev
___
paul j3 added the comment:
We need to be careful about when or where _negative_number_match is changed.
We basically do:
parser = argparse.ArgumentParser(...)
parser._negative_number_matcher = re.compile(r'^-.+$')
This changes the value for the parser itself, but not for the groups
Serhiy Storchaka added the comment:
I'm a little polished the patch before committing. Thank you for the patch,
Aman Shah.
--
resolution: - fixed
stage: commit review - committed/rejected
status: open - closed
___
Python tracker
Roundup Robot added the comment:
New changeset 4927899bea8d by Serhiy Storchaka in branch '2.7':
Issue #1285086: Get rid of the refcounting hack and speed up urllib.unquote().
http://hg.python.org/cpython/rev/4927899bea8d
New changeset 3cb07925fcb9 by Serhiy Storchaka in branch '3.2':
Issue
Serhiy Storchaka added the comment:
Sorry, I perhaps missed your response, Senthil. Now committed and closed again.
--
resolution: - fixed
stage: patch review - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
Serhiy Storchaka added the comment:
Of course it would be nice to have the tests for so much cases as possible, but
I am afraid that it will not be easy. The patch LGTM.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17016
Sergio Callegari added the comment:
On 14/03/2013 18:15, Martin v. Löwis wrote:
Martin v. Löwis added the comment:
Would you like to work on a patch?
--
nosy: +loewis
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17420
Serhiy Storchaka added the comment:
I think these tests have no sense after PEP393. They tests that StreamWriter
works with non-BMP characters broken inside surrogate pair. I.e.
c.write(s[:i]); c.write(s[i:]) always is same as c.write(s), even if i breaks s
inside a surrogate pair. This case
New submission from Eric Snow:
Currently type_new() in Objects/typeobject.c enforces a restriction that the
namespace be a dict or dict subclass. It does this via the
PyArg_ParseTupleAndKeywords() call there.
This means that valid mappings may not be used even though they should work
just
New submission from Eric Snow:
(related to PEP 422 and issue #17044)
The execution namespace from a class definition is passed as the third argument
to the metaclass (see builtin___build_class__() in Python/bltinmodule.c). When
applicable, which is almost always, the subsequent call to
Eric Snow added the comment:
We should definitely have a way to expose the original dictionary from
__prepare__(). Along with Nick's point, another reason is to allow class
decorators to have access to that original, which is important to any use case
that involves post-creation
Eric Snow added the comment:
I've also opened #17421 for dropping the restriction on the namespace passed to
the metaclass and #17422 for documenting that the passed namespace is copied
into a new dict.
--
___
Python tracker rep...@bugs.python.org
Serhiy Storchaka added the comment:
Test fails with stack overflow:
==
ERROR: test_pushCR_LF (email.test.test_email.TestIterators)
FeedParser BufferedSubFile.push() assumed it received complete
Eric Snow added the comment:
Given that, it is probably also better to revert the namespace keyword
to accepting an instance rather than a factory function, since the copy
operation after execution of the class body is automatic.
Agreed. Of course, the related note is rendered superfluous.
New submission from Maciej Fijalkowski:
The bug is a little tricky to reproduce. You need a 32bit linux. First compile
x.c with:
gcc -O3 -g -shared -o x.so x.c -std=c99 -msse3 -ftree-vectorize -mfpmath=sse
and run x.py. It segfaults because the alignment of stack is not preserved (and
it's
Changes by Maciej Fijalkowski fij...@gmail.com:
Added file: http://bugs.python.org/file29410/x.py
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17423
___
Changes by Maciej Fijalkowski fij...@gmail.com:
Removed file: http://bugs.python.org/file29409/x.c
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17423
___
Changes by Maciej Fijalkowski fij...@gmail.com:
Added file: http://bugs.python.org/file29411/x.c
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17423
___
Changes by Maciej Fijalkowski fij...@gmail.com:
--
keywords: +patch
Added file: http://bugs.python.org/file29412/ffi.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17423
___
New submission from Sean Reifschneider:
David Beazley in his tutorial pointed out that you could use a metaclass to
create function signatures for the common use case of:
class foo:
def __init__(self, name, value, high, low):
self.name = name
self.value = value
[...]
The
Changes by Alex Gaynor alex.gay...@gmail.com:
--
nosy: +alex
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17423
___
___
Python-bugs-list mailing
Nick Coghlan added the comment:
Oh, that's bizarre - the presence of __locals__ is a side effect of
calling locals() in the class body. So perhaps passing the namespace
as a separate __init_class__ parameter is a better option.
--
___
Python tracker
Changes by Daniel Urban urban.dani...@gmail.com:
--
nosy: +daniel.urban
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17422
___
___
Changes by Daniel Urban urban.dani...@gmail.com:
--
nosy: +daniel.urban
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17421
___
___
Vinay Sajip added the comment:
My approach was just as outlined in the first few paragraphs
The not-recommended approach I'm referring to is that of having a two
RotatingFileHandlers *with the same filename* attached to two loggers.
It's perfectly OK to follow the recommendation of naming
Ezio Melotti added the comment:
On Linux make html seems to use v1.0.7 too, so updating make.bat should be OK.
See also #16471.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17412
___
Ezio Melotti added the comment:
When this is done make.bat should be updated too.
--
stage: - needs patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16471
___
New submission from Antoine Pitrou:
OpenSSL recently issued a security advisory (*). Our bundled OpenSSL versions
seem to be vulnerable. They should be updated to OpenSSL 1.0.1d, 1.0.0k or
0.9.8y depending on the version.
(*) http://www.openssl.org/news/secadv_20130205.txt
Apologies if this
Martin v. Löwis added the comment:
I'd like to, but I really have no clue on bdist_wininst
That's perfectly fine. If people make feature requests, it's
often uncertain whether they lack time or knowledge, or are
merely to shy/uncertain to propose a patch. So somebody else
needs to volunteer to
Stefan Krah added the comment:
Is this the same as #17245?
--
nosy: +skrah
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17423
___
___
Maciej Fijalkowski added the comment:
This patch is not in the whatever version ubuntu supplies. Btw, this is code
duplication, since there is already darwin alignment, see 17423
--
nosy: +fijall
___
Python tracker rep...@bugs.python.org
Martin v. Löwis added the comment:
Are you sure that non-dicts work fine? ISTM that there is quite some code that
relies on tp_dict being a dict-or-subdict instance, e.g. in
typeobject.c:type_module,type_get_doc etc.
--
nosy: +loewis
___
Python
Martin v. Löwis added the comment:
No, it hasn't been handled. I'll look into it next week.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17425
___
Ezio Melotti added the comment:
There are a couple more tests elsewhere that use
@skipIf(sys.dont_write_bytecode, ...) directly, but I don't think it's generic
enough to be moved to test.support.
--
___
Python tracker rep...@bugs.python.org
Eric Snow added the comment:
Sorry I wasn't clear. Later in type.__new__() it copies that passed namespace
into a new dict (see issue #17422). So as long as the namespace argument is a
valid argument to dict(), it's going to work fine. We don't need the extra
explicit check performed by
Roundup Robot added the comment:
New changeset 7338e7ec47f0 by Terry Jan Reedy in branch '2.7':
Issue #17412: update 2.7 Doc/make.bat to also use sphinx-1.0.7.
http://hg.python.org/cpython/rev/7338e7ec47f0
--
nosy: +python-dev
___
Python tracker
Changes by Terry J. Reedy tjre...@udel.edu:
--
resolution: - fixed
stage: needs patch - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17412
___
Changes by Andrew Svetlov andrew.svet...@gmail.com:
--
nosy: +asvetlov
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17423
___
___
Terry J. Reedy added the comment:
This duplicates a part of #10224, which proposes to upgrade all of Sphinx,
Jinja2, and Pygments to Python 3 compatible versions (so we can build docs with
Py3). In msg175768, Brett claims that all three have such versions.
Chris, if you want to push to only
1 - 100 of 106 matches
Mail list logo
