On Sun, Jan 21, 2018 at 12:46 PM, Steven D'Aprano
wrote:
> On Sun, 21 Jan 2018 12:21:40 +1100, Chris Angelico wrote:
>
>> Jim, let the installer put it where it wants to, and make sure you've
>> added it to PATH. Then you should be able to type "py" to start Python.
>
> Shouldn't the installer ens
On Sat, 20 Jan 2018 12:57:45 +0200, Serhiy Storchaka wrote:
> Just `end` instead of `end+1`.
Oops!
> And it is safer to use `bytes.decode(obj[start:end], 'latin1')` or
> `str(obj[start:end], 'latin1')` instead of
> `obj[start:end].decode('latin1')`. Just for the case if obj has
> overridden deco
On Sun, Jan 21, 2018 at 12:40 PM, bartc wrote:
> On 21/01/2018 01:21, Chris Angelico wrote:
>>
>> On Sun, Jan 21, 2018 at 12:08 PM, bartc wrote:
>>>
>>> On 20/01/2018 17:16, Jim Sadler wrote:
I downloaded python 3.6.4 and although everything about the installation
seems correc
On Sun, 21 Jan 2018 12:21:40 +1100, Chris Angelico wrote:
> Jim, let the installer put it where it wants to, and make sure you've
> added it to PATH. Then you should be able to type "py" to start Python.
Shouldn't the installer ensure that it puts "py" somewhere on the path?
--
Steve
--
htt
On 21/01/2018 01:21, Chris Angelico wrote:
On Sun, Jan 21, 2018 at 12:08 PM, bartc wrote:
On 20/01/2018 17:16, Jim Sadler wrote:
I downloaded python 3.6.4 and although everything about the installation
seems correct (path, file size, checking on cmd to see if file installed
correctly-it is)
On Sun, Jan 21, 2018 at 12:08 PM, bartc wrote:
> On 20/01/2018 17:16, Jim Sadler wrote:
>>
>> I downloaded python 3.6.4 and although everything about the installation
>> seems correct (path, file size, checking on cmd to see if file installed
>> correctly-it is)
>
>
> What do you mean by 'checking
On 20/01/2018 17:16, Jim Sadler wrote:
I downloaded python 3.6.4 and although everything about the installation
seems correct (path, file size, checking on cmd to see if file installed
correctly-it is)
What do you mean by 'checking on cmd'?
I would install it somewhere like c:\python364, then
On 2018-01-20, Marko Rauhamaa wrote:
> Grant Edwards :
[...]
>> I won't argue with that. I think that non-blocking ssl-wrapped
>> sockets _should_ have the same select/poll/send/recv API/semantics
>> that normal sockets do. I thought about writing my own
>> wrapped-ssl-socket class that does tha
Hi, Jim,
On Sat, Jan 20, 2018 at 11:16 AM, Jim Sadler wrote:
> I downloaded python 3.6.4 and although everything about the installation
> seems correct (path, file size, checking on cmd to see if file installed
> correctly-it is) the only window that will pop up when I attempt to run it
> is the
On 1/20/2018 12:16 PM, Jim Sadler wrote:
I downloaded python 3.6.4 and although everything about the installation
seems correct (path, file size, checking on cmd to see if file installed
correctly-it is) the only window that will pop up when I attempt to run it
is the set-up window offering to mo
I downloaded python 3.6.4 and although everything about the installation
seems correct (path, file size, checking on cmd to see if file installed
correctly-it is) the only window that will pop up when I attempt to run it
is the set-up window offering to modify, restore, or uninstall. I have
uninst
Grant Edwards :
> On 2018-01-20, Marko Rauhamaa wrote:
>> OpenSSL isn't the easiest beast to deal with, but I have been able to
>> abstract it (in C) so it behaves very close to TCP. The one blemish
>> is in the fact that the TLS protocol does not support a half-duplex
>> connection. Shame.
>>
>>
On 2018-01-20, Marko Rauhamaa wrote:
> Grant Edwards :
>
>> Asyncore seems to be based on fundamental assumptions that aren't true
>> for non-blocking ssl sockets.
>
> Pot calling kettle black.
>
> OpenSSL isn't the easiest beast to deal with, but I have been able to
> abstract it (in C) so it beh
Grant Edwards :
> Asyncore seems to be based on fundamental assumptions that aren't true
> for non-blocking ssl sockets.
Pot calling kettle black.
OpenSSL isn't the easiest beast to deal with, but I have been able to
abstract it (in C) so it behaves very close to TCP. The one blemish is
in the f
Aside from the obvious imports I've added (import numpy as np, etc),
there are still undefined objects (`names`, `times_`, `feat`,
`bind_ind`) and indentation errors. Can you post a *working* code to be
sped up and a benchmarking test?
As you're using Python 2, you can improve the code with th
Looking around for how to create (l)xml one sees typical tutorials like this:
https://www.blog.pythonlibrary.org/2013/04/30/python-101-intro-to-xml-parsing-with-elementtree/
Given the requirement to build up this xml:
1181251680
04008200E000
1181572063
On 2018-01-18, Grant Edwards wrote:
[regarding secure-smtpd -- a module based on smtpd and asyncore]
> That makes the SSL support pretty much useless.
>
> I'm trying to fix that, but I can't find any information or
> documentation about using asyncore with SSL.
Asyncore seems to be based on fun
On 20/01/2018 11:55, Thomas Jollans wrote:
> control is returned to t.resume. nonblocking_accept is supposed to be a
> coroutine
> Ergo, it schedules the nonblocking_accept coroutine (‘value’) to be
> called on the next iteration, and keeps the running listen_on coroutine
> (‘coroutine’) on the sta
On 19/01/18 22:50, Léo El Amri wrote:
> Hello list,
>
> I am currently trying to learn co-routine/asynchronous mechanisms in
> Python. I read the PEP 342, but I stumble on the fourth example.
> I don't understand what the lines "data = yield nonblocking_read(sock)"
> in echo_handler() and "connect
20.01.18 10:32, Steven D'Aprano пише:
I want an error handler that falls back on Latin-1 for anything which
cannot be decoded. Is this the right way to write it?
def latin1_fallback(exception):
assert isinstance(exception, UnicodeError)
start, end = exception.start, exception.end
I want an error handler that falls back on Latin-1 for anything which
cannot be decoded. Is this the right way to write it?
def latin1_fallback(exception):
assert isinstance(exception, UnicodeError)
start, end = exception.start, exception.end
obj = exception.object
if isinstance(
21 matches
Mail list logo