Éric Araujo mer...@netwok.org added the comment:
Alright, closing.
--
resolution: - fixed
stage: - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12117
Éric Araujo mer...@netwok.org added the comment:
Is this still relevant?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12117
___
___
Brett Cannon br...@python.org added the comment:
Unless someone cares enough to decorate the tests that should not write the
bytecode (I think I have one such decorator in the importlib tests, but I think
it is more for other VMs than for this situation) then I wouldn't worry about
this.
Nick Coghlan ncogh...@gmail.com added the comment:
Several of these could be handled just by having test.support.make_legacy_pyc()
fall back to compiling from source if sys.dont_write_bytecode is set.
The others may need to be skipped in that situation.
--
Antoine Pitrou pit...@free.fr added the comment:
Honestly, now that it's been established that it has to do with a bogus system
default (on Mageia/Mandriva installs), I'm not sure it's worth fixing if it
means adding more logic to the tests.
--
assignee: brett.cannon -
R. David Murray rdmur...@bitdance.com added the comment:
In fact, not fixing it might send a small message as to what we think about
that particular system default :)
--
nosy: +r.david.murray
___
Python tracker rep...@bugs.python.org
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12117
___
Changes by STINNER Victor victor.stin...@haypocalc.com:
--
title: test_importlib failure - Failures with PYTHONDONTWRITEBYTECODE:
test_importlib, test_imp, test_distutils, test_packaging, test_runpy,
test_import
___
Python tracker
