Re: call_command; add *.pyc and *.pyo files to commands list

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/

Re: call_command; add *.pyc and *.pyo files to commands list

> 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

Re: call_command; add *.pyc and *.pyo files to commands list

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 >

Re: call_command; add *.pyc and *.pyo files to commands list

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

call_command; add *.pyc and *.pyo files to commands list

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

Generic edit generic views don't create `fail_silently` messages anymore.

Now deprecated generic create_update function based views (create_object, update_object, delete_object

Re: Error while importing URLconf 'permitprint.urls': day is out of range for month

On Wed, Feb 29, 2012 at 3:10 PM, furby wrote: > A site I built is breaking due to the leap year day, Feb. 29th.  The > error can be seen here: > > www.permitprint.com > > Any help resolving this would be appreciated.  I can't track down the > exception past the traceback. Do not post questions ab

Error while importing URLconf 'permitprint.urls': day is out of range for month

A site I built is breaking due to the leap year day, Feb. 29th. The error can be seen here: www.permitprint.com Any help resolving this would be appreciated. I can't track down the exception past the traceback. Traceback (most recent call last): File "/home/nolenjb/django/django_src/django/cor

Re: Jquery library update in django 1.4

On Wed, Feb 29, 2012 at 4:41 AM, Ric wrote: > hi, is it possibile to upgrade the jquery library in admin to the > lastest version with the now django 1.4? > > for what i've seen there is just one little bug when you use the > select all checkbox in admin changelist, all other javascript works > ou

Re: make the File Storage API works with a file-like object instead of the Django File object.

Allright, thank you, I will follow this django ticket then. On 29 fév, 01:21, Paul McMillan wrote: > This ticket is related to the issue: > > https://code.djangoproject.com/ticket/16946 > > -Paul > > > > > > > > On Tue, Feb 28, 2012 at 3:29 PM, Jonathan French > wrote: > > You can create a Dja

Re: Jquery library update in django 1.4

As we're already past feature freeze, changing the bundled copy of jQuery would require that there be a show stopping bug or some truly exceptional benefit. Absent both of these, updates like this will have to wait for the 1.5 cycle. I On Feb 29, 2012, at 9:42, Ric wrote: > hi, is it possibile