| 1 |
On 09/19/2009 08:21 PM, Dale wrote: |
| 2 |
> Dirkjan Ochtman wrote: |
| 3 |
>> On Sat, Sep 19, 2009 at 19:06, Alex Legler<a3li@g.o> wrote: |
| 4 |
>> |
| 5 |
>>> What is the point of stabilizing it if users shouldn't use it as main |
| 6 |
>>> interpreter? Just leave it in ~arch until it can be safely used. |
| 7 |
>>> |
| 8 |
>> |
| 9 |
>> Making it easily available so that people can port stuff, so that the |
| 10 |
>> entire world may be able to use it as their main interpreter sooner? |
| 11 |
>> |
| 12 |
>> Seriously, it's out there, there's no reason to keep it from stable. |
| 13 |
>> Just prevent people from making python invoke 3.x and everything will |
| 14 |
>> be fine. |
| 15 |
>> |
| 16 |
>> Cheers, |
| 17 |
>> |
| 18 |
>> Dirkjan |
| 19 |
>> |
| 20 |
>> |
| 21 |
>> |
| 22 |
> |
| 23 |
> Isn't ~arch supposed to be for testing? Isn't that the point of having |
| 24 |
> ~arch? |
| 25 |
|
| 26 |
For testing, yes. But what about people who want to use it? Not for |
| 27 |
portage, not as main interpreter, but simply "use it." Python is a |
| 28 |
programming language and has many uses, it's not only there to make |
| 29 |
portage happy. There are people who actually use it, and those people |
| 30 |
would like it stabilized. Just because portage isn't ported to 3.x yet |
| 31 |
shouldn't mean it can't go stable if there are no blockers about 3.x itself. |
Archives