Gregor Hoffleit <[EMAIL PROTECTED]> writes:
[...]
> From the discussion, the most pressing problem is how we tackle the
> upgrade of potato python-* packages, especially when they have
> incomplete/incorrect dependencies.
Here's a radical idea: don't. Leave the Python 1.5.2 packages exactly
as
Le jeu, jui 26, 2001, à 10:34:40 +0200, Gregor Hoffleit a écrit:
> > Too bad there's no DocBook-aware Wiki system...
>
> Well, there's no DocBook-aware Wiki yet, but then, ZWiki uses mostly
> StructuredText. The ZopeBook is written in StructuredText, too
> (http://sourceforge.net/cvs/?group_id=2
* Radovan Garabik <[EMAIL PROTECTED]> [010726 18:49]:
> On Thu, Jul 26, 2001 at 05:24:04PM +0200, Gregor Hoffleit wrote:
> > Then, we still have to agree on a strategy how to set up the
> > dependencies, in order to make the upgrade work in an intuitive way.
> >
> > For maintainers of Python exten
Cyrille, I's sure you don't mind quoting your mail in debian-python:
* Cyrille Chepelov <[EMAIL PROTECTED]> [010726 21:10]:
> Le jeu, jui 26, 2001, à 05:24:04 +0200, Gregor Hoffleit a écrit:
> > It's been much too long since I posted the last status report. I'm
> > swamped with all kinds of real w
On Thu, Jul 26, 2001 at 05:24:04PM +0200, Gregor Hoffleit wrote:
>
>
> My proposal for woody: Python 1.5.2 is renamed to python1.5-*. Python
> 2.1.1 will be shipped as python2.1-*. Do we need python2.0-* as well ?
I do not think so
>
> Then, we still have to agree on a strategy how to set up t
At some point, Gregor Hoffleit <[EMAIL PROTECTED]> wrote:
> My proposal for woody: Python 1.5.2 is renamed to python1.5-*. Python
> 2.1.1 will be shipped as python2.1-*. Do we need python2.0-* as well ?
I don't see why. Looking at the list of changes from 2.0 to 2.1 at
http://www.amk.ca/python/2.
6 matches
Mail list logo
