Changes by Trundle :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue2889>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.pyth
Changes by Trundle :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue1748064>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Trundle :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue8828>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.pyth
Trundle added the comment:
This was changed due to issue #4050.
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue8720>
___
___
Python-bugs-list m
Trundle added the comment:
`fill_file_fields()` does not open the fp, the caller of `PyFile_FromFile()`
opens the fp.
I don't have a better idea, that's why I don't have provided a patch.
--
___
Python tracker
<http://bugs.py
Trundle added the comment:
Note that the fp gets set with `fill_file_fields()` and that is called after
the error return of `PyString_FromString()`. Hence, the fp is left open if
`PyString_FromString()` returns NULL.
--
___
Python tracker
<h
New submission from Trundle :
Create a directory "__init__.py" and execute
>>> import imp
>>> imp.find_module('__init__', ['.'])
to reproduce that issue. It will crash because Python tries to double-close a
file pointer: `call_find_module` wi
Trundle added the comment:
What Joe Amenta stumbled across is that ABCMeta caches its subclass
checks. If you call ``isinstance(spam, Callable)`` and after that delete
`type(spam).__call__`, every other call of ``isinstance(spam, Callable)``
will still return True
Changes by Trundle :
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue5911>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.pyth
Trundle added the comment:
Crashes reliable with a segfault in Python 3.1.1.
Fixing the setter so that one can only set strings and not arbitrary
objects is possibly the best solution.
--
nosy: +Trundle
versions: +Python 3.1
___
Python tracker
New submission from Trundle :
The original lines in Lib/codeop.py under Python 2.6:
raise SyntaxError, err1
Those lines were ported to Python 3 as:
raise SyntaxError(err1)
Which is wrong because `err1` is in both cases an instance of
`SyntaxError`. Quote from the language reference: "I
Trundle added the comment:
You are using `CFUNCTYPE` wrong. `CFUNCTYPE` returns a type which will
take a *Python function* (or an address of a function as integer). You
provide `lib.get_message` as Python function, which is a wrapper object
for the C function. By default, ctypes assumes an
Trundle added the comment:
This is defined behaviour and no bug at all. Special methods are looked
up in the type for new-style classes and not in the instance. Try
changing ``self.__iter__=self.__str__`` to ``test1.__iter__ =
self.__str__`` in your example (which will then raise a TypeError on
Trundle added the comment:
As every type is an instance of `type`, every type also has a
`__call__` attribute which means ``hasattr(type(x), '__call__')`` is
always true. `callable()` checks whether `tp_call` is set on the type,
which cannot be done in Python directly.
-
Trundle added the comment:
See also issue #1699259.
--
nosy: +Trundle
___
Python tracker
<http://bugs.python.org/issue6952>
___
___
Python-bugs-list mailin
Trundle added the comment:
Of course it works for you. As you stated in issue #4787, your locale
is 'fr_FR.UTF-8'.
And I don't want Python to guess my terminal's encoding. I want Python
to respect my locale. Which is 'd
Trundle added the comment:
Yes, it uses a version of ncurses which supports wide characters, I
checked that.
I agree that using bytes instead may not be the preferred solution in
Python 3. The point is, currently, it is broken if the user does not
use an utf-8 environment
Changes by Trundle :
Added file: http://bugs.python.org/file14751/umlaut3x.py
___
Python tracker
<http://bugs.python.org/issue6745>
___
___
Python-bugs-list mailin
New submission from Trundle :
In Python 3, curses requires a str for addstr() where I think it should
take bytes instead. Otherwise it is impossible to output anything other
than ASCII (which is even more or less stated on top of curses'
documentation).
See the attached script "umlaut
New submission from Trundle :
Snippet to reproduce:
import curses
scr = curses.initscr()
curses.ungetch(1025)
scr.getkey()
This is because `keyname()` in `PyCursesWindow_GetKey()` returns NULL
which is passed to `PyString_FromString()` then.
The attached patch fixes the segfault
New submission from Trundle :
There is a small markup error in the description of Completer objects.
The attached patch fixes this.
--
assignee: georg.brandl
components: Documentation
files: rlcompleter_doc_markup.patch
keywords: patch
messages: 88551
nosy: Trundle, georg.brandl
Trundle added the comment:
See also issue #1694663.
--
___
Python tracker
<http://bugs.python.org/issue5322>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Trundle :
--
nosy: +gvanrossum
___
Python tracker
<http://bugs.python.org/issue5322>
___
___
Python-bugs-list mailing list
Unsubscribe:
Trundle added the comment:
The problem is that `type_setattro()` sets the new "__new__" attribute
in the type's dict (through `PyObject_GenericSetAttr()`), but the
corresponding slot will never be updated if the new "__new__" is a
PyCFunction.
The affected code in `upd
Trundle added the comment:
I think the real problem here is `update_one_slot` and not `object_new`. It
is impossible to set "__new__" to a PyCFunction inside Python code, which
may be a feature, but is in fact very irritating.
For example the following snippet:
>>> class
Trundle added the comment:
Is the fix really correct? The documentation clearly states about
`sys.last_type`: "These three variables are not always defined; they are set
when an exception is not handled and the interpreter prints an error
message and a stack traceback." And there
26 matches
Mail list logo
