#14952: New find_commands(management_dir) to support .pyc and .pyo
-------------------------------+--------------------------------------
Reporter: lgx@… | Owner: nobody
Type: Uncategorized | Status: closed
Component: Core (Other) | Version: 1.2
Severity: Normal | Resolution: wontfix
Keywords: find_commands | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by russellm):
I can appreciate the situation you're in here, but @carljm's point is
entirely valid - PYC files aren't "compiled python" (or, at least, they
shouldn't be treated like that). They're a cache of the runtime operation
of a language interpreter -- an artefact that varies between language
implementations and versions.
In this case, what you're faced with are legal requirements, rather than
technical ones. If Brazilian law specifically uses words like
"executable", then whoever drafted the law clearly didn't anticipate
dynamic languages like Python. While this is unfortunate, it's
unreasonable to expect us to modify the project to accommodate a non-
recommended use of Python just to satisfy your interpretation of a
Brazilian legal requirement.
In the short term, I'd suggest trying to work around the law. Get legal
advice about *exactly* what must be signed in order to be compliant. Have
you actually got legal advice that declares that in the case of Python,
the .pyc file *is* the executable? I'm not a lawyer, and I have no
familiarity with the PAF-ECF law, but if it says you need to sign the
"executable", then is there any scope for you to sign the *Python*
executable and say you've met your requirement? Could you sign the .py
file, on the grounds that *it* is the executable? Could you sign an egg
file that contains the source code? These are all questions that you'd
need to get legal advice on to be certain, but from my past experience,
the way that an engineer chooses to interpret the law doesn't always match
the way that a lawyer or judge would consider compliant usage.
In the longer term, work to fix the law. Work with your representatives to
get the wording altered in a way that is compatible with dynamic
languages. This is the industry you work in, so you need to take an
interest when governments start passing boneheaded laws that don't match
industry practice.
--
Ticket URL: <https://code.djangoproject.com/ticket/14952#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
