Quoting Matthias Klose <[EMAIL PROTECTED]>:
> Anthony Towns writes:
> > ] python-2.1_2.1.1
> > ] python_2.1.1 (depends on python-2.1) (does "ln
> /usr/bin/python{2.1,}")
> > ] python-2.1-_ (depends on python-2.1)
> > ] python-_ (depends on python and
> python-2.1-)
> >
> > Hrm. That should be
Quoting Bruce Sass <[EMAIL PROTECTED]>:
> Hi,
>
> On 16 Oct 2001, Jérôme Marant wrote:
> <...>
> > I installed both python1.5 and python2.1. And installing both on the
> same
> > system broke _all_ my python 1.5 packages: this is the alternative
> issue
> > Perl people have warned us about.
Matthias Klose wrote:
Ron writes:
On Tue, Oct 16, 2001 at 11:39:38AM +0200, Tille, Andreas wrote:
If you think that two separate wxgtk
versions are really necessary please speak now because Ron is preparing
packages for a new version.
Just to be completely clear about this, I almost certainly will
Anthony Towns writes:
> ] python-2.1_2.1.1
> ] python_2.1.1 (depends on python-2.1) (does "ln /usr/bin/python{2.1,}")
> ] python-2.1-_ (depends on python-2.1)
> ] python-_ (depends on python and python-2.1-)
>
> Hrm. That should be:
>
> Package: python-
> Version:
> Depends
Ron writes:
> On Tue, Oct 16, 2001 at 11:39:38AM +0200, Tille, Andreas wrote:
> > If you think that two separate wxgtk
> > versions are really necessary please speak now because Ron is preparing
> > packages for a new version.
>
> Just to be completely clear about this, I almost certainly will
> n
Bastian Kleineidam writes:
> Jérôme Marant wrote:
>
> > I said previously that the upgrade when OK. This is true, but I hadn't
> > look
> > further at that moment.
>
>
> My upgrade had some errors:
No errors. The postinst just compiled the testsuite. Btw, do we really
need the testsuite as
[Currently I am unable to read new incoming mails ... I'll respond
later to other messages]
Just uploaded a new python1.5 NMU which fixes three bugs I introduced.
Jérôme Marant writes:
> What should python modules packagers do now?
> Should we stop providing support for python2 and provide
>
Hi,
On 16 Oct 2001, Jérôme Marant wrote:
<...>
> I installed both python1.5 and python2.1. And installing both on the same
> system broke _all_ my python 1.5 packages: this is the alternative issue
> Perl people have warned us about.
>
> I discovered that /usr/bin/python is pointing to pyt
Jérôme Marant wrote:
I said previously that the upgrade when OK. This is true, but I hadn't look
further at that moment.
My upgrade had some errors:
File "/usr/lib/python2.1/test/nocaret.py", line 2
[x for x in x] = x
SyntaxError: can't assign to list comprehension
SyntaxError: from __futu
Hi,
I said previously that the upgrade when OK. This is true, but I hadn't look
further at that moment.
I installed both python1.5 and python2.1. And installing both on the same
system broke _all_ my python 1.5 packages: this is the alternative issue
Perl people have warned us about.
Hi,
The latest upgrade worked fine for me. Thanks to Gregor and
Matthias ;-)
What should python modules packagers do now?
Should we stop providing support for python2 and provide
python2.1 versions of our modules now?
Thanks.
--
Jérôme Marant <[EMAIL PROTECTED]>
<[EM
On Tue, Oct 16, 2001 at 11:39:38AM +0200, Tille, Andreas wrote:
> If you think that two separate wxgtk
> versions are really necessary please speak now because Ron is preparing
> packages for a new version.
Just to be completely clear about this, I almost certainly will
not consider having *both*
Hello,
the wxgtk maintainer asked me to foreward the following questions to this list:
> From [EMAIL PROTECTED] Tue Oct 16 11:31:09 2001
>
> What I'd really like to know is that (by far)
> most of the people currently using it with 1.5 will be happy that
> it is now built with 2.1
In my opinion a
On Sun, Oct 14, 2001 at 10:57:25AM +0200, Matthias Klose wrote:
> Jérôme Marant writes:
> > What about proposal and policy from Neil and his efforts?
> - the proposed packaging scheme doesn't allow smooth upgrades between
> one python version and a next version. compare python-1.5 to libc5
>
14 matches
Mail list logo
