On 14.12.2015 10:49, Petr Viktorin wrote:
On 12/14/2015 10:29 AM, Jan Cholasta wrote:
On 9.12.2015 12:04, Petr Viktorin wrote:
On 12/04/2015 12:49 PM, Jan Cholasta wrote:
On 4.12.2015 12:43, Petr Viktorin wrote:
On 12/04/2015 12:15 PM, Jan Cholasta wrote:
On 4.12.2015 10:53, Petr Viktorin wr
On 12/14/2015 10:29 AM, Jan Cholasta wrote:
> On 9.12.2015 12:04, Petr Viktorin wrote:
>> On 12/04/2015 12:49 PM, Jan Cholasta wrote:
>>> On 4.12.2015 12:43, Petr Viktorin wrote:
On 12/04/2015 12:15 PM, Jan Cholasta wrote:
> On 4.12.2015 10:53, Petr Viktorin wrote:
>> On 12/04/2015 08:
On 9.12.2015 12:04, Petr Viktorin wrote:
On 12/04/2015 12:49 PM, Jan Cholasta wrote:
On 4.12.2015 12:43, Petr Viktorin wrote:
On 12/04/2015 12:15 PM, Jan Cholasta wrote:
On 4.12.2015 10:53, Petr Viktorin wrote:
On 12/04/2015 08:51 AM, Jan Cholasta wrote:
On 3.12.2015 15:42, Petr Viktorin wro
On 12/04/2015 12:49 PM, Jan Cholasta wrote:
> On 4.12.2015 12:43, Petr Viktorin wrote:
>> On 12/04/2015 12:15 PM, Jan Cholasta wrote:
>>> On 4.12.2015 10:53, Petr Viktorin wrote:
On 12/04/2015 08:51 AM, Jan Cholasta wrote:
> On 3.12.2015 15:42, Petr Viktorin wrote:
>> On 12/03/2015 10:
On 4.12.2015 12:43, Petr Viktorin wrote:
On 12/04/2015 12:15 PM, Jan Cholasta wrote:
On 4.12.2015 10:53, Petr Viktorin wrote:
On 12/04/2015 08:51 AM, Jan Cholasta wrote:
On 3.12.2015 15:42, Petr Viktorin wrote:
On 12/03/2015 10:55 AM, Jan Cholasta wrote:
[...]
If we do encode/decode in run(
On 12/04/2015 12:15 PM, Jan Cholasta wrote:
> On 4.12.2015 10:53, Petr Viktorin wrote:
>> On 12/04/2015 08:51 AM, Jan Cholasta wrote:
>>> On 3.12.2015 15:42, Petr Viktorin wrote:
On 12/03/2015 10:55 AM, Jan Cholasta wrote:
[...]
> If we do encode/decode in run(), I think there should be a
On 4.12.2015 10:53, Petr Viktorin wrote:
On 12/04/2015 08:51 AM, Jan Cholasta wrote:
On 3.12.2015 15:42, Petr Viktorin wrote:
On 12/03/2015 10:55 AM, Jan Cholasta wrote:
[...]
If we don't care about output somewhere, we should not capture it
there
at all.
Then people need to remember to put
On 12/04/2015 08:51 AM, Jan Cholasta wrote:
> On 3.12.2015 15:42, Petr Viktorin wrote:
>> On 12/03/2015 10:55 AM, Jan Cholasta wrote:
>> [...]
> If we don't care about output somewhere, we should not capture it
> there
> at all.
Then people need to remember
On 3.12.2015 15:42, Petr Viktorin wrote:
On 12/03/2015 10:55 AM, Jan Cholasta wrote:
[...]
If we don't care about output somewhere, we should not capture it
there
at all.
Then people need to remember to put "capture_output=True" everywhere
(except that also disables logging of the output, so w
On 12/03/2015 10:55 AM, Jan Cholasta wrote:
[...]
>>> If we don't care about output somewhere, we should not capture it
>>> there
>>> at all.
>>
>> Then people need to remember to put "capture_output=True" everywhere
>> (except that also disables logging of the output, so we
On 2.12.2015 14:52, Petr Viktorin wrote:
On 12/02/2015 08:59 AM, Jan Cholasta wrote:
On 1.12.2015 12:26, Petr Viktorin wrote:
On 11/30/2015 08:59 AM, Jan Cholasta wrote:
On 25.11.2015 15:47, Petr Viktorin wrote:
On 11/25/2015 11:04 AM, Jan Cholasta wrote:
On 24.11.2015 17:21, Petr Viktorin w
On 12/02/2015 08:59 AM, Jan Cholasta wrote:
> On 1.12.2015 12:26, Petr Viktorin wrote:
>> On 11/30/2015 08:59 AM, Jan Cholasta wrote:
>>> On 25.11.2015 15:47, Petr Viktorin wrote:
On 11/25/2015 11:04 AM, Jan Cholasta wrote:
> On 24.11.2015 17:21, Petr Viktorin wrote:
>> On 11/23/2015 1
On 1.12.2015 12:26, Petr Viktorin wrote:
On 11/30/2015 08:59 AM, Jan Cholasta wrote:
On 25.11.2015 15:47, Petr Viktorin wrote:
On 11/25/2015 11:04 AM, Jan Cholasta wrote:
On 24.11.2015 17:21, Petr Viktorin wrote:
On 11/23/2015 10:50 AM, Jan Cholasta wrote:
On 23.11.2015 07:43, Jan Cholasta w
On 11/30/2015 08:59 AM, Jan Cholasta wrote:
> On 25.11.2015 15:47, Petr Viktorin wrote:
>> On 11/25/2015 11:04 AM, Jan Cholasta wrote:
>>> On 24.11.2015 17:21, Petr Viktorin wrote:
On 11/23/2015 10:50 AM, Jan Cholasta wrote:
> On 23.11.2015 07:43, Jan Cholasta wrote:
>> On 19.11.2015 0
On 25.11.2015 15:47, Petr Viktorin wrote:
On 11/25/2015 11:04 AM, Jan Cholasta wrote:
On 24.11.2015 17:21, Petr Viktorin wrote:
On 11/23/2015 10:50 AM, Jan Cholasta wrote:
On 23.11.2015 07:43, Jan Cholasta wrote:
On 19.11.2015 00:55, Petr Viktorin wrote:
On 11/03/2015 02:39 PM, Petr Viktorin
On 11/25/2015 11:04 AM, Jan Cholasta wrote:
> On 24.11.2015 17:21, Petr Viktorin wrote:
>> On 11/23/2015 10:50 AM, Jan Cholasta wrote:
>>> On 23.11.2015 07:43, Jan Cholasta wrote:
On 19.11.2015 00:55, Petr Viktorin wrote:
> On 11/03/2015 02:39 PM, Petr Viktorin wrote:
>> Hello,
>>
On 24.11.2015 17:21, Petr Viktorin wrote:
On 11/23/2015 10:50 AM, Jan Cholasta wrote:
On 23.11.2015 07:43, Jan Cholasta wrote:
On 19.11.2015 00:55, Petr Viktorin wrote:
On 11/03/2015 02:39 PM, Petr Viktorin wrote:
Hello,
Python 3's strings are Unicode, so data coming to or leaving a Python
pr
On 11/23/2015 10:50 AM, Jan Cholasta wrote:
> On 23.11.2015 07:43, Jan Cholasta wrote:
>> On 19.11.2015 00:55, Petr Viktorin wrote:
>>> On 11/03/2015 02:39 PM, Petr Viktorin wrote:
Hello,
Python 3's strings are Unicode, so data coming to or leaving a Python
program needs to be decode
On 23.11.2015 07:43, Jan Cholasta wrote:
On 19.11.2015 00:55, Petr Viktorin wrote:
On 11/03/2015 02:39 PM, Petr Viktorin wrote:
Hello,
Python 3's strings are Unicode, so data coming to or leaving a Python
program needs to be decoded/encoded if it's to be handled as a string.
One of the boundari
On 19.11.2015 00:55, Petr Viktorin wrote:
On 11/03/2015 02:39 PM, Petr Viktorin wrote:
Hello,
Python 3's strings are Unicode, so data coming to or leaving a Python
program needs to be decoded/encoded if it's to be handled as a string.
One of the boundaries where encoding is necessary is external
On 11/03/2015 02:39 PM, Petr Viktorin wrote:
> Hello,
> Python 3's strings are Unicode, so data coming to or leaving a Python
> program needs to be decoded/encoded if it's to be handled as a string.
> One of the boundaries where encoding is necessary is external programs,
> specifically, ipautil.ru
21 matches
Mail list logo