This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.araujo
Recipients alexis, eric.araujo, flox, francismb, higery, jlove, nadeem.vawda, paul.moore, pitrou, rpetrov, tarek, vinay.sajip, westley.martinez
Date 2011-11-05.16:48:02
SpamBayes Score 4.1846782e-08
Marked as misclassified No
Message-id <1320511682.91.0.217976628659.issue13193@psf.upfronthosting.co.za>
In-reply-to
Content
I’ll open another reports for the possible bug in _generate_cache and for review of the other tests calling get_distribution.

> Test test_install and test_command_install_data interference cache
I’ve added checks in regrtest to make sure that each tests clears the caches some time ago.

> Most important is why packaging use global variables.
[citation needed].  First, mutable objects with a global name (let’s not use “variable” for Python) are not unconditionally evil; see sys.path and sys.modules for example.  Second, how concretely would you change that implementation?  We need shared caches for functions in packaging.database.  They should be built on demand, and should be cleared by higher-level libraries or applications when the filesystem has changed (after an installation or removal for example).  With these constraints, do you have implementation ideas?
History
Date User Action Args
2011-11-05 16:48:02eric.araujosetrecipients: + eric.araujo, paul.moore, vinay.sajip, pitrou, nadeem.vawda, tarek, rpetrov, flox, alexis, westley.martinez, jlove, higery, francismb
2011-11-05 16:48:02eric.araujosetmessageid: <1320511682.91.0.217976628659.issue13193@psf.upfronthosting.co.za>
2011-11-05 16:48:02eric.araujolinkissue13193 messages
2011-11-05 16:48:02eric.araujocreate