Le jeudi 22 juin 2006 à 00:23 +0200, Arthur de Jong a écrit :
> Thanks for the documentation. I will make deciding between
> python-support and python-central easier. The whole thing does seem to
> be a little of a mess, especially regarding these:
> http://blogs.turmzimmer.net/2006/06/20#pycentral
> http://kitenet.net/~joey/blog/entry/on_forking_debhelper.html
> 
> I'm not sure what to make of these as I don't really have time to read
> the whole python-support vs python-central flamewar on debian-python.

This is mostly a disagreement between Matthias Klose and myself on what
is a good technical solution. Matthias wrote python-central because he
thought python-support wasn't doing enough, and I reworked
python-support in return to make it compatible with python-central,
because I believe python-central has a bad design from the very
beginning. As a result, you can switch from one to the other easily.

> > > I'm packaging a simple python application (webcheck) but most
> > > documentation (and stuff on the mailing list) is about public modules
> > > and extensions. I also ship a symlink in /usr/bin:
> > >   /usr/bin/webcheck -> ../lib/python2.3/site-packages/webcheck/webcheck.py
> > > what to do with it.
> > 
> > I think you should stop ship it as a symbolic link, as this way it
> > cannot cope with major python upgrades. A better way would be to
> > make /usr/bin/webcheck a very small script looking like:
> > #! /usr/bin/python
> > import webcheck
> > webcheck.main()
> > (I have no idea of the actual needed syntax, but I think you get the
> > idea.)
> 
> I don't see what the problem is with the symbolic link. It has the nice
> extra feature that you don't have to play around with sys.path to get
> the imports simple.

The problem with the symlink is that you cannot update it automatically
when the default python version changes.

> I was planning on moving the files to /usr/share/webcheck or somesuch
> (also depending on the chosen packaging solution). The modules could
> probably be used publicly but this is really untested and unsupported at
> the moment.

If these modules are meant to be private, I strongly recommend to make
them private, indeed.

> Giving it some thought, should the symlink point
> to /var/lib/python-support/python-2.x/webcheck.py for the current python
> version (ugly solution)? Would packaging webcheck to have private
> modules not cause this problem?

Indeed, packaging it as private modules solves the problem. You can even
keep your symlink, in this case, as the directory names won't change
when the default python version changes.

Cheers,
-- 
 .''`.           Josselin Mouette        /\./\
: :' :           [EMAIL PROTECTED]
`. `'                        [EMAIL PROTECTED]
  `-  Debian GNU/Linux -- The power of freedom

Attachment: signature.asc
Description: Ceci est une partie de message numériquement signée

Reply via email to