date:20180921

Re: [Django] #29711: Add system check to ensure uniqueness of admin actions' name.

2018-09-21 Thread Django

#29711: Add system check to ensure uniqueness of admin actions' __name__.
-+-
 Reporter:  Przemysław   |Owner:
  Buczkowski |  Przemysław Buczkowski
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Przemysław Buczkowski):

 The patch was modified.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.dab680a56f73b253736a0f32bfa398ae%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #29782: Better error message when filtering users with AnonymousUser

2018-09-21 Thread Django

#29782: Better error message when filtering users with AnonymousUser
-+-
   Reporter:  Sveder |  Owner:  nobody
   Type: | Status:  new
  Uncategorized  |
  Component:  Database   |Version:  2.1
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 When trying to filter a model with User ForeignKey on AnonymousUser, we
 get a cryptic:
 `Exception Value: int() argument must be a string or a number, not
 'AnonymousUser'`

 For example:
 https://stackoverflow.com/questions/3439709/how-to-cater-for-
 anonymoususer-when-filtering-based-on-user

 I think this deserves a better error message, for example something like:
 `ValueError("Can't filter User field with AnonymousUser")`.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/049.7ab2ac5f0e9d5b0faaac5fef503564a6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29780: Using default UserModel in django.contrib.auth forms

2018-09-21 Thread Django

#29780: Using default UserModel in django.contrib.auth forms
-+-
 Reporter:  Marcelo Canina   |Owner:  (none)
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.auth |  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Can Sarıgöl):

 * owner:  Can Sarıgöl => (none)
 * status:  assigned => new


-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.98d759bd3711bd734b774f510601586a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29780: Using default UserModel in django.contrib.auth forms

2018-09-21 Thread Django

#29780: Using default UserModel in django.contrib.auth forms
-+-
 Reporter:  Marcelo Canina   |Owner:  Can
 Type:   |  Sarıgöl
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.auth |  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Can Sarıgöl):

 * status:  new => assigned
 * owner:  nobody => Can Sarıgöl


-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.95f7e43e94c94e6043b87593d94b31ad%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #29781: Typo in russian translation

2018-09-21 Thread Django

#29781: Typo in russian translation
-+
   Reporter:  lockie |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Uncategorized  |Version:  master
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+
 Hello.
 Russian translation for the reverse ManyToMany relation in admin (here:
 
https://github.com/django/django/blob/7b407c9e9439ee460bb7b3028993faead062e24f/django/conf/locale/ru/LC_MESSAGES/django.po#L670
 ) seems to have the typo, the plural for "Relationship" ("Связь") is
 "Связи", not "Связьи".

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/049.45688d2d3b516e2b242e57af7d9e4761%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29775: custom url converters are not picked up on reverse when part of included patterns with namespace

2018-09-21 Thread Django

#29775: custom url converters are not picked up on reverse when part of included
patterns with namespace
-+-
 Reporter:  Eric Brandwein   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  converter,   | Triage Stage:  Accepted
  namespace, reverse, include|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Eric Brandwein):

 Great!

 I personally was using the nested instance namespace to be able to use the
 subsubpatterns in two different includes. In my case, the application
 namespace of these was declared in another file, along with the
 subsubpatterns. So I think using it that way wasn't as weird as this one.

 BTW, I'm sorry for any grammar mistakes I may have had; English is not my
 first language :/

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.ed81a9bdce641d16f28fc2d39582a7cb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29780: Using default UserModel in django.contrib.auth forms

2018-09-21 Thread Django

#29780: Using default UserModel in django.contrib.auth forms
-+-
 Reporter:  Marcelo Canina   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.auth |  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Javier Buzzi):

 Looks like the tests all passed. I have an issue with it though, how to
 really test this? By the time the tests run the `UserChangeForm` has
 already been executed and the metaclass already did its thing so no matter
 how much you change the `AUTH_USER_MODEL` nothing will change.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.496864ecd42d20f9ba209c8ededeffda%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29780: Using default UserModel in django.contrib.auth forms

2018-09-21 Thread Django

#29780: Using default UserModel in django.contrib.auth forms
-+-
 Reporter:  Marcelo Canina   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.auth |  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Javier Buzzi):

 Created this PR really quickly to see if it passes all tests on the first
 go. https://github.com/django/django/pull/10424

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.5120c8694a3773a062d5ebb560bfb720%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #29780: Using default UserModel in django.contrib.auth forms

2018-09-21 Thread Django

#29780: Using default UserModel in django.contrib.auth forms
+
   Reporter:  Marcelo Canina|  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  contrib.auth  |Version:  2.1
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+
 In django.contrib.auth.forms.py we have the
 {{{
 UserModel = get_user_model()
 }}}

 but User model is used twice in: UserCreationForm and UserChangeForm in
 theirs `meta`
 {{{
 class UserChangeForm(forms.ModelForm):
 class Meta:
 model = User
 }}}


 I think above forms should use UserModel instead of User so there is no
 need to subclass them to use project's user model when using a custom User
 model.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.85fa79b92cc6f4e6146b9f640eb17b1d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28145: Django documention - MySQL database connector - PyMySQL for python 3 support

2018-09-21 Thread Django

#28145: Django documention - MySQL database connector -  PyMySQL for python 3
support
---+--
 Reporter:  kinganu|Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  1.11
 Severity:  Normal |   Resolution:  needsinfo
 Keywords:  mysql  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by pojda):

 Jumping into something old here, but I have to add some info: the
 mysqlclient lib you recommend is a pain to install on Mac or Windows,
 while **PyMysql works out of the box**.

 I had to use the same workaround mentioned on that stackoverflow post -
 which I don't like because I'm modifying Django's source and may cause
 trouble when upgrading.


 Cheers!

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.9763a442a554e9ff97096ab03a4a5cb1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29776: Pulling part of django.conf.settings from the database

2018-09-21 Thread Django

#29776: Pulling part of django.conf.settings from the database
---+--
 Reporter:  Sven R. Kunze  |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Core (Other)   |  Version:  master
 Severity:  Normal |   Resolution:  needsinfo
 Keywords:  settings database  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Sven R. Kunze):

 * status:  new => closed
 * resolution:   => needsinfo


-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.11ecce8e9c094298742bbbdcd6795745%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29776: Pulling part of django.conf.settings from the database

2018-09-21 Thread Django

Comment (by Carlton Gibson):

Searching mailing list for “dynamic settings” returns
[https://groups.google.com/forum/#!searchin/django-
developers/dynamic$20settings%7Csort:date a long list of historical
discussions] of this sort of suggestion. (Including dynamic app plugins
and everything else.)

At this point I think it’s fair to say it’s been considered, and rejected
as not feasible or worth the complications.

To push it forward I think it would require a proof-of-concept in the form
of a working thrid-party application. That those that have been attempted
in the past are abandoned—if that’s true across the board—should tell us
something. If you’re able to pick one up and make it work then a post to
django-developers discussing whether it could be brought into core would
be reasonable.

--
Ticket URL:
Django
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.e503844089d2a1cb49917d583a540ebb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29776: Pulling part of django.conf.settings from the database

2018-09-21 Thread Django

* status: closed => new
* resolution: wontfix =>

Comment:

See Django Packages Live Settings grid for examples.

I checked them out and any active one of these break compatibility :-(

{{{
from django.conf import settings # won't work anymore
}}}

for Email, your example

I don't see why Email should be special.

This isn’t something that would be added to core.

Which is unfortunate given the plethora of 3rd-party apps, including many
old betas. If you change your mind, I can contribute pull requests.

To me seems like a rather tiny but very core functionality (also enabling
dynamic plugin apps etc).

--
Ticket URL:
Django
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.6a2959d5a0cd54dbf6f8ee44e3556c48%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29775: custom url converters are not picked up on reverse when part of included patterns with namespace

2018-09-21 Thread Django

#29775: custom url converters are not picked up on reverse when part of included
patterns with namespace
-+-
 Reporter:  Eric Brandwein   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  converter,   | Triage Stage:  Accepted
  namespace, reverse, include|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * version:  2.1 => master
 * stage:  Unreviewed => Accepted


Comment:

 OK, yes. Good. The test case reproduces — thank you for that!

 (Adding the nested instance namespace `'instance-ns-base64'` for a nested
 include is a little strange no? But taking it out doesn't affect the test:
 removing it and reversing `second-layer-namespaced-base64:subsubpattern-
 base64` has exactly the same error.)

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.0275631dd2ea6053d192e11d368dec11%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23423: Integrate unaccent lookups in django.contrib.postgres

2018-09-21 Thread Django

#23423: Integrate unaccent lookups in django.contrib.postgres
-+-
 Reporter:  Thomas Chaumeny  |Owner:  Thomas
 |  Chaumeny
 Type:  New feature  |   Status:  closed
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Gabor Körber):

 well since this writing further research revealed, that postgres 9.6 has
 fixed the issue. so it's only valid for 9.5 series and lower. i am
 therefore not sure if its worth a new ticket.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.cf00486131cb5375c559c28d3beac56b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29711: Add system check to ensure uniqueness of admin actions' name.

[Django] #29782: Better error message when filtering users with AnonymousUser

Re: [Django] #29780: Using default UserModel in django.contrib.auth forms

Re: [Django] #29780: Using default UserModel in django.contrib.auth forms

[Django] #29781: Typo in russian translation

Re: [Django] #29775: custom url converters are not picked up on reverse when part of included patterns with namespace

Re: [Django] #29780: Using default UserModel in django.contrib.auth forms

Re: [Django] #29780: Using default UserModel in django.contrib.auth forms

[Django] #29780: Using default UserModel in django.contrib.auth forms

Re: [Django] #28145: Django documention - MySQL database connector - PyMySQL for python 3 support

Re: [Django] #29776: Pulling part of django.conf.settings from the database

Re: [Django] #29776: Pulling part of django.conf.settings from the database

Re: [Django] #29776: Pulling part of django.conf.settings from the database

Re: [Django] #29775: custom url converters are not picked up on reverse when part of included patterns with namespace

Re: [Django] #23423: Integrate unaccent lookups in django.contrib.postgres

15 matches

Site Navigation

Mail list logo

Footer information