[BUG] --recursive bug, configs bug and code sign #1361
Unanswered
pauloswear
asked this question in
Q&A
Replies: 3 comments 3 replies
-
They're not bug, but work as designed, please check |
Beta Was this translation helpful? Give feedback.
2 replies
-
It's different from Pyarmor 7.x |
Beta Was this translation helpful? Give feedback.
1 reply
-
#UP Every script has this signature, don't want to send script with this. How to remove this: (Again, nothing on docs) Pyarmor 8.4.2 (pro), VAX, ***, 2023-11-01T15:16:51.450360 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello Jondy. There is some bugs happening here.
--recursive does not obfuscate all files., Actually, the behaviour is the same as using --exact
The .pyarmor folder that contains config it's not been updated when I use new configs (pyarmor cfg). It would be good if there's an option to remove folder after run CLI
Pyarmor gen always include pyarmor mark in output file and we can't disable it.
Example:
Pyarmor 8.2.9 (pro), VAX, DATETIME
Thanks
Beta Was this translation helpful? Give feedback.
All reactions