pyflakes in DACA

2011-01-02 Thread Jakub Wilk

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/20110102104920.ga7...@jwilk.net



Compressing objects.inv?

2011-01-02 Thread Michael Fladischer
-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 case for sphinx-issuetracker).

Some packages (e.g. python-sphinx itself) ship a gzip compressed
objects.inv.gz (it seems to me that dh_compress triggers this during
build) but sphinx.ext.intersphinx is not able to read compressed files.

Would it make sense to file bugs for those packages that ship
objects.inv.gz instead of objects.inv?

Regards,
- -- 
Michael Fladischer
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk0hB3IACgkQeJ3z1zFMUGaQwwCeLTCjPunwTGpz0ECZqO7SHtTu
MUMAoIsWpagZoB81TG/xfk1aaMLkdLo3
=8Cdj
-END PGP SIGNATURE-


-- 
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/4d210772.9000...@fladi.at



Re: Compressing objects.inv?

2011-01-02 Thread Sandro Tosi
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.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


-- 
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/aanlktim_ndtunxx6qyvde5rvpubvxwnxjohjbmcwv...@mail.gmail.com



Re: Compressing objects.inv?

2011-01-02 Thread Jakub Wilk

* 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 for 
sphinx-issuetracker).


Some packages (e.g. python-sphinx itself) ship a gzip compressed 
objects.inv.gz (it seems to me that dh_compress triggers this during 
build) but sphinx.ext.intersphinx is not able to read compressed files.


For python-sphinx, I've just committed a fix, thanks.

List of affected packages:

Michael Casadevall 
   python-sip-dev (U)

Ondrej Certik 
   python-mpmath-doc (U)
   python-numpy-doc (U)

David Cournapeau 
   python-numpy-doc (U)

Debian Python Modules Team 
   python-django-doc (U)
   python-jinja2-doc (U)
   python-kinterbasdb
   python-matplotlib-doc
   python-migrate (U)
   python-mpmath-doc
   python-multiprocessing
   python-networkx-doc
   python-numpy-doc
   python-paste (U)
   python-pywt
   python-repoze.what
   python-scrapy-doc
   python-sip-dev
   python-sphinx (U)
   python-sqlalchemy-doc (U)
   python-turbogears2-doc
   python-werkzeug (U)

Jan Dittberner 
   python-migrate

Benjamin Drung 
   python-matplotlib-doc (U)

Alexandre Fayolle 
   python-matplotlib-doc (U)
   python-numpy-doc (U)

Mikhail Gusarov 
   python-sphinx

Yaroslav Halchenko 
   python-mlpy-doc (U)
   python-mvpa-doc (U)
   python-nifti (U)
   python-nipy-doc (U)
   python-scikits-learn-doc (U)

Michael Hanke 
   python-mlpy-doc (U)
   python-mvpa-doc (U)
   python-nifti (U)
   python-nipy-doc (U)
   python-scikits-learn-doc (U)

Raphaël Hertzog 
   python-django-doc (U)

Matthias Klose 
   python-bsddb3-doc
   python-numpy-doc (U)

Chris Lamb 
   python-django-doc
   python-django-treebeard-doc

Stani M 
   phatch-doc (U)

Torsten Marek 
   python-sip-dev (U)

Emilio Pozuelo Monfort 
   phatch-doc (U)

Ignace Mouzannar 
   python-scrapy-doc (U)

Piotr Ożarowski 
   phatch-doc (U)
   python-jinja2-doc
   python-paste
   python-pywt (U)
   python-repoze.what (U)
   python-sqlalchemy-doc
   python-werkzeug (U)

Python Applications Packaging Team 
   ibid
   phatch-doc

Stefano Rivera 
   ibid (U)

Tomasz Rybak 
   python-pyopencl

Noah Slater 
   python-werkzeug

NeuroDebian Team 
   python-mlpy-doc
   python-mvpa-doc
   python-nifti
   python-nipy-doc
   python-scikits-learn-doc

Sandro Tosi 
   python-kinterbasdb (U)
   python-matplotlib-doc (U)
   python-mpmath-doc (U)
   python-multiprocessing (U)
   python-networkx-doc (U)
   python-numpy-doc (U)

Fabio Tranchitella 
   python-psycopg2

Iulian Udrea 
   git-cola

Jakub Wilk 
   python-sphinx (U)

Stefano Zacchiroli 
   python-repoze.what (U)
   python-turbogears2-doc (U)

Bernd Zeimetz 
   python-sip-dev (U)

Michal Čihař 
   gammu-doc

--
Jakub Wilk


signature.asc
Description: Digital signature


coming back to packaging multiple versions of libraries

2011-01-02 Thread Robert Collins
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.

Take something like wadllib - a library which has had the odd
effective api break without a namespace change. We currently install
its contents as:

/usr/share/pyshared
/usr/share/pyshared/wadllib
...

/usr/share/pyshared/wadllib-1.1.4.egg-info
/usr/share/pyshared/wadllib-1.1.4.egg-info/PKG-INFO
...

So the question is:
whats the simplest way to install this somewhere else - e.g.
/usr/share/pyshared/wadllib-1.1.4
and have
import wadllib
still work without user intervention.

Two options seem to present themselves to me at the moment:
 - the pyshared symlink logic could select the highest version and
link that into /usr/lib/.../wadllib as well as into
/usr/lib/.../wadllib-1.1.4
   - possibly using a single wadllib->wadllib-1.1.4 symlink, or
possibly using the 'normal' structure of directories + per-file links.
 - we could drop the versioned path into site.py in the same way
python-numeric etc do

I'm very interested in other approaches to make this work; the reason
for doing it were covered in the other thread, but making this one
case work would allow having two packages with slightly different
versions of something to coexist - which is immensely useful for
application (vs library) developers when developing for multiple
versions of dependencies.

It seems to me that the first option is the most efficient performance
wise for now; we should get better upstream support to, of course.

-Rob


-- 
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/aanlkti=6iq2z_d3tdzat0u35kfua_tz_drtutextq...@mail.gmail.com



Re: Compressing objects.inv?

2011-01-02 Thread Yaroslav Halchenko
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 www.onerussian.com
Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic


-- 
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/20110103015750.gu15...@onerussian.com