On 2016-08-29 23:56, Chris Angelico wrote:
> Up until very recently, the system Python has only been the Python 2.
> (For a while, it wasn't even 2.7, but I could easily use altinstall
> for that.) I have deliberately wanted to use 3.6 for ALL testing, not
> just by messing with venvs or shell alia
On Tue, Aug 30, 2016 at 11:58 AM, Matt Wheeler wrote:
> I think the real PSA is "don't mess with the system python(3) version".
>
> So you've managed to fix this issue, but what if there are others? I think
> packages on Debian have a reasonable right to expect that the version of
> python3 in the
I think the real PSA is "don't mess with the system python(3) version".
On Mon, 29 Aug 2016 at 13:18 Chris Angelico wrote:
> If, like me, you build Python 3.6 from source and make it your default
> 'python3' binary, you may run into issues with the latest
> apt-listchanges, which has switched to
If, like me, you build Python 3.6 from source and make it your default
'python3' binary, you may run into issues with the latest
apt-listchanges, which has switched to using Python 3. The symptom is
an ImportError trying to "import debconf", which is available in
dist-packages in the system Python,
