2009-09-20 20:46:17 Nirbheek Chauhan napisał(a):
> On Sun, Sep 20, 2009 at 11:57 PM, Arfrever Frehtes Taifersar Arahesis
> wrote:
> > There is a difference between Python scripts and Python modules.
> >
>
> Yes, I'm well aware of the difference between them.
>
> [snip]
> > Python modules shouldn
On Sun, Sep 20, 2009 at 06:20:41PM -0400, Mark Loeser wrote:
> Arfrever Frehtes Taifersar Arahesis said:
> > I agree. But Python 3.1 doesn't have more issues than Python 2.6, so
> > the stabilization is reasonable.
>
> And how about all of the packages in the tree that use python? You are
> miss
Mark Loeser wrote:
> Dawid Węgliński said:
>
>> You mix it up. Portage works with python 3.1. If an user switches to python
>> 3.1 as the main interpreter, it's possible that his own scripts won't work.
>> Marking it stable sometine in november give's some time to ebuilds
>> maintainers to f
Arfrever Frehtes Taifersar Arahesis said:
> I agree. But Python 3.1 doesn't have more issues than Python 2.6, so
> the stabilization is reasonable.
And how about all of the packages in the tree that use python? You are
missing that huge part. That's like saying libfoo works absolutely
great, bu
Dawid Węgliński said:
> You mix it up. Portage works with python 3.1. If an user switches to python
> 3.1 as the main interpreter, it's possible that his own scripts won't work.
> Marking it stable sometine in november give's some time to ebuilds
> maintainers to fix their python based apps jus
Petteri Räty wrote:
> Every Gentoo system where world or system includes deps like
>> =dev-lang/python-2.5 will get it installed because in this case Portage
> will automatically update to the latest slot at least according to my
> quick research. I don't like putting stuff to users systems that th
2009-09-20 20:46:17 Nirbheek Chauhan napisał(a):
> On Sun, Sep 20, 2009 at 11:57 PM, Arfrever Frehtes Taifersar Arahesis
> wrote:
> > There is a difference between Python scripts and Python modules.
> >
>
> Yes, I'm well aware of the difference between them.
>
> [snip]
> > Python modules shouldn
On Sun, Sep 20, 2009 at 11:57 PM, Arfrever Frehtes Taifersar Arahesis
wrote:
> There is a difference between Python scripts and Python modules.
>
Yes, I'm well aware of the difference between them.
[snip]
> Python modules shouldn't have shebang. Python modules are intended to
> be imported from
2009-09-20 19:47:28 Nirbheek Chauhan napisał(a):
> On Sun, Sep 20, 2009 at 11:05 PM, Arfrever Frehtes Taifersar Arahesis
> wrote:
> >> Package X (stable) requires python-2
> >> Package Y (stable) requires python-3
> >>
> >> => User can't use both at the same time.
> >
> > Distribute/Setuptools wil
2009-09-20 19:30:54 Nirbheek Chauhan napisał(a):
> On Sun, Sep 20, 2009 at 8:54 PM, Arfrever Frehtes Taifersar Arahesis
> wrote:
> > 2009-09-20 16:53:37 Jesús Guerrero napisał(a):
> >> # eselect python set 2
> >> # emerge -s foo
> >> File "/usr/bin/emerge", line 41
> >> except PermissionDeni
On Sun, Sep 20, 2009 at 11:05 PM, Arfrever Frehtes Taifersar Arahesis
wrote:
>> Package X (stable) requires python-2
>> Package Y (stable) requires python-3
>>
>> => User can't use both at the same time.
>
> Distribute/Setuptools will ensure that appropriate shebang is present in
> Python
> scrip
2009-09-20 19:25:55 Nirbheek Chauhan napisał(a):
> On Sun, Sep 20, 2009 at 9:37 PM, Arfrever Frehtes Taifersar Arahesis
> wrote:
> > which depend on Python 3) wouldn't break any packages and wouldn't require
> > to switch main Python interpreter to Python 3.
> >
>
> Package X (stable) requires py
On Sun, Sep 20, 2009 at 8:54 PM, Arfrever Frehtes Taifersar Arahesis
wrote:
> 2009-09-20 16:53:37 Jesús Guerrero napisał(a):
>> # eselect python set 2
>> # emerge -s foo
>> File "/usr/bin/emerge", line 41
>> except PermissionDenied, e:
>> ^
>> SyntaxError: invalid
On Sun, Sep 20, 2009 at 9:37 PM, Arfrever Frehtes Taifersar Arahesis
wrote:
> which depend on Python 3) wouldn't break any packages and wouldn't require
> to switch main Python interpreter to Python 3.
>
Package X (stable) requires python-2
Package Y (stable) requires python-3
=> User can't use
2009-09-20 18:51:53 Robert Buchholz napisał(a):
> On Sunday 20 September 2009, Arfrever Frehtes Taifersar Arahesis wrote:
> > Some packages (whose older versions might be stable) might soon start
> > requiring Python 3. Stabilization of these packages cannot be delayed
> > due to the fact that some
Arfrever Frehtes Taifersar Arahesis wrote:
> 2009-09-20 16:44:09 Jesús Guerrero napisał(a):
>> On Sat, 19 Sep 2009 19:09:38 +0200, Dirkjan Ochtman
>> wrote:
>>> On Sat, Sep 19, 2009 at 19:06, Alex Legler wrote:
What is the point of stabilizing it if users shouldn't use it as main
interp
On Sunday 20 September 2009, Arfrever Frehtes Taifersar Arahesis wrote:
> Some packages (whose older versions might be stable) might soon start
> requiring Python 3. Stabilization of these packages cannot be delayed
> due to the fact that some other packages don't work with Python 3.
Of course the
2009-09-20 17:56:46 Nirbheek Chauhan napisał(a):
> On Sun, Sep 20, 2009 at 9:16 PM, Arfrever Frehtes Taifersar Arahesis
> wrote:
> > Some packages (whose older versions might be stable) might soon start
> > requiring
> > Python 3. Stabilization of these packages cannot be delayed due to the fact
On Sun, Sep 20, 2009 at 9:16 PM, Arfrever Frehtes Taifersar Arahesis
wrote:
> Some packages (whose older versions might be stable) might soon start
> requiring
> Python 3. Stabilization of these packages cannot be delayed due to the fact
> that some other packages don't work with Python 3.
>
Are
2009-09-20 16:44:09 Jesús Guerrero napisał(a):
> On Sat, 19 Sep 2009 19:09:38 +0200, Dirkjan Ochtman
> wrote:
> > On Sat, Sep 19, 2009 at 19:06, Alex Legler wrote:
> >> What is the point of stabilizing it if users shouldn't use it as main
> >> interpreter? Just leave it in ~arch until it can be s
On Sun, 20 Sep 2009 17:24:53 +0200, Arfrever Frehtes Taifersar Arahesis
wrote:
> 2009-09-20 16:53:37 Jesús Guerrero napisał(a):
>> On Sun, 20 Sep 2009 00:41:32 +0200, Dawid Węgliński
>> wrote:
>> > On Sunday 20 of September 2009 00:32:28 Dale wrote:
>> >> >
>> >> > ~arch is for testing ebuilds, n
2009-09-20 16:53:37 Jesús Guerrero napisał(a):
> On Sun, 20 Sep 2009 00:41:32 +0200, Dawid Węgliński
> wrote:
> > On Sunday 20 of September 2009 00:32:28 Dale wrote:
> >> >
> >> > ~arch is for testing ebuilds, not the upstream package
> >>
> >> So it would be OK to mark something "stable" even tho
Jesús Guerrero wrote:
> On Sun, 20 Sep 2009 00:41:32 +0200, Dawid Węgliński
> wrote:
>
>> On Sunday 20 of September 2009 00:32:28 Dale wrote:
>>
~arch is for testing ebuilds, not the upstream package
>>> So it would be OK to mark something "stable" even tho portage itsel
On Sun, 20 Sep 2009 00:41:32 +0200, Dawid Węgliński
wrote:
> On Sunday 20 of September 2009 00:32:28 Dale wrote:
>> >
>> > ~arch is for testing ebuilds, not the upstream package
>>
>> So it would be OK to mark something "stable" even tho portage itself
>> doesn't work with it? Sorry, this makes n
Richard Freeman wrote:
> Olivier Crête wrote:
>>
>> ~arch is for testing ebuilds, not the upstream package
>>
>
> I'm pretty sure this isn't the case - at least not as cleanly as you
> suggest. Certainly testing the ebuilds themselves is part of the
> reason for having ~arch, but upstream readines
On Sun, 20 Sep 2009 08:55:00 +1200, Alistair Bush
wrote:
>> Stabilization of Python 3.1.* will be requested at the beginning of
>> november. There was a suggestion to create a news item which would
>> inform
>> users that temporarily they shouldn't switch to Python 3 as their main
>> interpret
On Sat, 19 Sep 2009 20:51:17 +0200, Arfrever Frehtes Taifersar Arahesis
wrote:
> 2009-09-19 20:22:49 Tobias Klausmann napisał(a):
>> Hi!
>>
>> Aside from the remarks made by others (and speaking as someone
>> who maintains Python software), there is one reason for me to not
>> switch Python 3 to
On Sat, 19 Sep 2009 19:09:38 +0200, Dirkjan Ochtman
wrote:
> On Sat, Sep 19, 2009 at 19:06, Alex Legler wrote:
>> What is the point of stabilizing it if users shouldn't use it as main
>> interpreter? Just leave it in ~arch until it can be safely used.
>
> Making it easily available so that peopl
Olivier Crête wrote:
~arch is for testing ebuilds, not the upstream package
I'm pretty sure this isn't the case - at least not as cleanly as you
suggest. Certainly testing the ebuilds themselves is part of the reason
for having ~arch, but upstream readiness is part of it as well. If a
pa
Alex Alexander wrote:
> *On Sat, Sep 19, 2009 at 23:21, Robert Bridge wrote:
>> So the question isn't SHOULD python-3 be stabilised, it's what will break if
>> it is surely?
>
> There seems to be a misunderstanding on what will happen if/when
> python 3 gets stabilized.
>
> The short answer is..
*On Sat, Sep 19, 2009 at 23:21, Robert Bridge wrote:
> So the question isn't SHOULD python-3 be stabilised, it's what will break if
> it is surely?
There seems to be a misunderstanding on what will happen if/when
python 3 gets stabilized.
The short answer is... *drum roll*... nothing :)
I'm gue
On Sunday 20 of September 2009 00:32:28 Dale wrote:
> >
> > ~arch is for testing ebuilds, not the upstream package
>
> So it would be OK to mark something "stable" even tho portage itself
> doesn't work with it? Sorry, this makes no sense to me. I run stable
> for the most part and having a packa
Olivier Crête wrote:
> On Sat, 2009-09-19 at 12:21 -0500, Dale wrote:
>
>> Dirkjan Ochtman wrote:
>>
>>> On Sat, Sep 19, 2009 at 19:06, Alex Legler wrote:
>>>
>>>
What is the point of stabilizing it if users shouldn't use it as main
interpreter? Just leave it in ~arch u
> Stabilization of Python 3.1.* will be requested at the beginning of
> november. There was a suggestion to create a news item which would inform
> users that temporarily they shouldn't switch to Python 3 as their main
> interpreter. Python ebuilds don't automatically activate Python 3, so I'm
>
Speaking as a user, I seem to recall having multiple versions of python
installed in the past, and never really knowing or caring which version was
being used so long as stuff worked. If you want to install python-3.14159 in
the stable tree, than go right ahead, so long as anything that doesn't wor
Arfrever Frehtes Taifersar Arahesis wrote:
> 2009-09-19 20:20:10 AllenJB napisał(a):
>> Dirkjan Ochtman wrote:
>>> On Sat, Sep 19, 2009 at 19:06, Alex Legler wrote:
What is the point of stabilizing it if users shouldn't use it as main
interpreter? Just leave it in ~arch until it can be s
On Sun, Sep 20, 2009 at 12:23 AM, Arfrever Frehtes Taifersar Arahesis
wrote:
>> Have any other distribution moved to purely using python-3.1?
>
> We won't move to purely using Python 3.1. Both Python 2 and 3 will be used.
>
Let me modify me question: Has any other distribution moved to using
pyth
Arfrever Frehtes Taifersar Arahesis said:
> Stabilization of Python 3.1.* will be requested at the beginning of november.
> There was a suggestion to create a news item which would inform users that
> temporarily they shouldn't switch to Python 3 as their main interpreter.
> Python ebuilds don't a
2009-09-19 20:20:10 AllenJB napisał(a):
> Dirkjan Ochtman wrote:
> > On Sat, Sep 19, 2009 at 19:06, Alex Legler wrote:
> >> What is the point of stabilizing it if users shouldn't use it as main
> >> interpreter? Just leave it in ~arch until it can be safely used.
> >
> > Making it easily availabl
2009-09-19 20:45:45 Nirbheek Chauhan napisał(a):
> On Sat, Sep 19, 2009 at 10:18 PM, Arfrever Frehtes Taifersar Arahesis
> wrote:
> > Stabilization of Python 3.1.* will be requested at the beginning of
> > november.
> > There was a suggestion to create a news item which would inform users that
>
2009-09-19 20:22:49 Tobias Klausmann napisał(a):
> Hi!
>
> Aside from the remarks made by others (and speaking as someone
> who maintains Python software), there is one reason for me to not
> switch Python 3 to stable yet: lack of compatibility. Software
> that runs with 3.x will not run with any
On Sat, Sep 19, 2009 at 10:18 PM, Arfrever Frehtes Taifersar Arahesis
wrote:
> Stabilization of Python 3.1.* will be requested at the beginning of november.
> There was a suggestion to create a news item which would inform users that
> temporarily they shouldn't switch to Python 3 as their main in
Alex Legler wrote:
> On Sat, 19 Sep 2009 19:09:38 +0200, Dirkjan Ochtman
> wrote:
>
>> Seriously, it's out there, there's no reason to keep it from stable.
>> Just prevent people from making python invoke 3.x and everything will
>> be fine.
>>
>
> Yeah, right, let's install it on all those stabl
Hi!
Aside from the remarks made by others (and speaking as someone
who maintains Python software), there is one reason for me to not
switch Python 3 to stable yet: lack of compatibility. Software
that runs with 3.x will not run with any 2.x version as of today
(and I doubt there will ever be a 2.
Dirkjan Ochtman wrote:
> On Sat, Sep 19, 2009 at 19:06, Alex Legler wrote:
>> What is the point of stabilizing it if users shouldn't use it as main
>> interpreter? Just leave it in ~arch until it can be safely used.
>
> Making it easily available so that people can port stuff, so that the
> entir
On Sat, 2009-09-19 at 12:21 -0500, Dale wrote:
> Dirkjan Ochtman wrote:
> > On Sat, Sep 19, 2009 at 19:06, Alex Legler wrote:
> >
> >> What is the point of stabilizing it if users shouldn't use it as main
> >> interpreter? Just leave it in ~arch until it can be safely used.
> >>
> >
> > Ma
On Sat, 19 Sep 2009 19:09:38 +0200, Dirkjan Ochtman
wrote:
> On Sat, Sep 19, 2009 at 19:06, Alex Legler wrote:
> > What is the point of stabilizing it if users shouldn't use it as
> > main interpreter? Just leave it in ~arch until it can be safely
> > used.
>
> Making it easily available so tha
Dirkjan Ochtman wrote:
> On Sat, Sep 19, 2009 at 19:06, Alex Legler wrote:
>
>> What is the point of stabilizing it if users shouldn't use it as main
>> interpreter? Just leave it in ~arch until it can be safely used.
>>
>
> Making it easily available so that people can port stuff, so that
On Sat, Sep 19, 2009 at 19:06, Alex Legler wrote:
> What is the point of stabilizing it if users shouldn't use it as main
> interpreter? Just leave it in ~arch until it can be safely used.
Making it easily available so that people can port stuff, so that the
entire world may be able to use it as
On Sat, 19 Sep 2009 18:48:27 +0200, Arfrever Frehtes Taifersar Arahesis
wrote:
> Stabilization of Python 3.1.* will be requested at the beginning of
> november. There was a suggestion to create a news item which would
> inform users that temporarily they shouldn't switch to Python 3 as
> their ma
On Sat, Sep 19, 2009 at 18:48, Arfrever Frehtes Taifersar Arahesis
wrote:
> Stabilization of Python 3.1.* will be requested at the beginning of november.
> There was a suggestion to create a news item which would inform users that
> temporarily they shouldn't switch to Python 3 as their main inter
Stabilization of Python 3.1.* will be requested at the beginning of november.
There was a suggestion to create a news item which would inform users that
temporarily they shouldn't switch to Python 3 as their main interpreter.
Python ebuilds don't automatically activate Python 3, so I'm not sure if
52 matches
Mail list logo
