trevp at trevp.net
Tue Nov 21 18:32:42 PST 2017
Hey Piotr (offlist),
Makes sense to me - the strings/bytes stuff is unpleasant to deal
with, and perhaps you're right that the world is finally moving on...
I'm hoping we can collect a few people with interest in NoiseSocket
and interop soon - maybe at least you, David, and Alexey - and work
towards some useful things, but we still need to hammer that out. You
attending RWC, by any chance?
On Thu, Nov 16, 2017 at 11:32 AM, Piotr Lizończyk
<piotr.lizonczyk at gmail.com> wrote:
> Quick update about Python library - I won't be adding support for Python
> 2.7. I've ran into tons of issues while trying to do so, mostly related to
> differences in handling strings/bytes between Python 2 and 3 - resolution of
> which was far from trivial and elegant, plus couple more smaller problems.
> The decision is supported by the fact, that Python 2.7 won't be supported
> past 2020 and many of the biggest projects/libraries have already ceased to
> support Python 2 (e.g. Django) or are planning to do so (e.g. NumPy) in the
> following two years.
> I'll move my efforts from that task to implementing NoiseSocket now.
> I'll soon post a note about this in library's readme.
> Kind regards,
> 2017-11-02 4:22 GMT+01:00 Trevor Perrin <trevp at trevp.net>:
>> Hi all,
>> I've linked Piotr's "noiseprotocol" python library, and Nazar's
>> but that will be updated when the underlying Noise-C library is).
>> I think these libraries (and all our libraries!) could use more code
>> review, testing with other vectors, optimization and extension to
>> different crypto libraries, and so on.
>> But our language coverage is filling out nicely, so thanks Piotr and
>> Nazar for contributing!
>> Noise mailing list
>> Noise at moderncrypto.org
More information about the Noise