Moshe Zadka <[EMAIL PROTECTED]> writes:
> Say module x Depends: on Python. Where do you install it? python1.5 or
> python2.0? Remember that you must encode this information in the
> package itself.
Any package that has a binary extension in it will necessarily have to
be compiled for a specific P
On Tue, 14 Nov 2000, Bastian Kleineidam wrote:
> >What might be a problem is where we put 3rd party modules.
> In /usr/lib/pythonx.x/site-packages/
Say module x Depends: on Python. Where do you install it? python1.5 or
python2.0? Remember that you must encode this information in the
package itse
>What might be a problem is where we put 3rd party modules.
In /usr/lib/pythonx.x/site-packages/
Bastian
On Tue, 14 Nov 2000, Michael Sobolev wrote:
> Why? I do think that it's a good idea to separate .py{c,o} files from .py
> ones.
As was mentioned before, .py{c,o} is very specific to Python minor
version. The Python development team, while it is firmly commited to
source-compatability, has no int
On Mon, Nov 13, 2000 at 09:39:45PM +0200, Moshe Zadka wrote:
> > BTW, what's the reason of making packages containing .py files? Is not it
> > better to include only .pyo and .pyc files? And for those who really need
> > sources there those source packages?
>
> No! These are needed at run-time,
From: Jeremy Hylton <[EMAIL PROTECTED]>
To: Guido van Rossum <[EMAIL PROTECTED]>
Cc: python-dev@python.org
Subject: [Python-Dev] installing IDLE & other Tools
Date: Mon, 13 Nov 2000 23:16:01 -0500 (EST)
I just saw your note about whether IDLE was packaged with the Python
RPMs. It isn't, nor is a
6 matches
Mail list logo
