Quoting Neil Schemenauer <[EMAIL PROTECTED]>:
> Donovan Baarda wrote:
> > In my above diagrams the (>=2.1,<2.2) dependancy could be replaced
> with a
> > python-api-2.1 provided by python (as suggested by Neil), but I think
> this
> > actually introduces confusion rather than convenience. The pr
Donovan Baarda wrote:
> In my above diagrams the (>=2.1,<2.2) dependancy could be replaced with a
> python-api-2.1 provided by python (as suggested by Neil), but I think this
> actually introduces confusion rather than convenience. The problem is that it
> doesn't really represent a particular v
Quoting Neil Schemenauer <[EMAIL PROTECTED]>:
> Jim Penny wrote:
[...]
> The python is a small package to create a link from /usr/bin/python2.2
> to /usr/bin/python. python-eggs is a dummy package for dependencies
> (similar to what is done for GCC). When we upgrade Python to 2.2 we
> have:
>
>
Jim Penny wrote:
> Why? Could you better explain your reasoning here?
> On the face of it, it certainly seems that python-1.5 ought to be
> able to provide python-api-1.5.
It breaks dependencies. We've been through this before but I'll explain
it again. Here's a dependency graph:
On Tue, Oct 02, 2001 at 06:53:39AM -0700, Neil Schemenauer wrote:
> Carey Evans wrote:
> > In my original example, spam embeds libpython2.1.so. It would make
> > sense for this to mean it depends on python-api-2.1, though this isn't
> > what the current shlibs file says.
>
> Only "python" can pro
Carey Evans wrote:
> In my original example, spam embeds libpython2.1.so. It would make
> sense for this to mean it depends on python-api-2.1, though this isn't
> what the current shlibs file says.
Only "python" can provide "python-api-*".
Neil
Neil Schemenauer <[EMAIL PROTECTED]> writes:
> spam should depend on python not python-2.1.
In my original example, spam embeds libpython2.1.so. It would make
sense for this to mean it depends on python-api-2.1, though this isn't
what the current shlibs file says.
--
Carey Evans ht
Carey Evans wrote:
>/> python-2.1 -\
>spam -- > python
>\---> python-eggs ---> python-api-2.1 ---/
spam should depend on python not python-2.1.
Neil
Neil Schemenauer <[EMAIL PROTECTED]> writes:
[...]
> Excellent point. I've updated the policy document to prevent this. The
> python package should provide python-api-X.Y. Module packages should
> depend on python-api-X.Y. If someone packages an older version of
> Python they should call it p
On Sat, Sep 29, 2001 at 11:10:43PM -0700, Neil Schemenauer wrote:
> Carey Evans wrote:
> > By way of example, suppose I have a package "spam" that embeds Python
> > 2.1, and therefore depends on python-2.1. spam also uses the "eggs"
> > module, and therefore depends on python-eggs, which depends o
Carey Evans wrote:
> By way of example, suppose I have a package "spam" that embeds Python
> 2.1, and therefore depends on python-2.1. spam also uses the "eggs"
> module, and therefore depends on python-eggs, which depends on
> python-2.1 itself.
>
> Now Python 2.2 is released, and eggs is recomp
On 18-Sep-2001 Neil Schemenauer wrote:
> Please comment.
>
> Neil
it is /usr/share/common-licenses, not licences. Annoying thing there being two
spellings of some common words.
>
> We could perhaps differenciate python modules and bindings.
>
> For example, libxml bindings for Python would be libxml-python.
> Also, python-gtk would become libgtk-python, python-gnome would become
> libgnome-python
> and so on.
>
> However, xml tools for python would stay pytho
On Wed, 2001-09-26 at 11:37, Jérôme Marant wrote:
> David Coe <[EMAIL PROTECTED]> writes:
>
> > Neil Schemenauer <[EMAIL PROTECTED]> writes:
> >
> > > 2.3. Module Package Names
> > > -
> > >
> > > Python module packages should be named for the primary module
> > >
David Coe <[EMAIL PROTECTED]> writes:
> Neil Schemenauer <[EMAIL PROTECTED]> writes:
>
> > 2.3. Module Package Names
> > -
> >
> > Python module packages should be named for the primary module
> > provided. The naming convention for module `foo' is `python-foo'
Neil Schemenauer <[EMAIL PROTECTED]> writes:
> 2.3. Module Package Names
> -
>
> Python module packages should be named for the primary module
> provided. The naming convention for module `foo' is `python-foo'.
> Packages which include multiple modules may
Neil Schemenauer <[EMAIL PROTECTED]> writes:
> Please comment.
This all looks good. I do have a question concerning dependencies on
Python modules.
By way of example, suppose I have a package "spam" that embeds Python
2.1, and therefore depends on python-2.1. spam also uses the "eggs"
module,
Jim Penny wrote:
> I just want to ask a couple of questions to make sure that I understand
> this in detail. Suppose python2.1 is installed as python and you
> also have python1.5 installed. You have
> script poo which is invoked via #!/usr/bin/python and
> script bah which is invoked via #!/us
On Mon, Sep 17, 2001 at 07:33:26PM -0700, Neil Schemenauer wrote:
>
I just want to ask a couple of questions to make sure that I understand
this in detail. Suppose python2.1 is installed as python and you
also have python1.5 installed. You have
script poo which is invoked via #!/usr/bin/python
Ricardo Javier Cardenes wrote:
> I think this:
>
> /usr/local/lib/python./site-packages
> /usr/local/lib/site-python
> /usr/lib/python./site-packages
>
> should be the order.
I see not problem with that. It shouldn't make any difference except in
the case you describe.
> And what happene
Mikael Hedin wrote:
> Looks fine to me. I'd prefer /usr/bin/python-X.Y, but that's
> cosmetics, not really important.
It has been pythonX.Y for many years. We should not change it.
Neil
On Mon, Sep 17, 2001 at 07:33:26PM -0700, Neil Schemenauer wrote:
> 1.2. Module Path
>
>
> Python searches a number of directories for modules. The module
> search path for Debian has been ordered to include these locations at
> the beginning of the path in the fol
Looks fine to me. I'd prefer /usr/bin/python-X.Y, but that's
cosmetics, not really important.
--
Mikael Hedin, MSc +46 (0)980 79176
Swedish Institute of Space Physics +46 (0)8 344979 (home)
Box 812, S-981 28 KIRUNA, Sweden+46 (0)70 5891533 (mobile)
[gpg key fingerprint =
Please comment.
Neil
Debian Python Policy
Neil Schemenauer <[EMAIL PROTECTED]>
version 0.1
24 matches
Mail list logo
