Mike Coleman <[EMAIL PROTECTED]> writes:
> Okay, but I'm thinking that not all .pycs should necessarily go in
> /usr/lib/pythonX.X (or whatever). I was thinking that generally useful python
> code should go in those directories, but that code that's really only useful
> as part of a particular app
Rob Tillotson <[EMAIL PROTECTED]> writes:
> Then we have no choice, all Python packages will have to depend on a
> specific version of Python and be installed under that version's
> library, no matter how the .pycs are supplied.
Okay, but I'm thinking that not all .pycs should necessarily go in
/
Moshe Zadka <[EMAIL PROTECTED]> writes:
> On 14 Nov 2000, Rob Tillotson wrote:
[...]
> > Any package that has a binary extension in it will necessarily have to
> > be compiled for a specific Python version.
>
> This isn't true. Python 1.5.2-compiled extensions will work just fine
> with Python
Hi,
Since I'm waiting in the NM queue (DAM stage), I'm seeking for sponsorship
on two python packages named:
- python-unit
- python-xml (adopted)
These packages have been checked by Joel Rosdahl, a valuable Debian Developer,
and can be found at http://jerome.marant.free.fr/debian/testing
T
On 15 Nov 2000, Rob Tillotson wrote:
> How about the other way around? If the goal is to have 1.5.2 coexist
> with 2.0 on the same machine, this still presents a potential problem
> which will force packages to be dependent on one version or the
> other.
Correct: things built for 2.0 have a good
Moshe Zadka <[EMAIL PROTECTED]> writes:
> On 15 Nov 2000, Rob Tillotson wrote:
> > Moshe Zadka <[EMAIL PROTECTED]> writes:
> > > This isn't true. Python 1.5.2-compiled extensions will work just fine
> > > with Python 2.0.
> >
> > Hmm, they have changed the C API version several times in the past
>
On 15 Nov 2000, Rob Tillotson wrote:
> Moshe Zadka <[EMAIL PROTECTED]> writes:
> > This isn't true. Python 1.5.2-compiled extensions will work just fine
> > with Python 2.0.
>
> Hmm, they have changed the C API version several times in the past
> with minor releases, I guess it just didn't occur
Moshe Zadka <[EMAIL PROTECTED]> writes:
> This isn't true. Python 1.5.2-compiled extensions will work just fine
> with Python 2.0.
Hmm, they have changed the C API version several times in the past
with minor releases, I guess it just didn't occur to me that there
would be a major release without
Here is the current Python-Dev consensus about installing things
in tools. Is there a Python-specific policy against these, or
is that possible?
--
Moshe Zadka <[EMAIL PROTECTED]> -- 95855124
http://advogato.org/person/moshez
-- Forwarded message --
Date: Tue, 14 Nov 2000 23:10:0
On 14 Nov 2000, Rob Tillotson wrote:
> 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 wil
10 matches
Mail list logo
