date:20150613

Re: [Django] #24962: Objects with primary keys containing newlines do not get links to being edited in the admin list view

2015-06-13 Thread Django

#24962: Objects with primary keys containing newlines do not get links to being
edited in the admin list view
---+
 Reporter:  alito  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  1
---+
Changes (by timgraham):

 * needs_tests:  1 => 0


Old description:

> The admin list view of an object lists each object and does a
>
> reverse('admin:%s_%s_change' % (self.opts.app_label,
> self.opts.model_name), args=(quote(pk),),
> current_app=self.model_admin.admin_site.name)
>
> to assign a change url for each one, skipping the link if the reverse
> fails. The 'quote' function there escapes a whole bunch of characters so
> as not to confuse the url pattern matcher but it forgets to escape
> newline.
>
> Therefore, a model like this:
>
> class Name(models.Model):
>name = models.TextField(primary_key=True)
>
> with:
> n = Name('John')
> n.save()
> o = Name('Have a \n newline')
> o.save()
>
> will list a link for John, but no link for 'Have a
> newline'
>
> (The bug actually is triggered in quite a few other places in admin but
> the list view is the easiest one to see. I've attached some screenshots
> that I prepared earlier)
>
> Change is a 2-character change to quote \n as well (attached)

New description:

 The admin list view of an object lists each object and does a
 {{{
 reverse('admin:%s_%s_change' % (self.opts.app_label,
 self.opts.model_name), args=(quote(pk),),
 current_app=self.model_admin.admin_site.name)
 }}}
 to assign a change url for each one, skipping the link if the reverse
 fails. The 'quote' function there escapes a whole bunch of characters so
 as not to confuse the url pattern matcher but it forgets to escape
 newline.

 Therefore, a model like this:
 {{{
 class Name(models.Model):
name = models.TextField(primary_key=True)
 }}}
 with:
 {{{
 n = Name('John')
 n.save()
 o = Name('Have a \n newline')
 o.save()
 }}}

 will list a link for John, but no link for 'Have a newline'

 (The bug actually is triggered in quite a few other places in admin but
 the list view is the easiest one to see. I've attached some screenshots
 that I prepared earlier)

 Change is a 2-character change to quote \n as well (attached)

--

--
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/063.e5d555cce97aace955b9161b764ea649%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #24982: Split staticfiles tests into multiple files

2015-06-13 Thread Django

#24982: Split staticfiles tests into multiple files
+
   Reporter:  timgraham |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  contrib.staticfiles   |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  1 |  Easy pickings:  1
  UI/UX:  0 |
+
 Update [https://github.com/django/django/pull/3977 an existing pull
 request] per the comments.

--
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/052.daae3989536d497a04a9f8b3fcbac227%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24890: Add warning to collectstatic when static files have clashing names

2015-06-13 Thread Django

#24890: Add warning to collectstatic when static files have clashing names
-+-
 Reporter:  giuliettamasina  |Owner:
 |  giuliettamasina
 Type:  New feature  |   Status:  closed
Component:  contrib.staticfiles  |  Version:  master
 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
-+-
Changes (by Tim Graham ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"5304494585c58b0c9245ea9896a6d6122a8673a2" 53044945]:
 {{{
 #!CommitTicketReference repository=""
 revision="5304494585c58b0c9245ea9896a6d6122a8673a2"
 Fixed #24890 -- Added warning to collectstatic when static files have
 clashing names
 }}}

--
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/073.27cea628d9e8104ba89f23b4cb1e36b9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23004: Cleanse entries from request.META in debug views

2015-06-13 Thread Django

#23004: Cleanse entries from request.META in debug views
--+
 Reporter:  blueyed   |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by jrabbit):

 * cc: jrabbit (added)


--
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.8e68a0f72b92bcc6254ed72d112ea6cf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24971: Make startapp generate an apps.py

2015-06-13 Thread Django

#24971: Make startapp generate an apps.py
-+-
 Reporter:  timgraham|Owner:
 |  MounirMesselmeni
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 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
-+-
Changes (by timgraham):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1


Comment:

 I reviewed the [https://github.com/django/django/pull/4856 PR].

--
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.22b254f2aa4f351b6efab2ad998a65f6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24894: Add CURRENT_TIMESTAMP function to contrib.postgres

2015-06-13 Thread Django

#24894: Add CURRENT_TIMESTAMP function to contrib.postgres
-+-
 Reporter:  adamchainz   |Owner:
 |  adamchainz
 Type:  New feature  |   Status:  new
Component:  contrib.postgres |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Accepted => Ready for checkin


--
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/068.d7b69dc539984d18c897e09e08e630cc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24978: Can't load fixtures with '[' and ']' in path

2015-06-13 Thread Django

#24978: Can't load fixtures with '[' and ']' in path
-+-
 Reporter:  mkow |Owner:  MoritzS
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  1.8
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  square brackets  | Triage Stage:  Accepted
  fixture path not found |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * status:  closed => new
 * has_patch:  1 => 0
 * resolution:  fixed =>
 * easy:  1 => 0


Comment:

 Sorry, but the new test doesn't pass on Windows. Are you able to
 investigate?

--
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/062.5a3ed2f90fb7453532ae187ef88f71c2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24978: Can't load fixtures with '[' and ']' in path

2015-06-13 Thread Django

#24978: Can't load fixtures with '[' and ']' in path
-+-
 Reporter:  mkow |Owner:  MoritzS
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.8
  commands)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  square brackets  | Triage Stage:  Accepted
  fixture path not found |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"98df288ddaba9787e4a370f12aba51c2b9133142" 98df288]:
 {{{
 #!CommitTicketReference repository=""
 revision="98df288ddaba9787e4a370f12aba51c2b9133142"
 Fixed #24978 -- Escaped special characters in loaddata fixture paths
 }}}

--
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/062.b2855e9fa0111091c22e81c522c85fec%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24981: Importing an abstract model from a bare package fails.

2015-06-13 Thread Django

#24981: Importing an abstract model from a bare package fails.
---+--
 Reporter:  skorokithakis  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.8
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by skorokithakis):

 Thank you, I'll just upgrade to 1.8!

--
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.28222d3cc6509090d65105d0f586b609%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24981: Importing an abstract model from a bare package fails.

2015-06-13 Thread Django

#24981: Importing an abstract model from a bare package fails.
---+--
Reporter: skorokithakis |Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 1.8
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 |UI/UX: 0
---+--
Changes (by timgraham):

* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0

Comment:

Based on the traceback, it looks like you're using Django 1.7. In Django
1.8 it looks like that `IndexError` is caught and you should get an error
message like 'Unable to detect the app label for model "%s." Ensure that
its module, "%s", is located inside an installed app.'" You might try
adding an explicit `Meta.app_label` to your abstract model. Feel free to
reopen if you continue to suspect a bug and can provide a sample project
running Django 1.8, as 1.7 is only receiving security updates at this
time. Thanks!

--
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.4d3f457c80055baef6e93595fae0e50f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24980: Calendar selector for DateField defaults to wrong date when timezone is missmatching

2015-06-13 Thread Django

#24980: Calendar selector for DateField defaults to wrong date when timezone is
missmatching
---+
 Reporter:  edruid |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.8
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+
Changes (by timgraham):

 * component:  Forms => contrib.admin
 * stage:  Unreviewed => Accepted


Comment:

 I can reproduce this.

--
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/064.eefa7288aa6c670a2e41bd91a6d415b6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24980: Calendar selector for DateField defaults to wrong date when timezone is missmatching

2015-06-13 Thread Django

#24980: Calendar selector for DateField defaults to wrong date when timezone is
missmatching
+--
 Reporter:  edruid  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  1.8
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  1
+--
Changes (by edruid):

 * Attachment "django_admin_calendar_missmatch.png" added.

 Missmatching date for text/calendar

--
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/064.a24ac5b28215c7e40f809843b2ac2328%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24980: Calendar selector for DateField defaults to wrong date when timezone is missmatching

2015-06-13 Thread Django

#24980: Calendar selector for DateField defaults to wrong date when timezone is
missmatching
+--
 Reporter:  edruid  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  1.8
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  1
+--

Comment (by edruid):

 There is a warning for the mismatching timezone.

 I'll attach an image displaying the problem.

 In this case the Member object has the sql row:
 {{{
  id | first_name | last_name | date_of_birth |email |
 gender
 ++---+---+--+
   1 | Eric   | Druid | 1983-11-20| eric.dr...@gmail.com | m
 }}}
 The problem is the preselected 1983-11-19 rather than 1983-11-20.

 It looks to me as if the javascript is converting the date (1983-11-20) in
 CEST as a timestamp (1983-11-20 00:00+2), then changing it to UTC
 (1983-11-19 22:00+0) and extracting the date (1983-11-19) and using that
 to mark the selected day.

--
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/064.23c02f3956bfc4a67fd128e7976d1f5b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #24981: Importing an abstract model from a bare package fails.

2015-06-13 Thread Django

#24981: Importing an abstract model from a bare package fails.
---+
 Reporter:  skorokithakis  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I have an abstract model called CharIDModel in
 myproject/utils/__init__.py. If I import it as "from utils import
 CharIDModel" and inherit from it, makemigrations crashes with:

 {{{
 Traceback (most recent call last):
   File "./manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/home/user/.virtualenvs/project/local/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 385, in
 execute_from_command_line
 utility.execute()
   File "/home/user/.virtualenvs/project/local/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 354, in execute
 django.setup()
   File "/home/user/.virtualenvs/project/local/lib/python2.7/site-
 packages/django/__init__.py", line 21, in setup
 apps.populate(settings.INSTALLED_APPS)
   File "/home/user/.virtualenvs/project/local/lib/python2.7/site-
 packages/django/apps/registry.py", line 108, in populate
 app_config.import_models(all_models)
   File "/home/user/.virtualenvs/project/local/lib/python2.7/site-
 packages/django/apps/config.py", line 202, in import_models
 self.models_module = import_module(models_module_name)
   File "/usr/lib/python2.7/importlib/__init__.py", line 37, in
 import_module
 __import__(name)
   File "/home/user/Code/Django/project/main/models.py", line 11, in
 
 from utils import dt_today, CharIDModel
   File "/home/user/Code/Django/project/utils/__init__.py", line 48, in
 
 class CharIDModel(models.Model):
   File "/home/user/.virtualenvs/project/local/lib/python2.7/site-
 packages/django/db/models/base.py", line 115, in __new__
 kwargs = {"app_label": package_components[app_label_index]}
 IndexError: list index out of range
 }}}

--
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/056.993582a0babb20e559115ea92e34ef47%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24941: Add get_exclude() hook to BaseModelAdmin

2015-06-13 Thread Django

#24941: Add get_exclude() hook to BaseModelAdmin
---+
 Reporter:  peterfarrell   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timgraham):

 * stage:  Unreviewed => Accepted


--
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/070.2476fa02b6efba6fc88bc072699c824e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24975: Prefetch_related from object directly

2015-06-13 Thread Django

#24975: Prefetch_related from object directly
-+-
 Reporter:  duduklein|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Unreviewed => Accepted


Comment:

 Conceptually, I don't see a request not to support something like this,
 although I'd be curious to know why assigning the query results to an
 intermediate variable isn't an acceptable solution. It would be helpful if
 you could post to the DevelopersMailingList in order to confirm what the
 API should look like and make sure there's no opposition to the idea in
 general.

--
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.aeea07fc58cd8598aa881c85383b925a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17122: Admin widgets and forms do not support custom model fields that store non-unicode data in the database to be the primary key referenced by relation fields.

2015-06-13 Thread Django

#17122: Admin widgets and forms do not support custom model fields that store 
non-
unicode data in the database to be the primary key referenced by relation
fields.
-+
 Reporter:  nickname123  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.3
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by claudep):

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


Comment:

 Considering that `UUIDField` is now part of Django and that the admin
 seems to work fine with it, I'm closing the 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/069.5bb04ce657f792a9c0a02d60c4927aca%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24972: Removing unique_together constraint makes migration fail on Django 1.8.2 with MySQL

2015-06-13 Thread Django

#24972: Removing unique_together constraint makes migration fail on Django 1.8.2
with MySQL
-+
 Reporter:  adambrenecki |Owner:  adambrenecki
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.8
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by timgraham):

 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted


--
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/070.9b82441cd4eb29bde68116c1d58df868%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24934: Can't drop or change unique_together index

2015-06-13 Thread Django

#24934: Can't drop or change unique_together index
+--
 Reporter:  user0007|Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.8
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by timgraham):

 Did you resolve the issue? (not sure why the ticket was marked "fixed").
 #24972 seems to report the same or similar issue.

--
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.7bfb839c1261d421e9adc8e51610149a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24976: admin.TabularInline custom form field header displaying as None on admin page

2015-06-13 Thread Django

#24976: admin.TabularInline custom form field header displaying as None on admin
page
---+
 Reporter:  kartikanand|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.8
 Severity:  Normal |   Resolution:
 Keywords:  TabularInline  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timgraham):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Accepted
 * easy:  1 => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


--
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/069.2e7470cc271f3100fb42284832aa4381%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24974: Cannot create subclass of form created by `modelform_factory()`, e.g. in `ModelAdmin.get_form()`

2015-06-13 Thread Django

#24974: Cannot create subclass of form created by `modelform_factory()`, e.g. in
`ModelAdmin.get_form()`
-+-
 Reporter:  mrmachine|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  form modelform   | Triage Stage:  Accepted
  modelform_factory modeladmin   |
  get_site metaclass |
  modelformmetaclass |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Unreviewed => Accepted


Comment:

 Discussion in #django-dev seemed to indicate that this is a problem we
 should solve.

--
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.ffbef7a33f575c59d9297f9ff184c4d7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24305: Allow to override abstract model fields

2015-06-13 Thread Django

#24305: Allow to override abstract model fields
-+-
 Reporter:  knbk |Owner:  knbk
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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
-+-
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 Chatted with Loic briefly and he indicated he didn't think the locking
 approach is an appropriate implementation. The approach also needs to
 integrate with the upcoming work on virtual fields, so it may take some
 time to sort that out.

--
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/062.f15ba739e3a17d1adf24c14dfd0ebaf3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24980: Calendar selector for DateField defaults to wrong date when timezone is missmatching

2015-06-13 Thread Django

* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0

Comment:

Your date field must default to `datetime.date.today()`. This value is
computed in the time zone you chose: `TIME_ZONE = 'UTC'`. You're seeing
the expected behavior.

Django doesn't automatically set the time zone based on the browser's time
zone for the reasons explained in the documentation:
https://docs.djangoproject.com/en/1.8/topics/i18n/timezones/#selecting-
the-current-time-zone

For date time fields, the admin displays a warning when the browser's time
zone doesn't match the server's time zone. Perhaps we should do this for
date fields as well.

--
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/064.2337692ebb53d52edb85026ffdd8ddaa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24979: Remove usage of inspect.getargspec()

2015-06-13 Thread Django

#24979: Remove usage of inspect.getargspec()
-+-
 Reporter:  timgraham|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

 * stage:  Accepted => Ready for checkin


--
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.1530f1a3c9310b262f7c0b917d68c10c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24977: Template variables with a value of None are considered to be == to non-existent properties

2015-06-13 Thread Django

#24977: Template variables with a value of None are considered to be == to non-
existent properties
-+-
 Reporter:  danielquinn  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Template system  |  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  string, if,  | Triage Stage:  Accepted
  equivalence|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


--
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/069.277ae318dc615a1c4cc446636e87c594%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17214: incorrect rendering of inline fk when parent has custom pk field

2015-06-13 Thread Django

#17214: incorrect rendering of inline fk when parent has custom pk field
-+-
 Reporter:  Aryeh Leib Taurog|Owner:  nobody
  |
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.3
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

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


Comment:

 I think that the addition of `from_db_value()` in Django 1.8 solves this
 issue.
 
https://docs.djangoproject.com/en/1.8/ref/models/fields/#django.db.models.Field.from_db_value

 Here's what would be a functional `TZDateField` definition:
 {{{
 class TZDateField(models.DateField):
 description = "Date field stored in PostgreSQL as TIMESTAMP WITH TIME
 ZONE"

 def db_type(self, connection):
 return "TIMESTAMP WITH TIME ZONE"

 def from_db_value(self, value, expression, connection, context):
 if value is not None:
 return self.to_python(value)
 return value
 }}}

--
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/095.8bb89fedad7f4870bf4f6d0c486b205e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #24980: Calendar selector for DateField defaults to wrong date when timezone is missmatching

2015-06-13 Thread Django

#24980: Calendar selector for DateField defaults to wrong date when timezone is
missmatching
+
Reporter: edruid | Owner: nobody
Type: Bug | Status: new
Component: Forms |Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 1
+
I have a server set to the time zone UTC and my browser set to CEST
(UTC+2). The calendar helper will display the date before the selected one
for date fields.

Steps to reproduce:
1. Set TIME_ZONE = 'UTC' in settings.py
2. Set timezone of local machine (where the browser is run from) to CEST
3. Create a DateField that is printed in a form on an object
4. Create an object
5. View the objects interface, open the calendar js helper and notice that
the selected date is the day before what is printed in the input box.

This is repeatable without saving the object, just select a different date
and reopen the calendar and the date before the one clicked is used.

This is tested using python 2.7.6, django 1.8 using Chromium 43.0.2357.81

--
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.73c01056911b01e93b3d31456025ccc4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24979: Remove usage of inspect.getargspec()

2015-06-13 Thread Django

#24979: Remove usage of inspect.getargspec()
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Utilities |  Version:  master
 Severity:  Normal|   Resolution:
 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 timgraham):

 [https://github.com/django/django/pull/4846 PR] which implements option 3.

--
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.b833b775f4a48ba870d1dd8732f33dd8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #24979: Remove usage of inspect.getargspec()

2015-06-13 Thread Django

#24979: Remove usage of inspect.getargspec()
+
   Reporter:  timgraham |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Utilities |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 `inspect.getargspec()` was deprecated in Python 3.0 and will be removed in
 3.6 (ETA late 2016). It started throwing a deprecation warning in Python
 3.5 which causes some test failures when we check the number of
 deprecation warnings so I'd like to deal with it now and avoid introducing
 more usages.

 Its replacement is `inspect.signature()` which is in all the versions of
 Python 3 we support, but not 2.7. Options I see:
 1. Add a dependency for the [https://github.com/aliles/funcsigs funcsigs
 backport] (only needed on Python 2)
 2. Vendor funcsigs in django.utils (about 1k LOC) (this has been the
 historical approach)
 3. Write different code for Python 2 & 3

 [https://groups.google.com/d/topic/django-
 developers/NZskysjasx8/discussion discussion on django-developers] about
 what option to use.

--
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/052.230a6d8803dac53ba5b03f936cc9ef78%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20577: Make prefetch_related faster by lazily creating related querysets

2015-06-13 Thread Django

#20577: Make prefetch_related faster by lazily creating related querysets
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 karyon):

 fyi, i can still observe this behavior. the profile looks pretty similar.
 using the Prefetch object didn't change anything.

--
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.148e3644eb60e8c30c9a83b20c50e1ad%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24971: Make startapp generate an apps.py

2015-06-13 Thread Django

#24971: Make startapp generate an apps.py
-+-
 Reporter:  timgraham|Owner:
 |  MounirMesselmeni
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by MounirMesselmeni):

 * owner:  nobody => MounirMesselmeni
 * status:  new => assigned


--
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.082a7560d21409a078643fe7caef4e98%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24203: Optimisation: adding multiple fields to same model should attempt to run single ALTER TABLE statement

2015-06-13 Thread Django

#24203: Optimisation: adding multiple fields to same model should attempt to run
single ALTER TABLE statement
-+-
 Reporter:  peterlauri   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  migration| Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by ambivalentno):

 Regarding timings:
 InnoDB table with 2 mln entries (but lots of big TextFields).
 It takes ~3 hours to add a single field, and also ~3 hours to add multiple
 fields in case they're grouped via single sql statement. Actually, most of
 time it takes to perform a migration mysql copies data to temporary table.

--
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/068.76a437ec1ac5d4873ddb6d2b0c506ef8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24972: Removing unique_together constraint makes migration fail on Django 1.8.2 with MySQL

2015-06-13 Thread Django

#24972: Removing unique_together constraint makes migration fail on Django 1.8.2
with MySQL
--+
 Reporter:  adambrenecki  |Owner:  adambrenecki
 Type:  Bug   |   Status:  assigned
Component:  Migrations|  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by adambrenecki):

 Replying to [comment:2 shaib]:
 > #24934 seems to describe the same problem and was marked as fixed. Can
 you please check against master?
 >

 Same problem on master for me.

--
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/070.64ac34f52f36ab483f8d77c2d7101e04%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #12464: Empty PATH_INFO causes blank SCRIPT_NAME

2015-06-13 Thread Django

#12464: Empty PATH_INFO causes blank SCRIPT_NAME
---+-
 Reporter:  chrisw |Owner:  wogan
 Type:  Bug|   Status:  closed
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:  duplicate
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by knbk):

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


Comment:

 Fixed in 336512fae77ec214ad6db24166b9a8676007cc09 / duplicate of #23173.

--
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/064.5e2814d48bc271e16da2892c3c6c133d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24962: Objects with primary keys containing newlines do not get links to being edited in the admin list view

2015-06-13 Thread Django

#24962: Objects with primary keys containing newlines do not get links to being
edited in the admin list view
---+
 Reporter:  alito  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  1
---+

Comment (by alito):

 I don't know almost anything about regression tests but I've attached my
 naive attempt

--
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/063.c07d9e7a86ed2278d3332ac4cdf2d6e9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24962: Objects with primary keys containing newlines do not get links to being edited in the admin list view

2015-06-13 Thread Django

#24962: Objects with primary keys containing newlines do not get links to being
edited in the admin list view
---+
 Reporter:  alito  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  1
---+
Changes (by alito):

 * Attachment "djangoregression.txt" added.

 regressiontest

--
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/063.381d34c4eed3eb4bf782a709cadc31e3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24978: Can't load fixtures with '[' and ']' in path

2015-06-13 Thread Django

#24978: Can't load fixtures with '[' and ']' in path
-+-
 Reporter:  mkow |Owner:  MoritzS
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  1.8
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  square brackets  | Triage Stage:  Accepted
  fixture path not found |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by MoritzS):

 * owner:  nobody => MoritzS
 * status:  new => assigned
 * has_patch:  0 => 1


Comment:

 Added PR.

--
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/062.6ca191461a061f9d6331ac74495f521b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24977: Template variables with a value of None are considered to be == to non-existent properties

2015-06-13 Thread Django

#24977: Template variables with a value of None are considered to be == to non-
existent properties
-+-
 Reporter:  danielquinn  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Template system  |  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  string, if,  | Triage Stage:
  equivalence|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by MoritzS):

 That's actually how jinja2 does it.
 All undefined variables are an instance of `jinja2.Undefined` and `{% if
 foo.undefined_attr is none %}` evaluates to false.

--
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/069.35d84edc4cfd5205e70a13f3c75b45f7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

38 matches

Mail list logo