New submission from Ronny Pfannschmidt ronny.pfannschm...@gmail.com:
compile('def foo(', '', 'exec')
Traceback (most recent call last):
File stdin, line 1, in module
File , line 1
def foo(
^
SyntaxError: unexpected EOF while parsing
vs
compile('from __future__ import
New submission from Ronny Pfannschmidt ronny.pfannschm...@gmail.com:
the problem manifests when calling with negative counts
when the c versions are used, a empty list is returned,
however if the pure python version is called islice errors out
--
components: Library (Lib)
messages
Ronny Pfannschmidt ronny.pfannschm...@gmail.com added the comment:
however some basic consistency between the cpython and pure python versions
within the stdlib would be nice
since it basically implicitly breaks unaware code on non cpython
New submission from Ronny Pfannschmidt ronny.pfannschm...@gmail.com:
$ python3.2 -c 'import
ast;compile(ast.parse(open(testing/test_keymap.py).read()), test, exec)'
Traceback (most recent call last):
File string, line 1, in module
TypeError: AST string must be of type str
note that just
Changes by Ronny Pfannschmidt ronny.pfannschm...@gmail.com:
--
nosy: +benjamin.peterson
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13381
New submission from Ronny Pfannschmidt ronny.pfannschm...@gmail.com:
not sure if this is to be considered a bug,
but python3.2 tries to flush sys.stdout on shutdown, even if its closed
$ python3.2 -c 'import sys;sys.stdout.close()'
Exception ValueError: 'I/O operation on closed file
Ronny Pfannschmidt ronny.pfannschm...@gmail.com added the comment:
i think checking for closed is the correct solution
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13444
New submission from Ronny Pfannschmidt:
the change to conform with pep 3114 makes socketSocketIO hide Timeouts,
since they are also denoted with EAGAIN (which is one of the blocking errors a
nonblocking socket will raise)
that causes read/readinto return None, when one would expect a Timeout
Ronny Pfannschmidt added the comment:
noticed an error in my testing, sorry for the noise
--
resolution: - invalid
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17039
New submission from Ronny Pfannschmidt:
examples that are found on a property dont detect the line number
class example(object):
@property
def me(self):
1/0
pass
--
messages: 184384
nosy: Ronny.Pfannschmidt
priority: normal
severity: normal
status: open
title
New submission from Ronny Pfannschmidt ronny.pfannschm...@gmail.com:
this patch simplifies and cleans up the resolve_name function
--
assignee: eric.araujo
components: Distutils2
files: resolve_name.patch
keywords: patch
messages: 161974
nosy: Ronny.Pfannschmidt, alexis, eric.araujo
Ronny Pfannschmidt ronny.pfannschm...@gmail.com added the comment:
my change is a unrelated cleanup
but the ideas in the patch look good
the attribute error addition seems relevant
i'll adapt my patch to raise the original import error for toplevel import
failure and accumuplate the attrbute
New submission from Ronny Pfannschmidt ronny.pfannschm...@gmail.com:
due to the lack of a marker that denotes where the module ends and the
attribute starts, unrelated import errors can break the tryerror chain at
unexpected places and the code can pass on to the recursive getattr chain
Ronny Pfannschmidt ronny.pfannschm...@gmail.com added the comment:
to correctly implement it we need the : separator back
with the separator the import specification is no longer ambigious,
and we can use one exact import, and an error will always be an error
Ronny Pfannschmidt ronny.pfannschm...@gmail.com added the comment:
an example of creating a wrong error would be something like the following:
there is a package foo.bar, which does a wrong import in __init__.py
we want to resolve the name foo.bar.something
we'd get the error that foo has
Ronny Pfannschmidt ronny.pfannschm...@gmail.com added the comment:
updated the patch with more detailed errors
--
Added file: http://bugs.python.org/file25771/resolve_name.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Ronny Pfannschmidt ronny.pfannschm...@gmail.com added the comment:
i missused hg export, here is a corrected patch
--
Added file: http://bugs.python.org/file25773/resolve_name.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
New submission from Ronny Pfannschmidt ronny.pfannschm...@gmail.com:
thats broken for assigning overlaping regions, the memcpy docs explicitly state
that memmove should be used in overlap cases
--
messages: 165127
nosy: Ronny.Pfannschmidt
priority: normal
severity: normal
status: open
Ronny Pfannschmidt ronny.pfannschm...@gmail.com added the comment:
im unlikely to find the time to try and fix pickle/cpickle myself in the next
few months
--
nosy: +Ronny.Pfannschmidt
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
New submission from Ronny Pfannschmidt ronny.pfannschm...@gmail.com:
behaviour:
name = 'woo\raa'
open(name, 'w')
aa', mode 'w' at 0x295a8a0
expected:
name = 'woo\raa'
open(name, 'w')
open file 'woo\raa', mode 'w' at 0x295a8a0
note:
don't ask why i tried this chunk of code in the first
Ronny Pfannschmidt added the comment:
wtf? you made it possible to return NULL in some case
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14161
Ronny Pfannschmidt added the comment:
sorry for the buzz, i got myself up to date on the c api now
why is there still the unicode case?
the PyObject_Repr variant should work fine in both cases
--
___
Python tracker rep...@bugs.python.org
http
New submission from Ronny Pfannschmidt:
this means its much harder to have a mixin to change the behaviour of a property
instead of super(Mixin, self).prop = foo
the code is super(Mixin, type(self)).prop.__set__(self, foo)
which is way harder to understand
the attached file demonstrates
Changes by Ronny Pfannschmidt ronny.pfannschm...@gmail.com:
--
nosy: +Ronny.Pfannschmidt
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14965
New submission from Ronny Pfannschmidt:
got:
l = {}
import inspect
exec(compile('def fun(): pass', '', 'exec'), l, l)
inspect.getsource(l['fun'])
Traceback (most recent call last):
File input, line 1, in module
File /home/private/.local/lib/python3.3/inspect.py, line 726, in getsource
Changes by Ronny Pfannschmidt ronny.pfannschm...@gmail.com:
--
components: +Library (Lib)
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19658
New submission from Ronny Pfannschmidt:
when using virtual tables, dumpiter generates a broken db script
virtual table entries must be created as master table entries
the sqlite tools dump does that correctly
however pythons iterdump seems to do that rather different and wrong
sqlite3 test.db
Changes by Ronny Pfannschmidt ronny.pfannschm...@gmail.com:
--
components: +Extension Modules
type: - behavior
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20463
Ronny Pfannschmidt added the comment:
could we please get the option to opt-out of that behaviour, as a extra
connection option maybe
with the normal python sqlite bindings its impossible
to have database migrations work safely
which IMHO makes this a potential data-loss issue
--
nosy
Ronny Pfannschmidt added the comment:
the sqlite binding deciding how to handle transactions
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10740
Ronny Pfannschmidt added the comment:
http://hg.python.org/releasing/3.4/file/447c758cdc26/Modules/_sqlite/cursor.c#l789
also i dont see the isolation level being taking into account in other parts of
the code
--
___
Python tracker rep
Ronny Pfannschmidt added the comment:
indeed it is, thanks for the reference i searched only for match and missed the
glob
--
resolution: -> duplicate
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bug
Ronny Pfannschmidt added the comment:
issue34731 was a duplicate of this
pytest was affected, as we port more bits to pathlib we hit this as well
bruno kindly implemented a local workaround in
https://github.com/pytest-dev/pytest/pull/3980/files#diff-63fc5ed688925b327a5af20405bf4b09R19
New submission from Ronny Pfannschmidt :
when porting parts of pytest to pathlib we noted that `path.match` does not
quite match normal fnmatch for usages of `**`
i believe this is related to always splitting the patter completely and not
handling `**` in that case
Bruno wrote
https
New submission from Ronny Pfannschmidt :
due to
```
def __iter__(self):
"""
Supply iter so one may construct dicts of EntryPoints easily.
"""
return iter((self.name, self))
```
the default namedtuple asdict method is broken
i
Ronny Pfannschmidt added the comment:
im on the noisy list because i faced this first in 2012
a key problem where i ran into this was mixins, - depending on whether a mixin
was added or not one would get errors or not
from my pov a super object should look like the "next class
36 matches
Mail list logo
