On 10/21/19, Albert-Jan Roskam wrote:
> On 18 Oct 2019 20:36, Chris Angelico wrote:
>
>> That's correct. The output of the command is, by default, given to you
>> in bytes.
>
> Do you happen to know why this is the default? And is there a reliable way
> to figure out the encoding? On posix, it's
On Tue, Oct 22, 2019 at 8:16 AM Albert-Jan Roskam
wrote:
>
>
>
> On 18 Oct 2019 20:36, Chris Angelico wrote:
>
> On Sat, Oct 19, 2019 at 5:29 AM Jagga Soorma wrote:
> >
> > Hello,
> >
> > I am writing my second python script and got it to work using
> > python2.x. However, realized that I shoul
On 18 Oct 2019 20:36, Chris Angelico wrote:
On Sat, Oct 19, 2019 at 5:29 AM Jagga Soorma wrote:
>
> Hello,
>
> I am writing my second python script and got it to work using
> python2.x. However, realized that I should be using python3 and it
> seems to fail with the following message:
>
> --
On Sat, Oct 19, 2019 at 5:29 AM Jagga Soorma wrote:
>
> Hello,
>
> I am writing my second python script and got it to work using
> python2.x. However, realized that I should be using python3 and it
> seems to fail with the following message:
>
> --
> Traceback (most recent call last):
> File "t
Hello,
I am writing my second python script and got it to work using
python2.x. However, realized that I should be using python3 and it
seems to fail with the following message:
--
Traceback (most recent call last):
File "test_script.py", line 29, in
test_cmd = ("diskcmd -u " + x + " | gr
