New submission from Andreas Stührk :
See http://docs.python.org/whatsnew/2.7.html#updated-module-elementtree-1-3
--
assignee: docs@python
components: Documentation
files: Element_iter_versionadded.patch
keywords: patch
messages: 145199
nosy: Trundle, docs@python
priority: normal
New submission from Andreas Stührk :
It's not possible (by intention) to instantiate a new instance of sys.flags.
This is achieved by setting the "tp_new" slot to NULL (in `_PySys_Init()`),
after `PyType_Ready()` is called, which means that a slot wrapper is added to
the ty
Changes by Andreas Stührk :
Added file: http://bugs.python.org/file23432/sys_flags__new__crash_2.7.patch
___
Python tracker
<http://bugs.python.org/issue13204>
___
___
Andreas Stührk added the comment:
It leaks because `PyException_GetTraceback()` already returns a new reference,
hence the "Py_XINCREF(tb)" is wrong.
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.o
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue13390>
___
___
Python-bugs-list mailing list
Unsubscribe:
Andreas Stührk added the comment:
As the test demonstrates, it's still possible to trigger a dynamic lookup
without the patch, hence I think this is still needed and valid, yes.
I updated the patch to make it reflect the latest committed changes.
--
Added file: http://bugs.pytho
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue12248>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue12265>
___
___
Python-bugs-list mailing list
Unsubscribe:
Andreas Stührk added the comment:
This issue tracker is for reporting issues about Python itself. Issues
concerning third-party projects should go to the respective issue tracker of
the project first (in this case https://bitbucket.org/bobf/bpython/issues).
This specific issue is caused by
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue2377>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue12149>
___
___
Python-bugs-list mailing list
Unsubscribe:
Andreas Stührk added the comment:
At least some of the remaining refleaks are caused by lib2to3. lib2to3 uses a
logger with the filename as logger name (see
`lib2to3.fixer_base.BaseFix.set_filename()`), but as the tests use a temporary
file with an arbitrary name, a new logger is created on
Andreas Stührk added the comment:
Attached is a patch that replaces `lib2to3.fixer_Base.BaseFix.set_filename()`
during tests. With the patch applied, I don't get any refleaks for packaging.
Another approach would be to simply remove the logging attribute of lib2to3
fixers, as it isn&#
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue12575>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue12555>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue10588>
___
___
Python-bugs-list mailing list
Unsubscribe:
Andreas Stührk added the comment:
Attached is a patch that removes the limit and that allows passing an arbitrary
number of positional and keyword arguments. Lacks tests for now.
--
keywords: +patch
nosy: +Trundle
Added file: http://bugs.python.org/file23089
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue12915>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Andreas Stührk :
There is some code in the inspect module that is now with the removal of tuple
unpacking in arguments in Python 3 no longer needed. The mentioned code does
not even work with Python 3 (because ``len(map(...))`` will raise a TypeError).
The attached patch
Changes by Andreas Stührk :
--
title: Dead code in pyk inspect module -> Dead code in py3k inspect module
___
Python tracker
<http://bugs.python.org/iss
Andreas Stührk added the comment:
The correct call is more something like
``inspect.formatargspec(*inspect.getargspec(f))``, which should work for all
(Python) functions in Python 3. In Python 2, tuple unpacking was represented
using a nested list for the arguments:
>>> def f
Andreas Stührk added the comment:
Actually, Python behaves the way you expect it. The problem is that when that
exception is created, Python tries to look up the involved class names. To do
that, it tries to get the "__class__" attribute (hapens in
`getinstclassname()`, which will
Andreas Stührk added the comment:
It's because you can fool `PyObject_IsInstance()` that way:
>>> class Spam(object):
... def __getattribute__(self, name):
... if name == '__class__':
... return str
... raise AttributeError
...
>>
Andreas Stührk added the comment:
At least two tests in `test.test_descr` consider that behaviour as a feature:
"test_isinst_isclass" and "test_proxy_super".
--
___
Python tracker
<http://bu
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue9732>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue9867>
___
___
Python-bugs-list mailing list
Unsubscribe:
Andreas Stührk added the comment:
The documentation about `getargvalues()` and the docstrings of `getargspec()`
and friends still mention nested lists for args. Should I update the patch or
should I create a new issue?
--
___
Python tracker
<h
New submission from Andreas Stührk :
Title says all, attached is a patch against trunk (2.7). I'm not familiar with
what version is correct for the Python 3 documentation.
--
assignee: d...@python
components: Documentation
files: stdtypes-memoryview-2.7.patch
keywords: patch
mes
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue10006>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue9369>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Andreas Stührk :
Title says all, attached is a patch against release27-maint that adds them.
--
assignee: d...@python
components: Documentation
files: future_builtins_docstring.patch
keywords: patch
messages: 118343
nosy: Trundle, d...@python
priority: normal
Andreas Stührk added the comment:
That behaviour is indeed caused by ncurses as it changes the buffer size of
stdio. The rationale behind that is explained in a comment in
ncurses/tinfo/setbuf.c
(http://codesearch.google.com/codesearch/p?hl=en#5KTrgOW2hXs/pub/nslu2/sources/ncurses-5.4.tar.gz
New submission from Andreas Stührk :
Some tests in test_rlcompleter make assumptions about the order of the list of
names that the completion methods of a Completer object return. That order is
not guaranteed and will break when running the tests under e.g. PyPy.
The attached patch against
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue5017>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue10174>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue1542677>
___
___
Python-bugs-list mailing list
Unsubscribe:
Andreas Stührk added the comment:
__builtin__ is the correct name for the module (see
http://docs.python.org/library/__builtin__.html, especially the note at the end
which is the cause of the confusion), hence this is not a bug.
--
nosy: +Trundle
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue10351>
___
___
Python-bugs-list mailing list
Unsubscribe:
Andreas Stührk added the comment:
Note that getkey() is broken, too. I attached a simple script to demonstrate
that. If you run it and enter some non-ascii input, you can see that getkey()
returns an utf-8 encoded str (in my utf-8 environment at least, I haven't check
if it's alway
New submission from Andreas Stührk :
Currently, if the parser's internal stack is full (as it happens when
the parser tries to parse a deeply nested structure), the parser
writes an error message to stderr and a bare MemoryError is
raised. That way, it is really hard for REPLs do handle
Changes by Andreas Stührk :
Added file: http://bugs.python.org/file20926/parser_nested_SyntaxError.patch
___
Python tracker
<http://bugs.python.org/issue11343>
___
___
Andreas Stührk added the comment:
Confirmed under Python 2.7, 3.2 and 3.3. Patch looks good to me. Attached is a
patch for 2.7.
--
nosy: +Trundle
Added file: http://bugs.python.org/file20927/issue11256_py27.patch
___
Python tracker
<h
Andreas Stührk added the comment:
It's because the _pickle module doesn't incref Pickler_Type and Unpickler_Type
before calling `PyModule_AddObject()` (which steals a reference).
The attached patch fixes the issue.
--
keywords: +patch
nosy: +Trundle
Added file: http://bugs.
Andreas Stührk added the comment:
@Éric: You should probably strip the colour from your diff :-)
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue11
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue4600>
___
___
Python-bugs-list mailing list
Unsubscribe:
Andreas Stührk added the comment:
That initial increase you can see happens because the module's dict is copied
in `_PyImport_FixupExtensionUnicode()`.
--
___
Python tracker
<http://bugs.python.org/is
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue11349>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue11406>
___
___
Python-bugs-list mailing list
Unsubscribe:
Andreas Stührk added the comment:
There are some issues with the patch:
- The check for size of `args` in `ImportError_init()` is wrong: You can't
create an `ImportError` with 3 arguments now ("TypeError: ImportError expected
2 arguments, got 3")
- `ImportError_clear()` doesn
Andreas Stührk added the comment:
This is a duplicate of issue #11272.
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue11434>
___
___
Python-bug
Andreas Stührk added the comment:
Looks good to me.
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue9651>
___
___
Python-bugs-list mailin
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue11470>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue11477>
___
___
Python-bugs-list mailing list
Unsubscribe:
Andreas Stührk added the comment:
Seems like like a case for "Bytes_kind" is missing in `set_context()`. Attached
is a patch, without a test though.
--
keywords: +patch
nosy: +Trundle
Added file: http://bugs.python.org/file21140/issue_1
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue11510>
___
___
Python-bugs-list mailing list
Unsubscribe:
Andreas Stührk added the comment:
The infinite recursion happens because `open` in tarfile is really
`TarFile.open` (see last line in the module). The builtin `open` is imported as
`_open`.
I also think that explicitly checking for "fileobj" being None is a cleaner
solution.
Andreas Stührk added the comment:
> I am sorry again for those mistakes, it's all completely new to me.
No worries!
>I have fixed those issues and created new patch. Using hg export, that now
>spans over two commits. Is it the way those patches should be provided, or
>sh
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue11549>
___
___
Python-bugs-list mailing list
Unsubscribe:
Andreas Stührk added the comment:
Any reason why the patch removes the `list()` calls? Without them, no parsing
happens at all.
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue11
Changes by Andreas Stührk :
Removed file: http://bugs.python.org/file21140/issue_11506.patch
___
Python tracker
<http://bugs.python.org/issue11506>
___
___
Python-bug
Andreas Stührk added the comment:
Added a test. Perhaps that should be done for other literals as well?
--
Added file: http://bugs.python.org/file21272/issue_11506.patch
___
Python tracker
<http://bugs.python.org/issue11
Andreas Stührk added the comment:
Confirmed under 3.2 and 2.7. The attached patch should fix the issue.
--
keywords: +patch
nosy: +Trundle
Added file: http://bugs.python.org/file21283/issue_11603.patch
___
Python tracker
<http://bugs.python.
Andreas Stührk added the comment:
On Sat, Mar 19, 2011 at 12:41 AM, Terry J. Reedy wrote:
> Whether or not this fixes issue ('should' is a bit vague, confirmation is
> needed) this seems like a good idea.
Yes, it fixes the issue. I wrote "should" because I was a bit
Changes by Andreas Stührk :
Removed file: http://bugs.python.org/file21283/issue_11603.patch
___
Python tracker
<http://bugs.python.org/issue11603>
___
___
Python-bug
Changes by Andreas Stührk :
Added file: http://bugs.python.org/file21300/issue_11603.patch
___
Python tracker
<http://bugs.python.org/issue11603>
___
___
Python-bug
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue10977>
___
___
Python-bugs-list mailing list
Unsubscribe:
Andreas Stührk added the comment:
That was changed in [a2213060d9dd], see issue #1414.
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue11
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue11627>
___
___
Python-bugs-list mailing list
Unsubscribe:
Andreas Stührk added the comment:
On Mon, Mar 21, 2011 at 10:27 PM, Santoso Wijaya wrote:
>
> Santoso Wijaya added the comment:
>
> Also, why is the print() in __new__ executed twice?
Because `PyErr_NormalizeException()` is called twice: First time when
the exceptions is raised
Andreas Stührk added the comment:
Attached is a patch. I'm not too happy about the error message though, I think
it's more confusing than helpful.
--
keywords: +patch
Added file: http://bugs.python.org/file21328/issue11627.patch
___
Pyth
Andreas Stührk added the comment:
> Antoine Pitrou added the comment:
> You could try something more explicit, such as
> "calling %s() should have returned an instance of BaseException, not %s"
> % (type, Py_TYPE(value))
Thanks, updated the patch.
> By the way, yo
Changes by Andreas Stührk :
Added file: http://bugs.python.org/file21329/issue11627_2.patch
___
Python tracker
<http://bugs.python.org/issue11627>
___
___
Python-bug
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue11393>
___
___
Python-bugs-list mailing list
Unsubscribe:
Andreas Stührk added the comment:
Thanks Nick, that is indeed much nicer. I updated the patch.
I also created a patch for 2.7, in case anyone thinks it's a good idea to fix
it there, too.
--
Added file: http://bugs.python.org/file21346/issue11627_3.
Changes by Andreas Stührk :
Added file: http://bugs.python.org/file21347/issue11627_py27.patch
___
Python tracker
<http://bugs.python.org/issue11627>
___
___
Python-bug
Andreas Stührk added the comment:
`input()` in Python 3 is the same as `raw_input()` in Python 2. It does not
evaluate the input as Python code.
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue11
Andreas Stührk added the comment:
This is a duplicate of issue #11272.
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue11642>
___
___
Python-bug
Andreas Stührk added the comment:
Another thing that can happen is that `__new__()` does return an instance of
BaseException, but that the return value is not an instance of the expected
class.
Example:
class MyException(OSError):
def __new__(*args):
return Exception()
try
Andreas Stührk added the comment:
On Fri, Mar 4, 2011 at 9:30 PM, Terry J. Reedy wrote:
> I agree with Martin (from 2000) that SyntaxError is not right either. Perhaps
> a new ParseError subclass thereof.
I added a new `ParserError` that inherits from `SyntaxError`.
> I presume REPL == read
Changes by Andreas Stührk :
Removed file: http://bugs.python.org/file20926/parser_nested_SyntaxError.patch
___
Python tracker
<http://bugs.python.org/issue11343>
___
___
Changes by Andreas Stührk :
Removed file: http://bugs.python.org/file20925/parser_nested_MemoryError.patch
___
Python tracker
<http://bugs.python.org/issue11343>
___
___
Andreas Stührk added the comment:
On Fri, Mar 25, 2011 at 5:52 PM, Éric Araujo wrote:
> Okay, it doesn’t work with -m __hello__, but using -c "import __hello__" I
> can see the message in all versions.
Can you elaborate on that? I.e. the versions and the actual message.
The
Andreas Stührk added the comment:
I really doubt that this issue has anything to do with `sys.excepthook` at all.
It's rather that module members are set to `None` during module cleanup.
Because the module raises an exception when one tries to import it, it will be
cleaned up immedi
Andreas Stührk added the comment:
The difference between 2.7 and 2.7.1 is issue #10068 (e2aa3b1d08bc).
--
___
Python tracker
<http://bugs.python.org/issue11
Andreas Stührk added the comment:
In my opinion, it is expected behaviour (but then, I'm not a core developer).
--
___
Python tracker
<http://bugs.python.org/is
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue11676>
___
___
Python-bugs-list mailing list
Unsubscribe:
Andreas Stührk added the comment:
The comment in the source that describes `Py_InspectFlag` also says
`SystemError` instead of `SystemExit`. I changed that and added the missing
:exc: for the SystemExit and created a patch for 3.1.
--
nosy: +Trundle
Added file: http://bugs.python.org
Changes by Andreas Stührk :
Added file: http://bugs.python.org/file21462/issue6498_31.patch
___
Python tracker
<http://bugs.python.org/issue6498>
___
___
Python-bug
Andreas Stührk added the comment:
That issue is already fixed in 2.7 and 3.x (by ae006386ec39). Also, it's a
duplicate of issue #2325, hence I think this one can be closed.
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/is
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue11770>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue11764>
___
___
Python-bugs-list mailing list
Unsubscribe:
Andreas Stührk added the comment:
Can you perhaps elaborate on the first part? I really can't see right now how a
class __dict__ can be something different from a dictionary. It's true that the
class dict can be any mapping while the class is being created, but that's
un
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue11796>
___
___
Python-bugs-list mailing list
Unsubscribe:
Andreas Stührk added the comment:
A first patch, misses any documentation changes. While working on it, I
realised that modules technically shadow the __dict__ attribute (because
modules use tp_dictoffset, hence module have a __dict__ member that points to
the instance dict). I updated
Changes by Andreas Stührk :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue1228112>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Andreas Stührk :
My patch for issue #11133 introduced a regression: it is no longer possible to
get attributes of modules. That is because modules use "tp_dictoffset" (at C
level). The instance __dict__ is exposed to Python code using a
types.MemberDescriptorType
Andreas Stührk added the comment:
See issue #11813 for the module problem.
--
___
Python tracker
<http://bugs.python.org/issue11770>
___
___
Python-bugs-list m
New submission from Andreas Stührk :
The recent addition of ABI flags broke the freeze tool as it doesn't construct
the paths to required files correctly any longer. The attached patch fixes the
issue for me, but I'm not too sure that I used the right config values.
--
New submission from Andreas Stührk :
The commit for issue #11133 omitted a part of the patch that checked whether
the __dict__ attribute of metaclasses are shadowed. That makes it possible to
trigger code execution in the case of metaclasses that have metaclasses.
Attached is a patch with a
Andreas Stührk added the comment:
Benjamin told me that "test_syntax" is the right place for the test and indeed,
there are quite some literals already tested.
--
nosy: +benjamin.peterson
Added file: http://bugs.python.org/file21637/issue_1150
1 - 100 of 141 matches
Mail list logo
