| 1 |
Arfrever Frehtes Taifersar Arahesis wrote: |
| 2 |
> 2009-09-20 16:44:09 Jesús Guerrero napisał(a): |
| 3 |
>> On Sat, 19 Sep 2009 19:09:38 +0200, Dirkjan Ochtman <djc@g.o> |
| 4 |
>> wrote: |
| 5 |
>>> On Sat, Sep 19, 2009 at 19:06, Alex Legler <a3li@g.o> wrote: |
| 6 |
>>>> What is the point of stabilizing it if users shouldn't use it as main |
| 7 |
>>>> interpreter? Just leave it in ~arch until it can be safely used. |
| 8 |
>>> Making it easily available so that people can port stuff, so that the |
| 9 |
>>> entire world may be able to use it as their main interpreter sooner? |
| 10 |
>> Ummm, if someone is not able to keywords the ~arch package, I doubt, |
| 11 |
>> highly doubt, that s/he is going to be able to port anything, seriously... |
| 12 |
> |
| 13 |
> Some packages (whose older versions might be stable) might soon start requiring |
| 14 |
> Python 3. Stabilization of these packages cannot be delayed due to the fact |
| 15 |
> that some other packages don't work with Python 3. |
| 16 |
> |
| 17 |
|
| 18 |
Yes indeed and when you have enough apps needing Python 3, it's much |
| 19 |
easier to sell python 3 to the developer base as there's actually |
| 20 |
benefit to users. |
| 21 |
|
| 22 |
Regards, |
| 23 |
Petteri |
Archives