Stray .pyc files from tests
by Orion Poplawski
I just ran into an issue with a package under review where stray python2
.pyc files were getting put into the python3_sitelib directory. The
tests were run with:
PYTHONPATH=%{buildroot}%{python3_sitelib} py.test-%{python3_version} -vv
and one of the tests ended up calling /usr/bin/python.setup.py --version
triggering the loading and byte-compiling of the installed module. I
don't know if this is common issue or not (I suspect not). Just a heads
up I guess. Not sure if this is something that can be prevented in any
other general way.
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
7 years, 11 months
(Another) One mailing list to rule them all
by Robert Kuska
For those who are interested new (official) mailing list was created (kudos to Nick
Coghlan and Barry Warsaw). The purpose of the mailing list is to bring together all folks
from various Linux distro communities to discuss any future (e.g. usr/bin/python)
or current features (/wave PEP476) affecting our beloved distributions and how to
deal with them consistently :-).
Also here is Nick's reasoning:
> With the Python 3 migration, and the growth in interest in user level
> package management for development purposes, what do you think of the idea
> of setting up a new Linux SIG to have those discussions? I know it's a case
> of "yet another mailing list", but I think it will be worthwhile to have a
> clear point of collaboration within the Python ecosystem, rather than
> expecting Pythonistas to know how to reach out to (other) distros directly.
Don't hesitate and sign-in @ https://mail.python.org/mailman/listinfo/linux-sig
---
Robert Kuska
{rkuska}
7 years, 11 months
