On 2020/02/05 00:32, Alexander Bluhm wrote: > Hi, > > I would like to import a new library for the industrial network > protocol OPC UA. > > ok? > > Comment: > library implementation of OPC UA > > Description: > open62541 is an open source and free implementation of OPC UA (OPC > Unified Architecture) written in the common subset of the C99 and > C++98 languages. The library is usable with all major compilers > and provides the necessary tools to implement dedicated OPC UA > clients and servers, or to integrate OPC UA-based communication > into existing applications. > > Maintainer: Alexander Bluhm <[email protected]> > > WWW: https://open62541.org/ > > bluhm
Maybe worth @comment'ing the empty share/doc/open62541/open62541.html/ directory? Is there a reason to use share/open62541/examples rather than the standard i.e. share/examples/open62541? I don't think it's worth bytecode-compiling the tools. The main benefit of bytecode-compiling is to stop new pyc files from being created at runtime (iff the tools are run by a user with write access to the directory). But these are tied to the python version; since there's no executable in bin/ the user has to choose themselves whether to run them with python2 or python3, and if they pick "the other one" than the port was built with, it will still create pyc files. And ports isn't setup to allow bytecode- compiling with both py2+py3.
