[Python-announce] pytest 7.2.0 released
pytest-7.2.0 == The pytest team is proud to announce the 7.2.0 release! This release contains new features, improvements, and bug fixes, the full list of changes is available in the changelog: https://docs.pytest.org/en/stable/changelog.html For complete documentation, please visit: https://docs.pytest.org/en/stable/ As usual, you can upgrade from PyPI via: pip install -U pytest Thanks to all of the contributors to this release: * Aaron Berdy * Adam Turner * Albert Villanova del Moral * Alice Purcell * Anthony Sottile * Anton Yakutovich * Babak Keyvani * Brandon Chinn * Bruno Oliveira * Chanvin Xiao * Cheuk Ting Ho * Chris Wheeler * EmptyRabbit * Ezio Melotti * Florian Best * Florian Bruhin * Fredrik Berndtsson * Gabriel Landau * Gergely Kalmár * Hugo van Kemenade * James Gerity * John Litborn * Jon Parise * Kevin C * Kian Eliasi * MatthewFlamm * Miro Hrončok * Nate Meyvis * Neil Girdhar * Nhieuvu1802 * Nipunn Koorapati * Ofek Lev * Paul Müller * Paul Reece * Pax * Pete Baughman * Peyman Salehi * Philipp A * Ran Benita * Robert O'Shea * Ronny Pfannschmidt * Rowin * Ruth Comer * Samuel Colvin * Samuel Gaist * Sandro Tosi * Shantanu * Simon K * Stephen Rosen * Sviatoslav Sydorenko * Tatiana Ovary * Thierry Moisan * Thomas Grainger * Tim Hoffmann * Tobias Diez * Tony Narlock * Vivaan Verma * Wolfremium * Zac Hatfield-Dodds * Zach OBrien * aizpurua23a * gresm * holesch * itxasos23 * johnkangw * skhomuti * sommersoft * wodny * zx.qiu Happy testing, The pytest Development Team ___ Python-announce-list mailing list -- python-announce-list@python.org To unsubscribe send an email to python-announce-list-le...@python.org https://mail.python.org/mailman3/lists/python-announce-list.python.org/ Member address: arch...@mail-archive.com
[issue14965] super() and property inheritance behavior
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" so properties of the next base should behave as such, special methods as well -- ___ Python tracker <https://bugs.python.org/issue14965> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue44893] importlib.metadata Entrypoint has a broken _asdict
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
instead of returning the fields, recursive objects are returned as
```
(Pdb) v
EntryPoint(name='.git', value='setuptools_scm.git:parse',
group='setuptools_scm.parse_scm')
(Pdb) v._asdict()
{'name': '.git', 'value': EntryPoint(name='.git',
value='setuptools_scm.git:parse', group='setuptools_scm.parse_scm')}
(Pdb) type(v)
(Pdb)
--
components: Library (Lib)
messages: 399419
nosy: Ronny.Pfannschmidt
priority: normal
severity: normal
status: open
title: importlib.metadata Entrypoint has a broken _asdict
type: behavior
versions: Python 3.10, Python 3.11, Python 3.8, Python 3.9
___
Python tracker
<https://bugs.python.org/issue44893>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29249] Pathlib glob ** 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 -- nosy: +Ronny.Pfannschmidt ___ Python tracker <https://bugs.python.org/issue29249> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34731] pathlib path.match misshandles multiple `**`
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://bugs.python.org/issue34731> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34731] pathlib path.match misshandles multiple `**`
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://github.com/pytest-dev/pytest/pull/3980/files#diff-63fc5ed688925b327a5af20405bf4b09R19 as a workaround -- components: Library (Lib) messages: 325701 nosy: Ronny.Pfannschmidt priority: normal severity: normal status: open title: pathlib path.match misshandles multiple `**` ___ Python tracker <https://bugs.python.org/issue34731> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
py.test 2.9.2 released
pytest-2.9.2
pytest is a mature Python testing tool with more than a 1100 tests
against itself, passing on many different interpreters and platforms.
See below for the changes and see docs at:
http://pytest.org
As usual, you can upgrade from pypi via::
pip install -U pytest
Thanks to all who contributed to this release, among them:
Adam Chainz
Benjamin Dopplinger
Bruno Oliveira
Florian Bruhin
John Towler
Martin Prusse
Meng Jue
MengJueM
Omar Kohl
Quentin Pradet
Ronny Pfannschmidt
Thomas Güttler
TomV
Tyler Goodlet
Happy testing,
The py.test Development Team
2.9.2 (compared to 2.9.1)
---
**Bug Fixes**
* fix `#510`_: skip tests where one parameterize dimension was empty
thanks Alex Stapleton for the Report and `@RonnyPfannschmidt`_ for the PR
* Fix Xfail does not work with condition keyword argument.
Thanks `@astraw38`_ for reporting the issue (`#1496`_) and `@tomviner`_
for PR the (`#1524`_).
* Fix win32 path issue when puttinging custom config file with absolute path
in ``pytest.main("-c your_absolute_path")``.
* Fix maximum recursion depth detection when raised error class is not aware
of unicode/encoded bytes.
Thanks `@prusse-martin`_ for the PR (`#1506`_).
* Fix ``pytest.mark.skip`` mark when used in strict mode.
Thanks `@pquentin`_ for the PR and `@RonnyPfannschmidt`_ for
showing how to fix the bug.
* Minor improvements and fixes to the documentation.
Thanks `@omarkohl`_ for the PR.
* Fix ``--fixtures`` to show all fixture definitions as opposed to just
one per fixture name.
Thanks to `@hackebrot`_ for the PR.
.. _#510: https://github.com/pytest-dev/pytest/issues/510
.. _#1506: https://github.com/pytest-dev/pytest/pull/1506
.. _#1496: https://github.com/pytest-dev/pytest/issue/1496
.. _#1524: https://github.com/pytest-dev/pytest/issue/1524
.. _@prusse-martin: https://github.com/prusse-martin
.. _@astraw38: https://github.com/astraw38
--
https://mail.python.org/mailman/listinfo/python-announce-list
Support the Python Software Foundation:
http://www.python.org/psf/donations/
py.test 2.9.2 released
pytest-2.9.2
pytest is a mature Python testing tool with more than a 1100 tests
against itself, passing on many different interpreters and platforms.
See below for the changes and see docs at:
http://pytest.org
As usual, you can upgrade from pypi via::
pip install -U pytest
Thanks to all who contributed to this release, among them:
Adam Chainz
Benjamin Dopplinger
Bruno Oliveira
Florian Bruhin
John Towler
Martin Prusse
Meng Jue
MengJueM
Omar Kohl
Quentin Pradet
Ronny Pfannschmidt
Thomas Güttler
TomV
Tyler Goodlet
Happy testing,
The py.test Development Team
2.9.2 (compared to 2.9.1)
---
**Bug Fixes**
* fix `#510`_: skip tests where one parameterize dimension was empty
thanks Alex Stapleton for the Report and `@RonnyPfannschmidt`_ for the PR
* Fix Xfail does not work with condition keyword argument.
Thanks `@astraw38`_ for reporting the issue (`#1496`_) and `@tomviner`_
for PR the (`#1524`_).
* Fix win32 path issue when puttinging custom config file with absolute path
in ``pytest.main("-c your_absolute_path")``.
* Fix maximum recursion depth detection when raised error class is not aware
of unicode/encoded bytes.
Thanks `@prusse-martin`_ for the PR (`#1506`_).
* Fix ``pytest.mark.skip`` mark when used in strict mode.
Thanks `@pquentin`_ for the PR and `@RonnyPfannschmidt`_ for
showing how to fix the bug.
* Minor improvements and fixes to the documentation.
Thanks `@omarkohl`_ for the PR.
* Fix ``--fixtures`` to show all fixture definitions as opposed to just
one per fixture name.
Thanks to `@hackebrot`_ for the PR.
.. _#510: https://github.com/pytest-dev/pytest/issues/510
.. _#1506: https://github.com/pytest-dev/pytest/pull/1506
.. _#1496: https://github.com/pytest-dev/pytest/issue/1496
.. _#1524: https://github.com/pytest-dev/pytest/issue/1524
.. _@prusse-martin: https://github.com/prusse-martin
.. _@astraw38: https://github.com/astraw38
--
https://mail.python.org/mailman/listinfo/python-announce-list
Support the Python Software Foundation:
http://www.python.org/psf/donations/
Pytest 2.8.7 - a hotfix release
pytest-2.8.7 This is a hotfix release to solve a regression in the builtin monkeypatch plugin that got introduced in 2.8.6. pytest is a mature Python testing tool with more than a 1100 tests against itself, passing on many different interpreters and platforms. This release is supposed to be drop-in compatible to 2.8.5. See below for the changes and see docs at: http://pytest.org As usual, you can upgrade from pypi via:: pip install -U pytest Thanks to all who contributed to this release, among them: Ronny Pfannschmidt Happy testing, The py.test Development Team 2.8.7 (compared to 2.8.6) - - fix #1338: use predictable object resolution for monkeypatch -- https://mail.python.org/mailman/listinfo/python-announce-list Support the Python Software Foundation: http://www.python.org/psf/donations/
pytest 2.8.4 was released :)
pytest-2.8.4 pytest is a mature Python testing tool with more than a 1100 tests against itself, passing on many different interpreters and platforms. This release is supposed to be drop-in compatible to 2.8.2. See below for the changes and see docs at: http://pytest.org As usual, you can upgrade from pypi via:: pip install -U pytest Thanks to all who contributed to this release, among them: Bruno Oliveira Florian Bruhin Jeff Widman Mehdy Khoshnoody Nicholas Chammas Ronny Pfannschmidt Tim Chan Happy testing, The py.test Development Team 2.8.4 (compared to 2.8.3) - - fix #1190: ``deprecated_call()`` now works when the deprecated function has been already called by another test in the same module. Thanks Mikhail Chernykh for the report and Bruno Oliveira for the PR. - fix #1198: ``--pastebin`` option now works on Python 3. Thanks Mehdy Khoshnoody for the PR. - fix #1219: ``--pastebin`` now works correctly when captured output contains non-ascii characters. Thanks Bruno Oliveira for the PR. - fix #1204: another error when collecting with a nasty __getattr__(). Thanks Florian Bruhin for the PR. - fix the summary printed when no tests did run. Thanks Florian Bruhin for the PR. - a number of documentation modernizations wrt good practices. Thanks Bruno Oliveira for the PR. -- https://mail.python.org/mailman/listinfo/python-announce-list Support the Python Software Foundation: http://www.python.org/psf/donations/
apipkg 1.3 released
Hello,
i pleased to annouce the release of apipkg 1.3.
Welcome to apipkg!
With apipkg you can control the exported namespace of a
python package and greatly reduce the number of imports for your users.
It is a `small pure python module`_ that works on virtually all Python
versions, including CPython2.3 to Python3.1, Jython and PyPy. It
co-operates
well with Python's ``help()`` system, custom importers (PEP302) and common
command line completion tools.
Usage is very simple: you can require 'apipkg' as a dependency or you
can copy paste the 200 Lines of code into your project.
As extra it will automatically set package.__version__
to your distribution version.
Tutorial example
---
Here is a simple ``mypkg`` package that specifies one namespace
and exports two objects imported from different modules::
# mypkg/__init__.py
import apipkg
apipkg.initpkg(__name__, {
'path': {
'Class1': _mypkg.somemodule:Class1,
'clsattr': _mypkg.othermodule:Class2.attr,
}
}
The package is initialized with a dictionary as namespace.
You need to create a ``_mypkg`` package with a ``somemodule.py``
and ``othermodule.py`` containing the respective classes.
The ``_mypkg`` is not special - it's a completely
regular python package.
Namespace dictionaries contain ``name: value`` mappings
where the value may be another namespace dictionary or
a string specifying an import location. On accessing
an namespace attribute an import will be performed::
import mypkg
mypkg.path
ApiModule 'mypkg.path'
mypkg.path.Class1 # '_mypkg.somemodule' gets imported now
class _mypkg.somemodule.Class1 at 0xb7d428fc
mypkg.path.clsattr # '_mypkg.othermodule' gets imported now
4 # the value of _mypkg.othermodule.Class2.attr
The ``mypkg.path`` namespace and its two entries are
loaded when they are accessed. This means:
* lazy loading - only what is actually needed is ever loaded
* only the root mypkg ever needs to be imported to get
access to the complete functionality.
* the underlying modules are also accessible, for example::
from mypkg.sub import Class1
Including apipkg in your package
--
If you don't want to add an ``apipkg`` dependency to your package you
can copy the `apipkg.py`_ file somewhere to your own package,
for example ``_mypkg/apipkg.py`` in the above example. You
then import the ``initpkg`` function from that new place and
are good to go.
.. _`small pure python module`:
.. _`apipkg.py`: http://bitbucket.org/hpk42/apipkg/src/tip/apipkg.py
Feedback?
---
If you have questions you are welcome to
* join the #pylib channel on irc.freenode.net
* subscribe to the http://codespeak.net/mailman/listinfo/py-dev list.
* create an issue on http://bitbucket.org/hpk42/apipkg/issues
1.3
- fix issue2 - adapt tests on Jython
- handle jython __pkgpath__ missabstraction when running python from jar
files
- alias modules pointing to unimportable modules will return None for
all their attributes instead of raising ImportError. This addresses
python3.4 where any call to getframeinfo() can choke on sys.modules
contents if pytest is not installed (because py.test.* imports it).
- introduce apipkg.distribution_version(name) as helper to
obtain the current version number of a package from install metadata
its used by default with the package name
- add an eagerloading option and eagerload automatically
if bpython is used (workaround for their monkeypatching)
-- Ronny
--
https://mail.python.org/mailman/listinfo/python-announce-list
Support the Python Software Foundation:
http://www.python.org/psf/donations/
[ANN] Execnet 1.3.0 released
Hello, is my pleasure to announce the release of execnet 1.3.0 availiable at https://pypi.python.org/pypi/execnet/1.3.0 -- Ronny PS: execnet: distributed Python deployment and communication .. _execnet: http://codespeak.net/execnet execnet_ provides carefully tested means to ad-hoc interact with Python interpreters across version, platform and network barriers. It provides a minimal and fast API targetting the following uses: * distribute tasks to local or remote processes * write and deploy hybrid multi-process applications * write scripts to administer multiple hosts Features -- * zero-install bootstrapping: no remote installation required! * flexible communication: send/receive as well as callback/queue mechanisms supported * simple serialization of python builtin types (no pickling) * grouped creation and robust termination of processes * well tested between CPython 2.6-3.X, Jython 2.5.1 and PyPy 2.2 interpreters. * interoperable between Windows and Unix-ish systems. * integrates with different threading models, including standard os threads, eventlet and gevent based systems. Changelog === 1.3.0 - fix issue33: index.txt to correctly mention MIT instead of GPL. - fix issue35: adapt some doctests, fix some channel tests for py3. - use subprocess32 when available for python 3. - try to be a bit more careful when interpreter is shutting down to avoid random exceptions, thanks Alfredo Deza. - ignore errors on orphan file removal when rsyncing - fix issue34: limit use of import based bootstrap 1.2 - fix issue22 -- during interpreter shutdown don't throw an exception when we can't send a termination sequence anymore as we are about to die anyway. - fix issue24 -- allow concurrent creation of gateways by guarding automatic id creation by a look. Thanks tlecomte. - majorly refactor internal thread and IO handling. execnet can now operate on different thread models, defaults to thread but allows for eventlet and gevent if it is installed. - gateway.remote_exec() will now execute in multiple threads on the other side by default. The previous neccessity of running gateway.remote_init_threads() to allow for such concurrency is gone. The latter method is now a no-op and will be removed in future versions of execnet. - fix issue20: prevent AttributError at interpreter shutdown by not trying to send close/last_message messages if the world around is half destroyed. - fix issue21: allow to create local gateways with sudo aka makegateway(popen//python=sudo python). Thanks Alfredo Deza for the PR. - streamline gateway termination and simplify proxy implementation. add more internal tracing. - if execution hangs in computation, we now try to send a SIGINT to ourselves on Unix platforms instead of just calling thread.interrupt_main() - change license from GPL to MIT - introduce execnet.dump/load variants of dumps/loads serializing/unserializing mechanism. - improve channel.receive() communication latency on python2 by changing the default timeout of the underlying Queue.get to a regular None instead of the previous default -1 which caused an internal positive timeout value (a hack probably introduced to allow CTRL-C to pass through for python2.5 versions). - extended ssh-syntax to allow passing of command line args, e.g. ssh= -p 50 hostname. The options are passed to the underlying ssh client binary. Thanks tundish. - fix issue15: interoperability with inspect.getstack(). Thanks Peter Feiner. - fix issue10 : skip PYTHONDONTWRITEBYTECODE test if it we are running with PYTHONDONTWRITEBYTECODE set. - dont try the jython pid fixup on a RemoteIO - avoid accidentally setting exc_info() in gateway_base.py -- https://mail.python.org/mailman/listinfo/python-announce-list Support the Python Software Foundation: http://www.python.org/psf/donations/
[issue10740] sqlite3 module breaks transactions and potentially corrupts data
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 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10740 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10740] sqlite3 module breaks transactions and potentially corrupts data
Ronny Pfannschmidt added the comment: the sqlite binding deciding how to handle transactions -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10740 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10740] sqlite3 module breaks transactions and potentially corrupts data
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...@bugs.python.org http://bugs.python.org/issue10740 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20463] sqlite dumpiter dumps invalid script when virtual tables are used
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 create virtual table test using fts4(example);
---
sqlite dump
PRAGMA foreign_keys=OFF;
BEGIN TRANSACTION;
PRAGMA writable_schema=ON;
INSERT INTO
sqlite_master(type,name,tbl_name,rootpage,sql)VALUES('table','test','test',0,'CREATE
VIRTUAL TABLE test using fts4(example)');
CREATE TABLE 'test_content'(docid INTEGER PRIMARY KEY, 'c0example');
CREATE TABLE 'test_segments'(blockid INTEGER PRIMARY KEY, block BLOB);
CREATE TABLE 'test_segdir'(level INTEGER,idx INTEGER,start_block
INTEGER,leaves_end_block INTEGER,end_block INTEGER,root BLOB,PRIMARY KEY(level,
idx));
CREATE TABLE 'test_docsize'(docid INTEGER PRIMARY KEY, size BLOB);
CREATE TABLE 'test_stat'(id INTEGER PRIMARY KEY, value BLOB);
PRAGMA writable_schema=OFF;
COMMIT;
--
python iterdump import sqlite3;
c=sqlite3.connect(test.db);
print(\n.join(c.iterdump()))
BEGIN TRANSACTION;
CREATE VIRTUAL TABLE test using fts4(example);
CREATE TABLE 'test_content'(docid INTEGER PRIMARY KEY, 'c0example');
CREATE TABLE 'test_docsize'(docid INTEGER PRIMARY KEY, size BLOB);
CREATE TABLE 'test_segdir'(level INTEGER,idx INTEGER,start_block
INTEGER,leaves_end_block INTEGER,end_block INTEGER,root BLOB,PRIMARY KEY(level,
idx));
CREATE TABLE 'test_segments'(blockid INTEGER PRIMARY KEY, block BLOB);
CREATE TABLE 'test_stat'(id INTEGER PRIMARY KEY, value BLOB);
COMMIT;
--
messages: 209825
nosy: Ronny.Pfannschmidt
priority: normal
severity: normal
status: open
title: sqlite dumpiter dumps invalid script when virtual tables are used
versions: Python 2.7
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20463
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20463] sqlite dumpiter dumps invalid script when virtual tables are used
Changes by Ronny Pfannschmidt ronny.pfannschm...@gmail.com: -- components: +Extension Modules type: - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20463 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19658] inspect.getsource weird case
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
lines, lnum = getsourcelines(object)
File /home/private/.local/lib/python3.3/inspect.py, line 715, in
getsourcelines
lines, lnum = findsource(object)
File /home/private/.local/lib/python3.3/inspect.py, line 553, in findsource
if not sourcefile and file[0] + file[-1] != '':
IndexError: string index out of range
expected:
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
lines, lnum = getsourcelines(object)
File /home/private/.local/lib/python3.3/inspect.py, line 715, in
getsourcelines
lines, lnum = findsource(object)
File /home/private/.local/lib/python3.3/inspect.py, line 563, in findsource
raise IOError('could not get source code')
OSError: could not get source code
this is a extraction, it appears that python in certein circumstances creates
code objects with that setup on its own,
im still further investigating
--
messages: 203426
nosy: Ronny.Pfannschmidt
priority: normal
severity: normal
status: open
title: inspect.getsource weird case
type: behavior
versions: Python 2.7, Python 3.2, Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19658
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19658] inspect.getsource weird case
Changes by Ronny Pfannschmidt ronny.pfannschm...@gmail.com: -- components: +Library (Lib) ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19658 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17446] doctest test finder doesnt find line numbers of properties
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: doctest test finder doesnt find line numbers of properties ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17446 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17039] socket.SocketIO hides socket timeouts as blocking errors
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 -- messages: 180660 nosy: Ronny.Pfannschmidt priority: normal severity: normal status: open title: socket.SocketIO hides socket timeouts as blocking errors versions: Python 3.2, Python 3.3, Python 3.4, Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17039 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17039] socket.SocketIO hides socket timeouts as blocking errors
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16363] super cannot invoke descriptors
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 the problem and has a proof of concept for an extended super allowing descriptor invocations -- components: Interpreter Core files: test_super.py messages: 174184 nosy: Ronny.Pfannschmidt priority: normal severity: normal status: open title: super cannot invoke descriptors type: enhancement versions: Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5 Added file: http://bugs.python.org/file27792/test_super.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16363 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14965] super() and property inheritance behavior
Changes by Ronny Pfannschmidt ronny.pfannschm...@gmail.com: -- nosy: +Ronny.Pfannschmidt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14965 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14161] python2 file __repr__ does not escape filename
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14161] python2 file __repr__ does not escape filename
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://bugs.python.org/issue14161 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15309] buffer/memoryview slice assignment uses only memcpy
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 title: buffer/memoryview slice assignment uses only memcpy versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15309 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14964] distutils2.utils.resolve_name cleanup
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 name so it can raise the correct error -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14964 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14967] distutils2.utils.resolve_name cannot be implemented to give correct errors in all situations
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, giving a completely different error instead of the real error this is not solvable without a marker or really nasty hacks o track subsequent imports -- assignee: eric.araujo components: Distutils2 messages: 161990 nosy: Ronny.Pfannschmidt, alexis, eric.araujo, tarek priority: normal severity: normal status: open title: distutils2.utils.resolve_name cannot be implemented to give correct errors in all situations ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14967] distutils2.utils.resolve_name cannot be implemented to give correct errors in all situations
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 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14967] distutils2.utils.resolve_name cannot be implemented to give correct errors in all situations
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 no attribute bar -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14964] distutils2.utils.resolve_name cleanup
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/issue14964 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14964] distutils2.utils.resolve_name cleanup
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/issue14964 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14964] distutils2.utils.resolve_name cleanup
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, tarek priority: normal severity: normal status: open title: distutils2.utils.resolve_name cleanup type: enhancement Added file: http://bugs.python.org/file25766/resolve_name.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14964 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
pyrepl 0.8.4 - multiline terminal editing and liberal licensed readline replacement
Hello, i'm pleased to announce the release of pyrepl 0.8.4 its available at http://pypi.python.org/pypi/pyrepl/0.8.4 pyrepl is a Python library, inspired by readline, for building flexible command line interfaces, featuring: * sane multi-line editing * history, with incremental search * completion, including displaying of available options * a fairly large subset of the readline emacs-mode keybindings * a liberal, Python-style, license * a new python top-level * no global variables, so you can run two or more independent readers without having their histories interfering. * no hogging of control -- it should be easy to integrate pyrepl into YOUR application's event loop. * generally speaking, a much more interactive experience than readline (it's a bit like a cross between readline and emacs's mini-buffer) * unicode support (given terminal support) * a readline replacement which supports colors Summary of 0.8.4: + initial python3 support (expect some bugs) + support for more readline hooks + backport various fixes from pypy + gracefully break on sys.stdout.close() Summary of 0.8.3: + First release from new home on bitbucket. + Various fixes to pyrepl.readline. + Allow pyrepl to run if unicodedata is unimportable. Summary of 0.8.2: + This is the same version which is distributed with PyPy 1.4, which uses it as its default interactive interpreter: - have the possibility of having a CPython-like prompt, with as PS1 and ... as PS2 - add the pyrepl.readline module, which exposes a subset of CPython's readline implemented on top of pyrepl + Add support for colored completions: see e.g. fancycomplete: http://bitbucket.org/antocuni/fancycompleter -- http://mail.python.org/mailman/listinfo/python-announce-list Support the Python Software Foundation: http://www.python.org/psf/donations/
[issue14161] python2 file __repr__ does not escape filename
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 place -- messages: 154649 nosy: Ronny.Pfannschmidt priority: normal severity: normal status: open title: python2 file __repr__ does not escape filename type: behavior versions: Python 2.6, Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14161 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6784] byte/unicode pickle incompatibilities between python2 and python3
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/issue6784 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13444] closed stdout causes error on stderr when the interpreter unconditionally flushes on shutdown
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13444] closed stdout causes error on stderr when the interpreter unconditionally flushes on shutdown
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.' in _io.TextIOWrapper name='stdout' mode='w' encoding='ANSI_X3.4-1968' ignored its related to how Issue #5319 was fixed -- components: Interpreter Core messages: 148055 nosy: Ronny.Pfannschmidt, georg.brandl, mkc, pitrou, terry.reedy priority: normal severity: normal status: open title: closed stdout causes error on stderr when the interpreter unconditionally flushes on shutdown versions: Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13444 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13381] compile fails to compile a ast module object giving a incomprehensible error
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 compiling the source works fine -- files: test_keymap.py messages: 147401 nosy: Ronny.Pfannschmidt priority: normal severity: normal status: open title: compile fails to compile a ast module object giving a incomprehensible error type: behavior versions: Python 3.2 Added file: http://bugs.python.org/file23652/test_keymap.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13381 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13381] compile fails to compile a ast module object giving a incomprehensible error
Changes by Ronny Pfannschmidt ronny.pfannschm...@gmail.com: -- nosy: +benjamin.peterson ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13381 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13274] heapq pure python version uses islice without guarding for negative counts
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 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13274 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13274] heapq pure python version uses islice without guarding for negative counts
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: 146483 nosy: Ronny.Pfannschmidt priority: normal severity: normal status: open title: heapq pure python version uses islice without guarding for negative counts type: behavior versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13274 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12216] future imports change the reporting of syntaxerrors
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 print_function\ndef foo(', '', 'exec')
Traceback (most recent call last):
File stdin, line 1, in module
File , line 2
def foo(
^
SyntaxError: invalid syntax
--
messages: 137285
nosy: Ronny.Pfannschmidt
priority: normal
severity: normal
status: open
title: future imports change the reporting of syntaxerrors
versions: Python 2.5, Python 2.6, Python 2.7, Python 3.1, Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12216
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
