| 1 |
On 2012-03-02 2:24 PM, Dale <rdalek1967@×××××.com> wrote: |
| 2 |
> But if I tell eselect to set it to 3 something then that is what the |
| 3 |
> system will try to use right? Isn't that what eselect does? I'm |
| 4 |
> recalling what was posted after you emerge python here. The einfo/ewarn |
| 5 |
> thingy. |
| 6 |
> |
| 7 |
> Again, this may have changed but what I'm wondering is if we need the |
| 8 |
> python 2 stuff any more if we can set this to python 3. After all, |
| 9 |
> python 2 has to die eventually. ^_^ |
| 10 |
|
| 11 |
did you miss my earlier reply? |
| 12 |
|
| 13 |
Mine also shows it is set to 3.1... |
| 14 |
|
| 15 |
# eselect python list --python3 |
| 16 |
Available Python 3 interpreters: |
| 17 |
[1] python3.1 * |
| 18 |
[2] python3.2 |
| 19 |
myhost : Fri Mar 02, 13:07:51 : ~ |
| 20 |
# |
| 21 |
|
| 22 |
So, that I'm guessing the correct way to do this is: |
| 23 |
|
| 24 |
eselect python set --python3 2 |
| 25 |
|
| 26 |
? |
Archives