Florent Xicluna added the comment:
Confirmed.
It should probably raise an ArgumentError like this one.
http://docs.python.org/library/argparse.html#conflict-handler
--
components: +Library (Lib)
nosy: +flox
stage: -> needs patch
versions: +Python
Florent Xicluna added the comment:
I don't see a valid use case to support "-" in the name of the positional
argument.
IMHO, it should raise an error (probably a ValueError) for the add_argument in
this case ...
Or we keep it as-is and close as wont-fix: if the op wants t
Changes by Florent Xicluna :
--
components: +IO
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue15100>
___
___
Python-bugs-list mailing list
Unsub
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue12014>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
nosy: +vinay.sajip
___
Python tracker
<http://bugs.python.org/issue15096>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
nosy: +aronacher, flox
___
Python tracker
<http://bugs.python.org/issue15096>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue13823>
___
___
Python-bugs-list mailing list
Unsubscribe:
Florent Xicluna added the comment:
LGTM too. Thanks.
--
___
Python tracker
<http://bugs.python.org/issue15054>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue805255>
___
___
Python-bugs-list mailing list
Unsubscribe:
Florent Xicluna added the comment:
The werkzeug.urls module has examples of such conversion IRI-to-URI:
https://github.com/mitsuhiko/werkzeug/blob/master/werkzeug/urls.py#L109,L205
--
___
Python tracker
<http://bugs.python.org/issue9
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue15068>
___
___
Python-bugs-list mailing list
Unsubscribe:
Florent Xicluna added the comment:
> File "/home/eliben/python-src/33/Lib/test/regrtest.py", line 710 in main
> File "/home/eliben/python-src/33/Lib/test/regrtest.py", line 1829 in
>
> File "/home/eliben/python-src/33/Lib/runpy.py", line 75 in _
New submission from Florent Xicluna :
With Python 2.7, both b'hello' and br'hello' are wrong.
With Python 3.3, b'hello' is wrong.
$ python2.7 -m tokenize <<<"'hello', u'hello', ur'hello', b'hello', br'hel
Florent Xicluna added the comment:
It should raise a SyntaxError, if coding is 'utf8'.
I don't agree with the last patch proposed.
If the import report a SyntaxError, 'tokenize' should do the same.
$ ./python Lib/test/bad_coding2.py
File "Lib/test/bad_c
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue14998>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue13598>
___
___
Python-bugs-list mailing list
Unsubscribe:
Florent Xicluna added the comment:
This patch seems to fix the issue.
--
keywords: +patch
stage: needs patch -> patch review
Added file: http://bugs.python.org/file25805/issue14990_detect_encoding.diff
___
Python tracker
<http://bugs.pyth
New submission from Florent Xicluna :
I've hit this issue while playing with tokenize for the pep8.py module.
The tokenize detect_encoding() should report SyntaxError when the encoding is
improperly declared.
However it raises a LookupError in some cases.
$ ./python -m tokenize Lib
Changes by Florent Xicluna :
--
nosy: +anikom15, flox, josmiley
___
Python tracker
<http://bugs.python.org/issue11796>
___
___
Python-bugs-list mailing list
Unsub
Florent Xicluna added the comment:
This is a duplicate of issue 11796.
See also issue 13557:
http://bugs.python.org/issue13557#msg154174
For Python 3, a list comprehension defines a block pretty much like the method
definition during the class creation:
class x:
x = 1
def incx
Florent Xicluna added the comment:
Simpler test case:
class A:
x = 42
y = [x for _ in '1']
The semantics of list comprehension changed with Python 3.
However, I do not see this specific behavior documented somewhere.
http://docs.python.org/dev/whatsnew/3.0.html#chan
Florent Xicluna added the comment:
It seems the documentation is not enough accurate.
"Unlike the StringIO module, this module is not able to accept Unicode strings
that cannot be encoded as plain ASCII strings."
I understand that u'foo' can be encoded as plan ASCII,
New submission from Florent Xicluna :
pydoc fails on custom instances in specific cases. (When instance __name__ does
not resolve to a str).
This is a small example:
>>> import pydoc
>>> class A:
... def __getattr__(self, name):
... return True
...
>>> print(
Changes by Florent Xicluna :
--
components: +Windows
nosy: +loewis
___
Python tracker
<http://bugs.python.org/issue14608>
___
___
Python-bugs-list mailin
New submission from Florent Xicluna :
This is probably a bug.
>>> class A:
... def f(self, __a=42):
... pass
...
>>> A().f()
>>> class A:
... def f(self, *, __a=42):
... pass
...
>>> A().f()
Traceback (most recent call last):
File "&q
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue4600>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue12643>
___
___
Python-bugs-list mailing list
Unsubscribe:
Florent Xicluna added the comment:
If someone else is looking for the PyPI SSH support, it's there.
http://pypi.python.org/pypi/pypissh
(I did not find it mentioned in the tutorial)
Thanks Martin.
--
nosy: +flox
___
Python tracker
Florent Xicluna added the comment:
It breaks the compilation on few buildbots.
Python/import.c:130:14: error: #if with no expression
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue6
Changes by Florent Xicluna :
--
nosy: +flox
title: __dict__ = self in subclass of dict causes a memory leak? -> __dict__ =
self in subclass of dict causes a memory leak
___
Python tracker
<http://bugs.python.org/issue1
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue14208>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Florent Xicluna :
The links for the latest RC are broken on the official page.
http://www.python.org/download/
And the "release" page only list 3.2.3 rc1 and forget the other 3:
http://www.python.org/download/releases/
--
messages: 154762
nosy: flo
Changes by Florent Xicluna :
--
stage: -> patch review
versions: +Python 3.3
___
Python tracker
<http://bugs.python.org/issue14164>
___
___
Python-bugs-lis
Florent Xicluna added the comment:
FWIW, Fredrik, who is the creator of ElementTree, had a preference for JavaDoc
conventions, as explained here: http://bugs.python.org/issue6488#msg102087
They are compatible with the tool PythonDoc, authored by Fredrik too:
http://www.effbot.org/zone
Florent Xicluna added the comment:
Two other differences:
* the C TreeBuilder has an undocumented and unused method "xml"
* if you omit one of the TreeBuilder method (start(), end(), data(), close())
on you custom TreeBuilder implementation, the C XMLParser works fine, but t
Changes by Florent Xicluna :
--
assignee: ronaldoussoren ->
___
Python tracker
<http://bugs.python.org/issue14085>
___
___
Python-bugs-list mailing list
Un
Florent Xicluna added the comment:
Same on OSX, building trunk (3.3.0a0)
$ uname -v
Darwin Kernel Version 10.8.0: Tue Jun 7 16:32:41 PDT 2011;
root:xnu-1504.15.3~1/RELEASE_X86_64
$ gcc --version
i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3)
$ ./configure
Florent Xicluna added the comment:
This last feature (doctype handler on custom TreeBuilder) does not have tests...
So, it is certainly broken with the C implementation.
--
stage: needs patch -> test needed
___
Python tracker
&l
Florent Xicluna added the comment:
I understand the point about compatibility.
However it is slightly different here, because the method is already deprecated
in Python 2.7 and 3.2, with a warning in the documentation and a
DeprecationWarning at runtime.
This method was never available in the
Florent Xicluna added the comment:
the class versus factory issue is gone to issue 14128.
The current issue is only about the doctype() method missing in the C
implementation.
I propose to drop this deprecated method from the Python version, instead of
implementing the deprecated method in
Changes by Florent Xicluna :
--
nosy: +effbot
___
Python tracker
<http://bugs.python.org/issue14128>
___
___
Python-bugs-list mailing list
Unsubscribe:
Florent Xicluna added the comment:
I have updated the patch to a simpler form where I copy() sys.modules.
Strangely, I do not detect any refleak running the tests.
I plan to commit this fix, if we don't have leaks in the test suite.
--
resolution: -> duplicate
Added fi
Changes by Florent Xicluna :
Removed file: http://bugs.python.org/file24537/issue14035_fresh_modules.diff
___
Python tracker
<http://bugs.python.org/issue14035>
___
___
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue812369>
___
___
Python-bugs-list mailing list
Unsubscribe:
Florent Xicluna added the comment:
Keeping reference of fresh modules solves the issue.
--
keywords: +patch
stage: -> patch review
Added file: http://bugs.python.org/file24537/issue14035_fresh_modules.diff
___
Python tracker
&l
Florent Xicluna added the comment:
Trigger the same behavior without import_fresh_module. (test_fresh_import2.py)
If you uncomment line #A or #B, it succeed.
On the other side, if you comment line #C or #D, it succeed too.
The import machinery is a bit complex, indeed ...
--
nosy
Changes by Florent Xicluna :
--
nosy: +ezio.melotti
___
Python tracker
<http://bugs.python.org/issue14035>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Florent Xicluna :
While writing tests xml.etree, I hit a strange behaviour of import_fresh_module.
How to reproduce:
- dummy/__init__.py
- dummy/foo.py
- dummy/bar.py
- test_fresh_import.py
# 'dummy/foo.py'
from dummy.bar import func
# 'dummy/bar.py
Changes by Florent Xicluna :
--
resolution: -> duplicate
status: open -> closed
superseder: -> Unupdated source file in traceback
___
Python tracker
<http://bugs.python.or
Florent Xicluna added the comment:
For the doctype() issue, it might be removed, since it was already deprecated
in 3.2 (in compliance with PEP 387). However the deprecation cycle is under
discussion for the 3.x serie. (issue 13248)
For subclassing, you hit the same issue for all the
Changes by Florent Xicluna :
--
components: +XML
nosy: +flox
versions: +Python 3.3
___
Python tracker
<http://bugs.python.org/issue14001>
___
___
Python-bug
Florent Xicluna added the comment:
Now the merge is done. Thank you Eli for the effort, and to the other
contributors for the review.
Following topics may need further work:
- add a Deprecation warning for cElementTree? it will annoy the package
maintainers which support both 3.2 and
Florent Xicluna added the comment:
> from xml.etree.ElementTree import _namespace_map
>
> And the import in cElementTree won't be necessary.
> After all, _namespace_map is definitely not a public API!
Because of the interaction of the support.import_fresh_module with the
Cle
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue13997>
___
___
Python-bugs-list mailing list
Unsubscribe:
Florent Xicluna added the comment:
Updated patch:
- add 'XMLID' and 'register_namespace' to the ElementTree.__all__
- the comment says explicitly that cElementTree is deprecated
- exercise the deprecated module with the tests
--
Added file:
http://bugs.
Florent Xicluna added the comment:
There was a discussion in December which ruled out some CPython too specific
implementation details from the documentation.
http://mail.python.org/pipermail/python-dev/2011-December/115063.html
Maybe it's better to remove these 2 lines about the "t
Florent Xicluna added the comment:
I've pushed this first part, which is just a code refactoring.
I tried to work out a patch for the second part.
The tricky thing is because of xml.etree still using doctests.
The patch for the tests seems to be enough small and readable.
We have
Changes by Florent Xicluna :
Added file: http://bugs.python.org/file24485/issue13988_prepare_pep399_v2.diff
___
Python tracker
<http://bugs.python.org/issue13988>
___
___
Florent Xicluna added the comment:
Updated patch:
- fixed missing import and missing alias
- moved the XMLTreeBuilder alias to the Python module
--
___
Python tracker
<http://bugs.python.org/issue13
Florent Xicluna added the comment:
> Anyhow, I tried to apply it and a few tests in test_xml_etree_c fail,
> because it can't find fromstring and fromstringlist.
Ooops, I cut some redundancy after running the tests, and I forgot to re-add
the import. You're right.
> H
Florent Xicluna added the comment:
The first step is to strip out the cElementTree bootstrap code from the C
module.
I did it in the attached patch (plus removal of obsolete code for copy() in
Python 2.4).
This passes the unmodified tests "test_xml_etree" and "test_xml_etree_c&
Florent Xicluna added the comment:
> If possible I would avoid pyElementTree,
Me too:
- __name__ and __qualname__ would be less confusing
- the cElementTree accelerator uses large parts of Python implementation
> ElementTree is different - it's pretty much two separate impleme
Florent Xicluna added the comment:
Actuallly, the assertions were commented in the upstream repository.
https://bitbucket.org/effbot/et-2009-provolone/src/9e9e7f2710aa/elementtree/CHANGES#cl-46
> (1.3a6 released)
> - Removed most assert statements from the Element and ElementTree code
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue11108>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue7980>
___
___
Python-bugs-list mailing list
Unsubscribe:
Florent Xicluna added the comment:
The proposed solution is ok.
It sounds like unfinished documentation when you hit an "XXX".
For the "/dev/" documentation, it's OK, but for the released version, we should
avoid it.
--
Changes by Florent Xicluna :
--
nosy: +eric.araujo, tarek
versions: +Python 3.2, Python 3.3
___
Python tracker
<http://bugs.python.org/issue13716>
___
___
Pytho
New submission from Florent Xicluna :
http://docs.python.org/distutils/apiref.html?highlight=XXX#module-distutils.ccompiler
We find lots of "XXX" and "XXX see also." which give no information.
--
assignee: docs@python
components: Documentation
messages: 150683
nos
Changes by Florent Xicluna :
--
nosy: +belopolsky, flox, haypo
versions: +Python 3.3
___
Python tracker
<http://bugs.python.org/issue13674>
___
___
Python-bug
Florent Xicluna added the comment:
> Is mro_internal's second call to type_mro_modified still needed?
I was about to remove it, however I'm not enough confident on this.
I have to understand how "tp_mro" and "tp_bases" interact i
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue13555>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue13624>
___
___
Python-bugs-list mailing list
Unsubscribe:
Florent Xicluna added the comment:
Patch is ready for python 3.4
:-)
--
keywords: +patch
nosy: +flox
Added file: http://bugs.python.org/file23936/issue9856_python-3.4.diff
___
Python tracker
<http://bugs.python.org/issue9
Changes by Florent Xicluna :
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Florent Xicluna added the comment:
I removed object.__format__ from the patch because it is not planned for
removal in 3.3, but in 3.4 (see issue #9856).
I've fixed the documentation *versionchanged* and split the patch in two.
The first is less controversial.
The second might be dela
Changes by Florent Xicluna :
Removed file: http://bugs.python.org/file23905/issue13248_obsolescence.diff
___
Python tracker
<http://bugs.python.org/issue13248>
___
___
Changes by Florent Xicluna :
--
dependencies: -Change object.__format__(s) where s is non-empty to a TypeError
Added file: http://bugs.python.org/file23928/issue13248_argparse_io_lib2to3.diff
___
Python tracker
<http://bugs.python.org/issue13
Changes by Florent Xicluna :
--
dependencies: +Change object.__format__(s) where s is non-empty to a TypeError
___
Python tracker
<http://bugs.python.org/issue13
Florent Xicluna added the comment:
I know it won't be committed as-is, but this is the patch with most of the
deprecated things removed.
I skipped all the modules where a veto has been pronounced explicitly.
--
keywords: +patch
Added file: http://bugs.python.org/file
Florent Xicluna added the comment:
Off course the leftovers are mainly in comments and documentation.
See also issue #13574.
--
___
Python tracker
<http://bugs.python.org/issue13
New submission from Florent Xicluna :
there are still some leftovers of Python 2 old-style classes.
See attached patch.
--
components: Interpreter Core, Library (Lib)
files: oldstyle_leftovers.diff
keywords: patch
messages: 149188
nosy: flox
priority: low
severity: normal
stage: patch
Florent Xicluna added the comment:
Of course it's better to have someone else to review the patch.
However in this case, I'm not sure it is a major feature.
BTW, I noticed that effbot is currently marked as *inactive* maintainer
http://docs.python.org/devguide/experts.html#stdlib
If
New submission from Florent Xicluna :
The example uses PyInstanceObject which is Python 2 only (old-style classes).
http://docs.python.org/dev/extending/newtypes.html#weak-reference-support
--
assignee: docs@python
components: Documentation, Extension Modules
messages: 149183
nosy
Florent Xicluna added the comment:
Updated with documentation.
Thank you for the review.
I know this does not cover different namespaces in subtree.
But this use case seems very specific. The user could find other means to
achieve it.
--
stage: patch review -> commit review
Ad
Florent Xicluna added the comment:
thank you for this fix.
I agree a posteriori.
--
___
Python tracker
<http://bugs.python.org/issue11886>
___
___
Python-bug
Changes by Florent Xicluna :
--
components: +XML
___
Python tracker
<http://bugs.python.org/issue11379>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
nosy: +flox
type: -> performance
___
Python tracker
<http://bugs.python.org/issue11379>
___
___
Python-bugs-list mai
Florent Xicluna added the comment:
This explanation is enough. Thanks.
--
resolution: works for me -> invalid
stage: needs patch -> committed/rejected
status: pending -> closed
___
Python tracker
<http://bugs.python.or
New submission from Florent Xicluna :
http://docs.python.org/library/sys.html#sys.setrecursionlimit
http://docs.python.org/dev/library/sys.html#sys.setrecursionlimit
Doc for Python 2.7 says:
"A user may need to set the limit higher when she has ..."
Doc for Python 3.3 says:
"A u
Changes by Florent Xicluna :
--
status: pending -> closed
___
Python tracker
<http://bugs.python.org/issue13427>
___
___
Python-bugs-list mailing list
Unsubscri
Florent Xicluna added the comment:
collName is probably not what you expect.
You can print repr(collName), repr(currColl) to verify this.
It is not a bug on Python side.
--
nosy: +flox
resolution: -> works for me
stage: -> committed/rejected
status: open ->
Florent Xicluna added the comment:
this was implemented with ticket #13201.
It will be available in version 3.3.
--
nosy: +flox
resolution: -> out of date
stage: -> committed/rejected
status: open -> closed
superseder: -> Implement comparison operators for range
Changes by Florent Xicluna :
--
type: -> behavior
versions: +Python 3.3 -Python 2.6, Python 3.1
___
Python tracker
<http://bugs.python.org/issue8913>
___
_
Changes by Florent Xicluna :
--
priority: low -> normal
stage: -> patch review
___
Python tracker
<http://bugs.python.org/issue13126>
___
___
Python-bugs-
Changes by Florent Xicluna :
--
status: pending -> closed
___
Python tracker
<http://bugs.python.org/issue13309>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue9102>
___
___
Python-bugs-list mailing list
Unsubscribe:
Florent Xicluna added the comment:
Thank you Stefan for the comments.
I've added the prefix collision detection, and removed the **kw argument.
(+ tests)
--
Added file:
http://bugs.python.org/file23702/issue13378_non_global_namespaces_v2
Florent Xicluna added the comment:
With Darwin 10.8.0 x86_64, I confirm the behavior described in first message.
$ python2.7 -V
Python 2.7.2
$ python2.7 -i xx.py
22
22
>>>
TypeError: int() argument must be a string or a number, not 'Foo'
>>> '%d'
Changes by Florent Xicluna :
--
nosy: +flox, mark.dickinson
stage: -> needs patch
___
Python tracker
<http://bugs.python.org/issue13410>
___
___
Python-
Changes by Florent Xicluna :
--
components: +Windows
type: -> behavior
___
Python tracker
<http://bugs.python.org/issue13412>
___
___
Python-bugs-list mai
201 - 300 of 1386 matches
Mail list logo
