Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #10631

Re: Could somebody change the alioth documentation, have a buster roadmap and know what's missing to move to python 3 entirely.

Show key headers only | View raw

Ondrej Novy <novy@ondrej.org> writes:

> do I understand you correctly that there is no default Python in
> Debian? :)

:-) Hopefully a little polite repetition will help the point become
clearer, though Andrey said it plainly in the initial response.

Shirish, now that we've established there is no “default Python” in
Debian, you may want to know that there *is* a concept of the default
interpreter for *a specific Python major version*.

You can ask the Debian system. First choose which Python major version
(currently Python 2 or Python 3) you want, then run the command to ask
what interpreter command to use:

    $ pyversions --default  # What is the name of the default Python 2 interpreter command?
    python2.7

    $ py3version --default  # What is the name of the default Python 3 interpreter command?
    python3.6

Note that you can *only* ask about the default within a specific Python
major version. Each of those commands is installed by a completely
separate Python environment, and neither of them care about the other:

    $ dpkg --search $(which pyversions py3versions)
    python-minimal: /usr/bin/pyversions
    python3-minimal: /usr/bin/py3versions

The ‘pyversions’ command asks *only* about Python 2. The ‘py3versions’
commandasks *only* about Python 3.

The answer you get for “default interpreter” depends which Python major
version you choose to interrogate; there's no default choice.

-- 
 \     “If you pick up a starving dog and make him prosperous, he will |
  `\      not bite you. This is the principal difference between a dog |
_o__)                    and a man.” —Mark Twain, _Pudd'n'head Wilson_ |
Ben Finney

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Could somebody change the alioth documentation, have a buster roadmap  and know what's missing to move to python 3 entirely. shirish शिरीष <shirishag75@gmail.com> - 2018-06-06 17:10 +0200
  Re: Could somebody change the alioth documentation, have a buster  roadmap and know what's missing to move to python 3 entirely. Andrey Rahmatullin <wrar@debian.org> - 2018-06-06 17:30 +0200
  Re: Could somebody change the alioth documentation, have a buster  roadmap and know what's missing to move to python 3 entirely. shirish शिरीष <shirishag75@gmail.com> - 2018-06-06 19:00 +0200
    Re: Could somebody change the alioth documentation, have a buster  roadmap and know what's missing to move to python 3 entirely. Andrey Rahmatullin <wrar@debian.org> - 2018-06-06 20:10 +0200
    Re: Could somebody change the alioth documentation, have a buster roadmap and know what's missing to move to python 3 entirely. Ben Finney <bignose@debian.org> - 2018-06-07 11:10 +0200
      Re: Could somebody change the alioth documentation, have a buster  roadmap and know what's missing to move to python 3 entirely. Ondrej Novy <novy@ondrej.org> - 2018-06-07 12:00 +0200
        Re: Could somebody change the alioth documentation, have a buster roadmap and know what's missing to move to python 3 entirely. Ben Finney <bignose@debian.org> - 2018-06-08 00:10 +0200

csiph-web