On 02/29/2012 09:07 PM, bhuztez wrote:
> IMHO, no extra support for them is required. Simply add support for
> PEP 302 importers, Django will find management commands in pyc/pyo
> files.
>
> I improved patch for #14087 weeks ago, which add support for PEP 302
> importers. I am just wondering why t
On 01/03/2012, at 12:07 PM, bhuztez wrote:
> I improved patch for #14087 weeks ago, which add support for PEP 302
> importers. I am just wondering why the core team did not even bother
> to review it.
>
This is covered in the FAQ on contributing to Django:
https://docs.djangoproject.com/en/1.3/
> I'm extremely strongly -1 on this. .pycs are a) an implementation detail,
> b) not even remotely a security tool, c) really just ship your source,
> having extra support for them is a waste of time IMO.
agreed.
> having extra support for them is a waste of time IMO.
IMHO, no extra support for
On Wed, Feb 29, 2012 at 6:56 PM, John Paulett wrote:
> Related tickets are #14952 and #12206. #14952 includes a possible
> patch, but marked as wontfix.
>
> However, I'm definitely +1 on adding support for pyc/pyo support for
> management commands. I understand the arguments against deploying
>
Related tickets are #14952 and #12206. #14952 includes a possible
patch, but marked as wontfix.
However, I'm definitely +1 on adding support for pyc/pyo support for
management commands. I understand the arguments against deploying
bytecode-only, but it seems to work everywhere in Django, except
Hi, django developers,
I think it would be useful to add *.pyc and *.pyo files into commands
list (not only *.py files). In my opinion firstly it have to search
for *.py files and add them, and then if there are other commands in
*.pyc or *.pyo files, add them too. It would be useful for example f
