You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Two days ago (June 17, 2024), PyPi has implemented a policy against "obfuscation techniques to hide or mask functionality."
I maintain some proprietary packages on PyPi that employ obfuscation to protect our intellectual property (e.g., betterbib). Our obfuscation is not intended to hide functionality though—in fact, I make an effort to document my packages thoroughly.
I assume this policy targets malicious practices, which do not apply to my packages. Therefore, I believe our practices comply with the new policy. I would appreciate confirmation of this and perhaps clarification within the policy.
This might also affect other proprietary packages like gurobipy, which "obfuscate" their source code by providing shared (compiled) libraries only, or by relaying their functionality to API calls.
The text was updated successfully, but these errors were encountered:
Two days ago (June 17, 2024), PyPi has implemented a policy against "obfuscation techniques to hide or mask functionality."
I maintain some proprietary packages on PyPi that employ obfuscation to protect our intellectual property (e.g., betterbib). Our obfuscation is not intended to hide functionality though—in fact, I make an effort to document my packages thoroughly.
I assume this policy targets malicious practices, which do not apply to my packages. Therefore, I believe our practices comply with the new policy. I would appreciate confirmation of this and perhaps clarification within the policy.
This might also affect other proprietary packages like gurobipy, which "obfuscate" their source code by providing shared (compiled) libraries only, or by relaying their functionality to API calls.
The text was updated successfully, but these errors were encountered: