Enforcing a max size for form field values read into memory (review/determination of next steps needed)

Hi, I think I will be able to make good on my promise to give all the tickets that were in the review queue on last Friday a review for 1.9, except for this one... https://code.djangoproject.com/ticket/21231 https://github.com/django/django/pull/3852 Mostly I am wondering if there any other

Re: Proposal to document the error on trying to import django in python 3.4.

I think a better use of time could be to update the docs to more strongly recommend virtualenv and discourage the use of `sudo pip install`. On Wednesday, September 9, 2015 at 10:17:48 AM UTC-4, Anjul Tyagi(geety) wrote: > > Thanks for all that information Nick, it helped me a lot. > > Yes, it

Re: Hide specific users from auth user model for non super users

On Wednesday, September 9, 2015 at 5:42:07 PM UTC+2, Xavier Palacín Ayuso wrote: > > I need hide a super admin's users from auth user model of Django of list > users template for a normal users or no super admin users. > Hi Xavier. This mailing list is for discussing the development of

Hide specific users from auth user model for non super users

I need hide a super admin's users from auth user model of Django of list users template for a normal users or no super admin users. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this

Re: Get current user in model signal pre_save

On Wed, Sep 9, 2015 at 4:11 PM, Xavier Palacín Ayuso wrote: > I want to collects current user in model signal pre_save, to prevent remove > super user permission to current super users. Hi Xavier. This mailing list is for discussing the development of django itself,

Get current user in model signal pre_save

I want to collects current user in model signal pre_save, to prevent remove super user permission to current super users. As I have now so I can not give administrative privileges to a normal user. from django.db.models.signals import pre_delete, pre_save, post_save from

Re: Proposal to document the error on trying to import django in python 3.4.

Thanks for all that information Nick, it helped me a lot. Yes, it will be a platform specific information but may be we can just mention it in the documentation, giving the users a hint. -Anjul -- You received this message because you are subscribed to the Google Groups "Django developers

Re: Proposal to document the error on trying to import django in python 3.4.

To make myself clear. I don't think we need to document this as it is not a django error. It is a Python error because the module was not installed correctly. Maybe there should be a mention of the difference for installation on Ubuntu (and other linux distros?). But this would be unusual for

Re: Proposal to document the error on trying to import django in python 3.4.

In which case you need to install it again with *pip3*. All the defaults in Ubuntu (Python, pip etc.) are focused on 2.7, you always need to append 3 if you want it to be *python3 *specific. For earlier versions of ubuntu this was because some core processes required python2.7 and would call

Re: Proposal to document the error on trying to import django in python 3.4.

yes, I installed django using *pip *and not* pip3.* -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: Proposal to document the error on trying to import django in python 3.4.

Can you show us how you installed django? More specifically, did you do *pip install django* and *pip3 install django* As it looks like you only install django for 2.7, and not for 3.4. - Nick. On Wednesday, September 9, 2015 at 2:51:07 PM UTC+1, Anjul Tyagi(geety) wrote: > > Hi everyone,

Re: URL Dispatcher

Marten, good to have you back in the fold. I'll leave the effort in your hands (phew!) - as before, let me know if I can help in any way. I'm fairly new to Django internals, so don't expect much! I can test, however, and help with docs somewhat (based on limited knowledge). Cheers, James On Sep

Proposal to document the error on trying to import django in python 3.4.

Hi everyone, I am new to django and wish to address the problem which I faced during the installation of django on Ubuntu 14.04. I had two versions of python installed before I installed django: python 2.7.6 and python 3.4. I installed django as per the steps given in the documentation. Now,

Re: Ability to migrate other applications

On Wednesday, September 9, 2015 at 9:21:43 PM UTC+10, Shai Berger wrote: > > > > On 9 בספטמבר 2015 13:29:58 GMT+03:00, Marten Kenbeek > wrote: > > > >> > >> The order of migrations isn't something which is local to this > >feature, it > >> is something which isn't

Re: Ability to migrate other applications

On 9 בספטמבר 2015 13:29:58 GMT+03:00, Marten Kenbeek wrote: > >> >> The order of migrations isn't something which is local to this >feature, it >> is something which isn't fixed (probably by design, correct me if I'm > >> wrong) and if it is not "the right way" to do

Re: Ability to migrate other applications

On Wednesday, 9 September 2015 12:29:59 UTC+2, Marten Kenbeek wrote: > > The order of migrations isn't something which is local to this feature, it >> is something which isn't fixed (probably by design, correct me if I'm >> wrong) and if it is not "the right way" to do it, maybe it should be

Re: Ability to migrate other applications

> > The order of migrations isn't something which is local to this feature, it > is something which isn't fixed (probably by design, correct me if I'm > wrong) and if it is not "the right way" to do it, maybe it should be part > of another issue. The order of migrations within a single app

Re: Ability to migrate other applications

> > if we change the code in Django that does order resolution even slightly > it could result in different operation orders or even different "final" > rendered models. The order of migrations isn't something which is local to this feature, it is something which isn't fixed (probably by

Re: URL Dispatcher

Hi James, Thanks for keeping this alive while I had some personal issues to sort out. I'll be working on this again, though I can use all the help I can get. As for the work that still needs to be done: - 3.1 is done, mostly as a proof-of-concept that can be found at

Re: Ability to migrate other applications

Say A.0002 and B.0001 are different leaf nodes for A.0001, and both alter the same field. Now, on a clean database, the order is pretty stable. If that order is A.0001, A.0002, B.0001, you'll always end up with the field from B.0001. This is also what the autodetector sees. If you first

Re: Making the test suite run faster

Le 8 sept. 2015 à 18:42, Michael Manfre a écrit : > > I agree with Shai. The database backend needs to be able to control this > feature. Yes, I'm implementing that. The feature will be opt-in for database backends. -- Aymeric. -- You received this message because you