Cindy Sue Causey writes:
> Mine's Python 3.8.5 on Bullseye..
Howdy, Cindy^^^
*Because* i like very so much Bullseye^^^
Sincerely, Byung-Hee from South Korea
--
^고맙습니다 _白衣從軍_ 감사합니다_^))//
Dear Arun,
"J.Arun Mani" writes:
> Hello.
> I'm using Debian Testing (upgraded from Debian 10). Today I started Python 3,
> but it was not able to interpret any
> commands from stdin and resulted in Segmentation Fault. Luckily
> modules (python3 -m ) and files ...
Just i guess because you are
Hello all.
I found a crazy fix to this issue. Running Python in Isolation mode raises no
problem ! That is, you need to run Python like this:
$ python3 -I
So having the isolation mode fix the issue, what next step shall I take to make
the fix permanent (I mean tweak or look at which modules,
On 8/4/20, J.Arun Mani wrote:
> Hello.
> I'm using Debian Testing (upgraded from Debian 10). Today I started Python
> 3, but it was not able to interpret any commands from stdin and resulted in
> Segmentation Fault. Luckily modules (python3 -m ) and files (python3
> ) works fine though.
>
>
"J.Arun Mani" writes:
> Hello.
> I'm using Debian Testing (upgraded from Debian 10). Today I started
> Python 3, but it was not able to interpret any commands from stdin and
> resulted in Segmentation Fault. Luckily modules (python3 -m )
> and files (python3 ) works fine though.
>
> Observed:
>
Hello.
I'm using Debian Testing (upgraded from Debian 10). Today I started Python 3,
but it was not able to interpret any commands from stdin and resulted in
Segmentation Fault. Luckily modules (python3 -m ) and files (python3
) works fine though.
Observed:
$ python3
Python 3.8.3rc1 (default,
6 matches
Mail list logo
