Thank you all. I will go for containers. Will ask for more time based on all your inputs..
Thanks, Chandana On Tue, 2 Oct 2018, 11:22 dieter, <die...@handshake.de> wrote: > dieter <die...@handshake.de> writes: > > Chandana Pattanayak <chandana.pattana...@patterneffectslabs.com> writes: > >> I have a requirement to provide basic code protection for a module in > our > >> product suite. With python 3.6 the .pyc files are created under pycache > , > >> so if i remove the py file the module is not found anymore. > > ... > > Note that you can disassemble "*.pyc" files and gain > > quite some insight by this. Thus, the protection provided > > by not deploying the source files is basic indeed. > > You should also read "https://www.python.org/dev/peps/pep-3147/";. > It mainly explains why "pycache" has been introduced > but as a side effect, it points out a bondage between > the "*.pyc" files and the major Python version: it is very likely, > that a major Python version will not accept "*.pyc" files created > by another major Python version. > > -- > https://mail.python.org/mailman/listinfo/python-list > -- https://mail.python.org/mailman/listinfo/python-list
