Michal Kurowski <[EMAIL PROTECTED]> writes:
> Trond Eivind Glomsrřd [[EMAIL PROTECTED]] wrote:
> >
> > Python 1.5.2 is what's being used in the distribution, python2 is
> > there for people to play with/develop for the future with. Note that
> > all suppor
Trond Eivind Glomsrřd [[EMAIL PROTECTED]] wrote:
>
> Python 1.5.2 is what's being used in the distribution, python2 is
> there for people to play with/develop for the future with. Note that
> all support modules (database modules, newt, etc) only are shipped
for
> 1.5.2
>
>>>>> "teg" == Trond Eivind <[EMAIL PROTECTED]>
>>>>> wrote the following on 05 Apr 2002 17:57:44 -0500
teg> For the current series: Depend on python2 =
...
teg> In the future, python 1.5.2 will be obsoleted and python will
teg&g
Ben Escoto <[EMAIL PROTECTED]> writes:
> How does redhat recommend that RPMs require python >= 2.x?
For the current series: Depend on python2 =
> In version 7.x it seems that there are separate python (v1.x) and
> python2 (2.x) packages, so an RPM cannot simply speci
--==_Exmh_1886728034P
Content-Type: text/plain; charset=us-ascii
How does redhat recommend that RPMs require python >= 2.x? In version
7.x it seems that there are separate python (v1.x) and python2 (2.x)
packages, so an RPM cannot simply specify python >= 2.x. However,
other distrib
Will Newton <[EMAIL PROTECTED]> writes:
> I see Python 2 is in Powertools as "python2". When will it be moving into
> the main distribution
Next major series.
> and what is holding it up?
It isn't binary compatible with 1.5[1], and we don't break binary
com
I see Python 2 is in Powertools as "python2". When will it be moving into
the main distribution, and what is holding it up?
I haven't found any problems as yet moving from 1.5.2 -> 2.0.
___
Redhat-devel-list mailing list
[EMAI
