Python packaging

[Adrian von Bidder]

Heyho!

I'm fairly new to Python and absolutely new to packaging python stuff.  So
I'd be happy about a few comments [cc:s appreciated] or pointers to online
resources (sorry, I'm working mostly offline, so I've not looked beyong the
python policy.)

My small application needs python3 (yes, I realize this is just in
experimental.)

-> python-central vs. python-support: is one generally preferred over the
other, or is it just a matter of taste?  Does either already support
python3?  At least python-support appeared not to (it tried to byte-compile
with regular python despite the XS-Python-Version: >= 3.1 header being
present.

-> dh_python reports that I can delete it if dh_pysupport is present.  
Python policy says to include both.  dh_python manpage says dh_python is
deprecated.

-> Python policy is unclear: should XS-Python-Version be a field of the
source or the binary package?  XB-P-V is clearly on the binary package.

-> Policy says I should ship my (private) modules in /usr/share/<appname>.  
How will Python find the modules?

-> Minor nit: Both /usr/share/python/README.Debian and
/usr/share/python3/README.Debian refer to /usr/share/doc/python2.3/; this
shouuld probably be updated... (or better yet:: generated while building the
package, so it won't be forgotten again?)

Thanks for any comments!

cheers
-- vbi

--
featured link: Debian Bookmark Collection - http://bookmarks.debian.net/

[Alessandro Dentella]

On Tue, Sep 15, 2009 at 07:02:23AM +0200, Adrian von Bidder wrote:

> Heyho!
>
> I'm fairly new to Python and absolutely new to packaging python stuff.  So
> I'd be happy about a few comments [cc:s appreciated] or pointers to online
> resources (sorry, I'm working mostly offline, so I've not looked beyong the
> python policy.)
>
> My small application needs python3 (yes, I realize this is just in
> experimental.)
>
> -> python-central vs. python-support: is one generally preferred over the
> other, or is it just a matter of taste?  Does either already support
> python3?  At least python-support appeared not to (it tried to byte-compile
> with regular python despite the XS-Python-Version: >= 3.1 header being
> present.

there has been a fairly long thread with title 'XS-Python-Version vs
pyversions ' some days ago, you may want to read it at:

  http://lists.debian.org/debian-python/2009/09/threads.html

> -> Policy says I should ship my (private) modules in /usr/share/<appname>.  
> How will Python find the modules?

i guess you must patch your application to add that to sys.path...

sandro
*:-)



--
Sandro Dentella  *:-)
http://sqlkit.argolinux.org        SQLkit home page - PyGTK/python/sqlalchemy


--
To UNSUBSCRIBE, email to debian-python-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Julian Andres Klode-4]

On Tue, Sep 15, 2009 at 09:12:54AM +0200, Alessandro Dentella wrote:
> On Tue, Sep 15, 2009 at 07:02:23AM +0200, Adrian von Bidder wrote:
> > -> Policy says I should ship my (private) modules in /usr/share/<appname>.  
> > How will Python find the modules?
>
> i guess you must patch your application to add that to sys.path...

Installing scripts into /usr/share/<appname> and symlinking them
to /usr/{s,}bin is a bit easier.

--
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.


--
To UNSUBSCRIBE, email to debian-python-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Adrian von Bidder]

On Tuesday 15 September 2009 09.12:54 Alessandro Dentella wrote:
> there has been a fairly long thread with title 'XS-Python-Version vs
> pyversions ' some days ago, you may want to read it at:
>
>   http://lists.debian.org/debian-python/2009/09/threads.html

Hmm.

Reading only the first few messages:
 -> there was a BoF where something was discussed
 -> the Python Toolchain maintainer isn't doing his Job
 -> some ignore what was discussed/decided/requested/demanded at that BoF
 -> what this actually was and why is in the minds of a few people and not
written down.

I don't think I want to read that.

I guess I'll just cobble something together that installs on my system, then
upload, and then react to bug reports.  I don't have time to help design a
better Python policy and/or port the current one to Python3.

[still, thanks for the link]

cheers
-- vbi

[cc:s still appreciated.]

--
Example is not the main thing in influencing others.  It is the only thing.
                -- Albert Schweitzer

[Alessandro Dentella]

On Tue, Sep 15, 2009 at 09:27:23AM +0200, Julian Andres Klode wrote:
> On Tue, Sep 15, 2009 at 09:12:54AM +0200, Alessandro Dentella wrote:
> > On Tue, Sep 15, 2009 at 07:02:23AM +0200, Adrian von Bidder wrote:
> > > -> Policy says I should ship my (private) modules in /usr/share/<appname>.  
> > > How will Python find the modules?
> >
> > i guess you must patch your application to add that to sys.path...
>
> Installing scripts into /usr/share/<appname> and symlinking them
> to /usr/{s,}bin is a bit easier.

He was talking about private modules that should be found by
python. Symlinking to /usr/{S,}bin wouldn't be any usefull in my opinion.

sandro
*:-)


--
To UNSUBSCRIBE, email to debian-python-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Bernd Zeimetz]

Adrian von Bidder wrote:

> Reading only the first few messages:
>  -> there was a BoF where something was discussed
>  -> the Python Toolchain maintainer isn't doing his Job
>  -> some ignore what was discussed/decided/requested/demanded at that BoF
>  -> what this actually was and why is in the minds of a few people and not
> written down.
>
> I don't think I want to read that.

Ack.
Probably do what most people (no, I didn't count them) seem to do:
Use python-support and debian/pyversions. And if you run into problems, you join
#debian-python on OFTC and just ask for help.


Cheers,

Bernd

--
 Bernd Zeimetz                             Debian GNU/Linux Developer
 GPG Fingerprints: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79
                   ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F


--
To UNSUBSCRIBE, email to debian-python-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Julian Andres Klode-4]

On Tue, Sep 15, 2009 at 03:21:41PM +0200, Alessandro Dentella wrote:

> On Tue, Sep 15, 2009 at 09:27:23AM +0200, Julian Andres Klode wrote:
> > On Tue, Sep 15, 2009 at 09:12:54AM +0200, Alessandro Dentella wrote:
> > > On Tue, Sep 15, 2009 at 07:02:23AM +0200, Adrian von Bidder wrote:
> > > > -> Policy says I should ship my (private) modules in /usr/share/<appname>.  
> > > > How will Python find the modules?
> > >
> > > i guess you must patch your application to add that to sys.path...
> >
> > Installing scripts into /usr/share/<appname> and symlinking them
> > to /usr/{s,}bin is a bit easier.
>
> He was talking about private modules that should be found by
> python. Symlinking to /usr/{S,}bin wouldn't be any usefull in my opinion.

I should have written "symlinking from" and not "symlinking to".

If you install the modules in /usr/share/<appname>/ and the script too, and
then create a symlink in /usr/{s,}bin pointing to your script, python will
automatically find the modules. That's the way I do it in my packages, e.g.
gnome-app-install.

--
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.


--
To UNSUBSCRIBE, email to debian-python-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...