New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ray/Cloudpickle/dis issue with Pyarmor #231
Comments
Thanks for your report in details, it's great. I found the problem in the traceback,
Here One solution is to obfuscate the scripts with |
Hi @jondy Thanks for you quick reply! |
One simple way is to patch
|
Are there other ways? |
It also could create a project to build this package in the script:
|
I'm trying to use the above snippet, but seems my code is not obfuscated at all. I assume I need an alternative for the I've tried different ways of setting
|
Maybe it's better to apply this patch d5ad20d |
Looks great! Will this be in a release anytime soon? Then I rather wait for a release instead of hacking around now :) |
It may releases in a couple of weeks, I'm developing another feature, and plan to release a minor version with this new feature, I'm not sure the exact date. |
Ok thanks a lot!! |
Hi
I'm trying to run obfuscated python packages via ray (https://github.com/ray-project/ray/).
I got however stuck on this line: https://github.com/ray-project/ray/blob/master/python/ray/function_manager.py#L118 which uses the python
dis
package.I was trying to create a minimal example to reproduce the issue, but then I got stuck on https://github.com/ray-project/ray/blob/master/python/ray/cloudpickle/cloudpickle.py#L440.
So it seems both Ray and Cloudpickle are incompatible with Pyarmor because they are using
dis
.Method to reproduce the
dis
issue with cloudpickle:simple_example.py
->
pyarmor obfuscate simple_example.py
dist/run_example.py
python dist/run_example.py
Error traceback
Method to reproduce the
dis
issue with ray:simple_example.py
->
pyarmor obfuscate simple_example.py
dist/run_example.py
python dist/run_example.py
Error traceback
Is there a way to overcome this?
Best regards, Pieterjan
The text was updated successfully, but these errors were encountered: