Re: Python plugins provided as compiled *.PYC files?
I just tried it. It doesn't work with all files being *.pyc. The main plugin file must be provided as source (*.py). I could live with that.
The reason I am asking is that I have created a plugin that exports the model to JPA-annotated entity classes and I would like to make the plugin available to the public, OTOH I want to keep the sources private, at least for now, until I have decided what to finally do with the whole thing.
So the question now comes down to:
If I provide *.pyc files compiled by WB's Python implementation, will anybody downloading these files be able to decompile the files to reconstruct the sources, that is including class names, method names, variable names etc. so that the actual meaning becomes clear?
Karsten
Subject
Views
Written By
Posted
1449
March 09, 2015 09:51AM
692
March 10, 2015 01:18AM
551
March 10, 2015 11:03AM
509
March 10, 2015 03:16PM
Re: Python plugins provided as compiled *.PYC files?
746
March 10, 2015 04:27PM
573
March 10, 2015 04:51PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.