#25968: Don't ship invalid .py files; rename them at run-time
-------------------------------------+-------------------------------------
Reporter: lamby | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Core (Management | Version: 1.9
commands) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"abc0777b63057e2ff97eee2ff184356051e14c47" abc0777b]:
{{{
#!CommitTicketReference repository=""
revision="abc0777b63057e2ff97eee2ff184356051e14c47"
Fixed #25968 -- Changed project/app templates to use a "py-tpl" suffix.
Debian packages unconditionally byte-compile .py files on installation and
do not silence errors by design. Therefore, we need a way of shipping
these
invalid .py files without a .py extension but ensuring that when we
template them, they end up as .py.
We don't special-case .py files so that the all the TemplateCommand
command-line options (eg. extra_files and extensions) still work entirely
as expected and it may even be useful for other formats too.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25968#comment:3>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.58cd8c87215a2a44eac32298ede35363%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
