#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
-------------------------------------+-------------------------------------

Comment (by Tim Graham <timograham@…>):

 In [changeset:"3306106fb1ce610e0961ce319a98e33c93795c1f" 3306106]:
 {{{
 #!CommitTicketReference repository=""
 revision="3306106fb1ce610e0961ce319a98e33c93795c1f"
 [1.9.x] 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.

 Backport of abc0777b63057e2ff97eee2ff184356051e14c47 from master
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/25968#comment:4>
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.e537fe21ab396e1855cf2c149a7c13c3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to