Re: Compressing objects.inv?

cool extension -- any plans to develop/contribute a handler for DBTS? On Mon, 03 Jan 2011, Michael Fladischer wrote: > While preparing the sphinx-issuetracker package, I noticed that -- =--= Keep in touch

coming back to packaging multiple versions of libraries

So in the thread 'Python packaging, dependencies, upstream facilities' we had a brief talk that faded out; rather than resurrecting the entire thread, I'd like to pick one point that seems like a necessary condition to me: installing the eggs in versioned paths rather than simple module paths. Tak

Re: Compressing objects.inv?

* Michael Fladischer , 2011-01-03, 00:17: While preparing the sphinx-issuetracker package, I noticed that sphinx.ext.intersphinx uses the "objects.inv" files that are generated by sphinx-build to resolve cross-package references in documentation (if configured in doc/conf.py, which is the case

Re: Compressing objects.inv?

On Mon, Jan 3, 2011 at 00:17, Michael Fladischer wrote: > Would it make sense to file bugs for those packages that ship > objects.inv.gz instead of objects.inv? Yes, I think so (with severity minor I'd say). Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.

Compressing objects.inv?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, While preparing the sphinx-issuetracker package, I noticed that sphinx.ext.intersphinx uses the "objects.inv" files that are generated by sphinx-build to resolve cross-package references in documentation (if configured in doc/conf.py, which is the

pyflakes in DACA

FYI, Debian Automated Code Analysis now includes pyflakes: http://qa.debian.org/daca/pyflakes/sid/ -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2011