date:20140507

[Django] #22597: update the inlineformset_factory example to include extra

2014-05-07 Thread Django

#22597: update the inlineformset_factory example to include extra
--+---
 Reporter:  saurabh.hirani@…  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.6
 Severity:  Normal|   Keywords:  inlineformset
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+---
 Hi,

 >>> from django.forms.models import inlineformset_factory
 >>> BookFormSet = inlineformset_factory(Author, Book)
 >>> author = Author.objects.get(name='Mike Royko')
 >>> formset = BookFormSet(instance=author)

 should have

  BookFormSet = inlineformset_factory(Author, Book, extra=0)

 as deafult value of extra is 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.1ee110c37726b37eaa69a0b8daa2169a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22439: LiveServerTestCase handles error messages inconsistently

2014-05-07 Thread Django

#22439: LiveServerTestCase handles error messages inconsistently
--+
 Reporter:  jmbowman  |Owner:  jmbowman
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Testing framework |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by ramiro):

 As noted in a comment there. This would also solve issue #21227.

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

[django/django] bc82c0: [1.7.x] Restored site header text in password rese...

2014-05-07 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: bc82c0dbac33ced1a4d6953e8626236ae05af956
  
https://github.com/django/django/commit/bc82c0dbac33ced1a4d6953e8626236ae05af956
  Author: Ramiro Morales 
  Date:   2014-05-07 (Wed, 07 May 2014)

  Changed paths:
M django/contrib/admin/templates/admin/base_site.html

  Log Message:
  ---
  [1.7.x] Restored site header text in password reset view.

It's the one shown when the optional integration described in
https://docs.djangoproject.com/en/dev/ref/contrib/admin/#adding-a-password-reset-feature
is used.

Follow-up to commits 6f470650d0 and 1d42a86ec7, together they fix
different small UI regressions after a962286b74.

Refs #21293.

5ea34f3f86 from master.


-- 
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/536aed00224ab_18bb581d44120774%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21293: Some authentication-related templates are broken

2014-05-07 Thread Django

Comment (by Ramiro Morales ):

In [changeset:"bc82c0dbac33ced1a4d6953e8626236ae05af956"]:
{{{
#!CommitTicketReference repository=""
revision="bc82c0dbac33ced1a4d6953e8626236ae05af956"
[1.7.x] Restored site header text in password reset view.

It's the one shown when the optional integration described in
https://docs.djangoproject.com/en/dev/ref/contrib/admin/#adding-a
-password-reset-feature
is used.

Follow-up to commits 6f470650d0 and 1d42a86ec7, together they fix
different small UI regressions after a962286b74.

Refs #21293.

5ea34f3f86 from master.
}}}

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

[Django] #22596: revert select_related

2014-05-07 Thread Django

#22596: revert select_related
--+
 Reporter:  qcxhome@… |  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.5
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 In some complicated situation, a QuerySet is passed through several
 methods to construct the final QuerySet. In this case, it's useful for
 developers to revert previous select_related due to that is not necessary
 for the final query. Fox example, a QuerySet like following is passed to
 another method,

 {{{
 #!div style="font-size: 80%"
 {{{#!python
 # qs is constructed a little far from invocation to final_query
 qs = MyModel.objects.filter(...).select_related('author', 'priority')

 result = final_query(qs)
 }}}
 }}}

 only MyModel.summary field is required from the final query result.
 Definition of final_query would be

 {{{
 #!div style="font-size: 80%"
   {{{#!python
 def final_query(qs):
 return qs.only('summary')
   }}}
 }}}

 but, the select_related is also applied to the final QuerySet. With the
 ability this ticket is requesting, developers are able to revert all
 unnecessary related fields. It's much convenient.

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

[django/django] 5ea34f: Restored site header text in password reset view.

2014-05-07 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5ea34f3f86af307e1a1c02b49136f51a4f63da88
  
https://github.com/django/django/commit/5ea34f3f86af307e1a1c02b49136f51a4f63da88
  Author: Ramiro Morales 
  Date:   2014-05-07 (Wed, 07 May 2014)

  Changed paths:
M django/contrib/admin/templates/admin/base_site.html

  Log Message:
  ---
  Restored site header text in password reset view.

It's the one shown when the optional integration described in
https://docs.djangoproject.com/en/dev/ref/contrib/admin/#adding-a-password-reset-feature
is used.

Follow-up to commits 6f470650d0 and 1d42a86ec7, together they fix
different small UI regressions after a962286b74.

Refs #21293.


-- 
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/536aebe798612_247cc05d3c1432f0%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21293: Some authentication-related templates are broken

2014-05-07 Thread Django

Comment (by Ramiro Morales ):

In [changeset:"5ea34f3f86af307e1a1c02b49136f51a4f63da88"]:
{{{
#!CommitTicketReference repository=""
revision="5ea34f3f86af307e1a1c02b49136f51a4f63da88"
Restored site header text in password reset view.

It's the one shown when the optional integration described in
https://docs.djangoproject.com/en/dev/ref/contrib/admin/#adding-a
-password-reset-feature
is used.

Follow-up to commits 6f470650d0 and 1d42a86ec7, together they fix
different small UI regressions after a962286b74.

Refs #21293.
}}}

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

Re: [Django] #22595: LiveServerTestCase concurrency

2014-05-07 Thread Django

#22595: LiveServerTestCase concurrency
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.6
 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 timo):

 I'm not sure exactly what you're suggesting. Can you explain a bit more?
 There's the note at the bottom of the section you linked that seems like
 it might be related: "When using an in-memory SQLite database to run the
 tests, the same database connection will be shared by two threads in
 parallel."

 I'm not so sure about the advice to inherit from both `LiveServerTestCase`
 and `TestCase` either.

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

Re: [Django] #22563: Migration of admin.LogEntry.user fails.

2014-05-07 Thread Django

#22563: Migration of admin.LogEntry.user fails.
-+
 Reporter:  efrinut@…|Owner:  andrewgodwin
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-2
 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
-+

Comment (by andrewgodwin):

 Ah yes, you're right, it does occur even from scratch. Not sure how we can
 support that; I'll have to leave this one and ponder it. Swappable models
 are a right PITA and we might have to exclude them from migrations or
 something if it gets really bad.

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

Re: [Django] #22432: Switching model on an M2M field results in a broken db (no change to the automatic through table)

2014-05-07 Thread Django

#22432: Switching model on an M2M field results in a broken db (no change to the
automatic through table)
-+--
 Reporter:  melinath |Owner:  timo
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-beta-1
 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
-+--

Comment (by melinath):

 Blocking this one with an error makes sense, because it's a weird edge
 case (and probably shouldn't be done, honestly) but #22476 is related to
 changes to fields that *don't* affect the database (blank, help_text, etc)
 but still generate migrations) so it should probably still get fixed
 (IMO).

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

Re: [Django] #22563: Migration of admin.LogEntry.user fails.

2014-05-07 Thread Django

#22563: Migration of admin.LogEntry.user fails.
-+
 Reporter:  efrinut@…|Owner:  andrewgodwin
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-2
 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 melinath):

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


Comment:

 I get this error even if I *haven't* changed the value of AUTH_USER_MODEL.
 Even if I delete and regenerate the migrations.

 (Though I can't actually test the raw state of this bug due to #22325. In
 order to apply the migrations, I have to delete all the
 `migrations.swappable_dependency(settings.AUTH_USER_MODEL)` declarations.)

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

Re: [Django] #22476: Migrations fail to migrate m2m fields with custom through model.

2014-05-07 Thread Django

#22476: Migrations fail to migrate m2m fields with custom through model.
-+
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations, m2m  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by andrewgodwin):

 Alright, I'll make sure I cover that too; I suspect there's an easy fix
 where I can just ignore if the to and through properties match.

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

Re: [Django] #22476: Migrations fail to migrate m2m fields with custom through model.

2014-05-07 Thread Django

#22476: Migrations fail to migrate m2m fields with custom through model.
-+
 Reporter:  apollo13 |Owner:  andrewgodwin
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations, m2m  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by andrewgodwin):

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


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

Re: [Django] #22476: Migrations fail to migrate m2m fields with custom through model.

2014-05-07 Thread Django

#22476: Migrations fail to migrate m2m fields with custom through model.
-+
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations, m2m  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by marfire):

 Yes, it is exactly the same traceback (other than the model / field names,
 since I'm seeing this on an actual project). This is after making the lone
 `blank=True` change, and getting this single operation in the migrations
 file generated by `makemigrations`:

 {{{
 operations = [
 migrations.AlterField(
 model_name='question',
 name='tags',
 field=models.ManyToManyField(to=u'questions.Tag',
 through=u'questions.ContentTag', blank=True),
 ),
 ]
 }}}

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

Re: [Django] #22476: Migrations fail to migrate m2m fields with custom through model.

2014-05-07 Thread Django

#22476: Migrations fail to migrate m2m fields with custom through model.
-+
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations, m2m  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by andrewgodwin):

 Hm, that should be allowable - you're getting the exact same traceback as
 in the ticket description?

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

[django/django] 8eb51a: Insert space.

2014-05-07 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8eb51a8cf62bbbea2bbc776ea00ba08332151d92
  
https://github.com/django/django/commit/8eb51a8cf62bbbea2bbc776ea00ba08332151d92
  Author: Markus Amalthea Magnuson 
  Date:   2014-05-07 (Wed, 07 May 2014)

  Changed paths:
M docs/ref/settings.txt

  Log Message:
  ---
  Insert space.


  Commit: b57ee15b12aacf70ccd13ad301f7ebb51d19439f
  
https://github.com/django/django/commit/b57ee15b12aacf70ccd13ad301f7ebb51d19439f
  Author: Alex Gaynor 
  Date:   2014-05-07 (Wed, 07 May 2014)

  Changed paths:
M docs/ref/settings.txt

  Log Message:
  ---
  Merge pull request #2639 from alimony/patch-1

Insert space


Compare: https://github.com/django/django/compare/5a917cfef319...b57ee15b12aa

-- 
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/536ac53ddba59_1be3983d3410526e%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22476: Migrations fail to migrate m2m fields with custom through model.

2014-05-07 Thread Django

#22476: Migrations fail to migrate m2m fields with custom through model.
-+
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations, m2m  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by marfire):

 * cc: k@… (added)


Comment:

 I can reproduce this, and the M2M uses a through model both before and
 after. The ''only'' difference is the addition of `blank=True`. My
 understanding was that `blank` is used for form validation and doesn't
 affect the database at all. Am I missing something?

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

Re: [Django] #22595: LiveServerTestCase concurrency

2014-05-07 Thread Django

#22595: LiveServerTestCase concurrency
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.6
 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
---+--
Changes (by Wernight):

 * cc: werner@… (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/067.3b2607f67b74d99497d0a33aa996647d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22595: LiveServerTestCase concurrency

2014-05-07 Thread Django

#22595: LiveServerTestCase concurrency
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.6
 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
---+--
Changes (by Wernight):

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

[Django] #22595: LiveServerTestCase concurrency

2014-05-07 Thread Django

#22595: LiveServerTestCase concurrency
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I love the live tests but they run concurrently and it's no clearly
 written in the section:
 
https://docs.djangoproject.com/en/dev/topics/testing/tools/#django.test.LiveServerTestCase

 I know it's written for the basic tests. I'd suggest to include something
 like:

 Those tests run in parallel by default. If you need to change the
 database, consider inheriting from
 {{{django.test.LiveServerTestCase}}} as well as {{{django.test.TestCase}}}
 (see section above about TestCase).

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

Re: [Django] #22588: makemigrations and regexvalidators

2014-05-07 Thread Django

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

Comment:

@andrewgodwin, if you look at my patch, it sits on top of the fix from
#21638. this is not a duplicate.

[https://github.com/django/django/commit/a68f32579145dfbd51d87e14f9b5e04c770f9081
a68f32579145dfbd51d87e14f9b5e04c770f9081] compares regex pattern objects,
which i change to comparing their parameters. since a68f325 the regex
validator has also grown an `inverse_match` argument, which is ignored.
finally, you added `__eq__`, but no `__ne__` which means `assertNotEqual`s
don't work properly. please see the pr above

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

Re: [Django] #22594: Content Type framework does not trigger Cascade delete

2014-05-07 Thread Django

#22594: Content Type framework does not trigger Cascade delete
-+-
 Reporter:  JoseTomasTocino  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:   |  Version:  1.6
  contrib.contenttypes   |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by JoseTomasTocino):

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


Comment:

 Curiously, both pre_delete and post_delete signals are fired in the
 failing case... What happens in the middle?

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

Re: [Django] #22496: Data migrations are not transactional (except on Postgres)

2014-05-07 Thread Django

#22496: Data migrations are not transactional (except on Postgres)
-+
 Reporter:  shai |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  oracle mysql sqlite  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by Andrew Godwin ):

 In [changeset:"7f63ac5a9f0ed76d2e372a8c0fda95cce67e7170"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7f63ac5a9f0ed76d2e372a8c0fda95cce67e7170"
 [1.7.x] Fixed #22496: Data migrations get transactions again!
 }}}

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

Re: [Django] #22496: Data migrations are not transactional (except on Postgres)

2014-05-07 Thread Django

#22496: Data migrations are not transactional (except on Postgres)
-+
 Reporter:  shai |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  oracle mysql sqlite  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Andrew Godwin ):

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


Comment:

 In [changeset:"5a917cfef319df33ca30a3b27bd0b0533b8e63bb"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5a917cfef319df33ca30a3b27bd0b0533b8e63bb"
 Fixed #22496: Data migrations get transactions again!
 }}}

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

[django/django] 7f63ac: [1.7.x] Fixed #22496: Data migrations get transact...

2014-05-07 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 7f63ac5a9f0ed76d2e372a8c0fda95cce67e7170
  
https://github.com/django/django/commit/7f63ac5a9f0ed76d2e372a8c0fda95cce67e7170
  Author: Andrew Godwin 
  Date:   2014-05-07 (Wed, 07 May 2014)

  Changed paths:
M django/db/migrations/migration.py
M django/db/migrations/operations/base.py
M django/db/migrations/operations/special.py
M docs/ref/migration-operations.txt
M tests/migrations/test_operations.py

  Log Message:
  ---
  [1.7.x] Fixed #22496: Data migrations get transactions again!


-- 
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/536aa5bb89bd0_253f122bd38919a%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 5a917c: Fixed #22496: Data migrations get transactions aga...

2014-05-07 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5a917cfef319df33ca30a3b27bd0b0533b8e63bb
  
https://github.com/django/django/commit/5a917cfef319df33ca30a3b27bd0b0533b8e63bb
  Author: Andrew Godwin 
  Date:   2014-05-07 (Wed, 07 May 2014)

  Changed paths:
M django/db/migrations/migration.py
M django/db/migrations/operations/base.py
M django/db/migrations/operations/special.py
M docs/ref/migration-operations.txt
M tests/migrations/test_operations.py

  Log Message:
  ---
  Fixed #22496: Data migrations get transactions again!


-- 
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/536aa5ac3fba7_1f035c5d3c1161a9%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[Django] #22594: Content Type framework does not trigger Cascade delete

2014-05-07 Thread Django

#22594: Content Type framework does not trigger Cascade delete
--+
 Reporter:  JoseTomasTocino   |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  contrib.contenttypes  |Version:  1.6
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 I've posted this question in StackOverflow
 (http://stackoverflow.com/questions/23528296/djangos-content-type-
 framework-does-not-trigger-cascade-delete) and given it looks like a bug,
 I've decided to post it here.

 Suppose the following models:

 {{{#!python
 class DeltaCheck(models.Model):
 logs = generic.GenericRelation('Log')
 title = models.CharField(max_length=50)
 owner = models.ForeignKey(User)

 class Log(models.Model):
 title = models.CharField(max_length=50)

 content_type = models.ForeignKey(ContentType)
 object_id = models.PositiveIntegerField()
 content_object = generic.GenericForeignKey('content_type',
 'object_id')
 }}}

 If I create a DeltaCheck and a couple of Logs and then delete the
 DeltaCheck, the Logs are deleted as well:

 {{{
 In [7]: Log.objects.count()
 Out[7]: 10

 In [8]: DeltaCheck.objects.get().delete()

 In [9]: Log.objects.count()
 Out[9]: 0
 }}}

 BUT if I delete the User (the field owner), the DeltaCheck gets deleted
 BUT not the Logs, look:

 {{{
 In [14]: Log.objects.count()
 Out[14]: 10

 In [15]: DeltaCheck.objects.get().owner.delete()

 In [16]: DeltaCheck.objects.all()
 Out[16]: []

 In [17]: Log.objects.count()
 Out[17]: 10
 }}}

 Is that proper behavior? I don't think so.

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

Re: [Django] #22496: Data migrations are not transactional (except on Postgres)

2014-05-07 Thread Django

#22496: Data migrations are not transactional (except on Postgres)
-+
 Reporter:  shai |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  oracle mysql sqlite  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by andrewgodwin):

 My vote is that we definitely leave RunSQL as non-transactional on MySQL
 and Oracle (SeparateDatabaseAndState is a combiner, it should be left
 alone too).

 I also agree that we should have RunPython in a transaction, but have an
 argument to turn it off if you're doing schema changes on Oracle (the only
 know crash case I know of). I'll commit that now and mark this as fixed.

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

Re: [Django] #22432: Switching model on an M2M field results in a broken db (no change to the automatic through table)

2014-05-07 Thread Django

#22432: Switching model on an M2M field results in a broken db (no change to the
automatic through table)
-+--
 Reporter:  melinath |Owner:  timo
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-beta-1
 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
-+--

Comment (by andrewgodwin):

 This is a tricky one to fix. I'm tempted to just block any changes on M2M
 fields (for this and #22476) in 1.7 and ship it so that makemigrations
 dies saying "you can't alter M2Ms, if you want to change it delete and add
 a new one!", as there's no way we can write generic M2M alteration code in
 time, and it's not a regression, as you couldn't do any alteration at all
 before.

 Thoughts?

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

Re: [Django] #22588: makemigrations and regexvalidators

2014-05-07 Thread Django

#22588: makemigrations and regexvalidators
-+--
 Reporter:  leftmoose|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:  worksforme
 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 andrewgodwin):

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


Comment:

 This is a duplicate of the issue in #21638, and I've verified that on
 master it works as expected (I suspect, leftmoose, you're using the beta,
 where this wasn't fixed yet). Closing as WORKSFORME.

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

[django/django] e9a456: Fixed #22581: Pass default values for schema throu...

2014-05-07 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e9a456d11b5b63389b466ed435ef3915f0e79e4c
  
https://github.com/django/django/commit/e9a456d11b5b63389b466ed435ef3915f0e79e4c
  Author: Andrew Godwin 
  Date:   2014-05-07 (Wed, 07 May 2014)

  Changed paths:
M django/db/backends/schema.py
M django/db/backends/sqlite3/schema.py
M tests/schema/tests.py

  Log Message:
  ---
  Fixed #22581: Pass default values for schema through get_db_prep_save()


-- 
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/536a9bcf86402_1ad7fdfd40532cf%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22581: Field.get_default() causes migration to fail if non-string value returned

2014-05-07 Thread Django

#22581: Field.get_default() causes migration to fail if non-string value 
returned
-+
 Reporter:  martin.tirsel@…  |Owner:  andrewgodwin
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  migration| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by Andrew Godwin ):

 In [changeset:"d8bf415ab29ef3ef843286e69c646ebcce58c172"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d8bf415ab29ef3ef843286e69c646ebcce58c172"
 [1.7.x] Fixed #22581: Pass default values for schema through
 get_db_prep_save()
 }}}

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

Re: [Django] #22581: Field.get_default() causes migration to fail if non-string value returned

2014-05-07 Thread Django

#22581: Field.get_default() causes migration to fail if non-string value 
returned
-+
 Reporter:  martin.tirsel@…  |Owner:  andrewgodwin
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  migration| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by andrewgodwin):

 Turns out that akaariai was pretty correct; this was database-level
 directly, though it turns out this matches get_db_prep_save better (as
 that's for values that are saved rather than for queries, so it'll match
 better).

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

Re: [Django] #22581: Field.get_default() causes migration to fail if non-string value returned

2014-05-07 Thread Django

#22581: Field.get_default() causes migration to fail if non-string value 
returned
-+
 Reporter:  martin.tirsel@…  |Owner:  andrewgodwin
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  migration| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Andrew Godwin ):

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


Comment:

 In [changeset:"e9a456d11b5b63389b466ed435ef3915f0e79e4c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e9a456d11b5b63389b466ed435ef3915f0e79e4c"
 Fixed #22581: Pass default values for schema through get_db_prep_save()
 }}}

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

[django/django] d8bf41: [1.7.x] Fixed #22581: Pass default values for sche...

2014-05-07 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: d8bf415ab29ef3ef843286e69c646ebcce58c172
  
https://github.com/django/django/commit/d8bf415ab29ef3ef843286e69c646ebcce58c172
  Author: Andrew Godwin 
  Date:   2014-05-07 (Wed, 07 May 2014)

  Changed paths:
M django/db/backends/schema.py
M django/db/backends/sqlite3/schema.py
M tests/schema/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #22581: Pass default values for schema through 
get_db_prep_save()


-- 
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/536a9be29e02e_1abc1089d4011221a%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22534: Checks fail on non-swappable ForeignKeys when the related model is swapped out

2014-05-07 Thread Django

#22534: Checks fail on non-swappable ForeignKeys when the related model is
swapped
out
+
Reporter: bendavis78 |Owner: andrewgodwin
Type: Bug | Status: assigned
Component: Migrations | Version: 1.7-beta-2
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 andrewgodwin):

* severity: Release blocker => Normal

Comment:

Your parsing of what swappable means is incorrect; it's not for a
swappable model, it's for a model that might be swapped in in place of
that model. It won't allow you to access models that are swapped out, and
that _should_ fail the checks system immediately.

I'm bumping this down from release blocker as it's just a documentation
clarification and a missing test for the false side IMO (we didn't
implement Russ' plan exactly; from what I remember, the None option wasn't
necessary in the end due to the limited options migrations had dealing
with it).

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

Re: [Django] #22534: Checks fail on non-swappable ForeignKeys when the related model is swapped out

2014-05-07 Thread Django

#22534: Checks fail on non-swappable ForeignKeys when the related model is 
swapped
out
-+
 Reporter:  bendavis78   |Owner:  andrewgodwin
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-beta-2
 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 andrewgodwin):

 * owner:  nobody => andrewgodwin
 * 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/068.fa99de1b4db3e7922ee203780074f5c1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22563: Migration of admin.LogEntry.user fails.

2014-05-07 Thread Django

#22563: Migration of admin.LogEntry.user fails.
-+
 Reporter:  efrinut@…|Owner:  andrewgodwin
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-beta-2
 Severity:  Release blocker  |   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
-+

Comment (by Andrew Godwin ):

 In [changeset:"f67433e74b06bbeb9b6bba0a9db5fb33512bdb43"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f67433e74b06bbeb9b6bba0a9db5fb33512bdb43"
 [1.7.x] Fixed #22563: Better error message when trying to change
 AUTH_USER_MODEL

 You're not allowed to do this after you've made migrations; see ticket
 for more details.
 }}}

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

Re: [Django] #22563: Migration of admin.LogEntry.user fails.

2014-05-07 Thread Django

#22563: Migration of admin.LogEntry.user fails.
-+
 Reporter:  efrinut@…|Owner:  andrewgodwin
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-beta-2
 Severity:  Release blocker  |   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 Andrew Godwin ):

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


Comment:

 In [changeset:"fc974313b85da932a70f1f993b33207d78d31831"]:
 {{{
 #!CommitTicketReference repository=""
 revision="fc974313b85da932a70f1f993b33207d78d31831"
 Fixed #22563: Better error message when trying to change AUTH_USER_MODEL

 You're not allowed to do this after you've made migrations; see ticket
 for more details.
 }}}

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

[django/django] f67433: [1.7.x] Fixed #22563: Better error message when tr...

2014-05-07 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: f67433e74b06bbeb9b6bba0a9db5fb33512bdb43
  
https://github.com/django/django/commit/f67433e74b06bbeb9b6bba0a9db5fb33512bdb43
  Author: Andrew Godwin 
  Date:   2014-05-07 (Wed, 07 May 2014)

  Changed paths:
M django/db/migrations/state.py

  Log Message:
  ---
  [1.7.x] Fixed #22563: Better error message when trying to change 
AUTH_USER_MODEL

You're not allowed to do this after you've made migrations; see ticket
for more details.


-- 
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/536a922093652_1ccf1071d442888a%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] fc9743: Fixed #22563: Better error message when trying to ...

2014-05-07 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: fc974313b85da932a70f1f993b33207d78d31831
  
https://github.com/django/django/commit/fc974313b85da932a70f1f993b33207d78d31831
  Author: Andrew Godwin 
  Date:   2014-05-07 (Wed, 07 May 2014)

  Changed paths:
M django/db/migrations/state.py

  Log Message:
  ---
  Fixed #22563: Better error message when trying to change AUTH_USER_MODEL

You're not allowed to do this after you've made migrations; see ticket
for more details.


-- 
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/536a920cc5e83_1e44edbd4041023%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22563: Migration of admin.LogEntry.user fails.

2014-05-07 Thread Django

Comment (by andrewgodwin):

This is actually expected; migrations don't supporting changing
AUTH_USER_MODEL (or any swappable model) after you've made an initial
migration, and this has always been the intention, but before that commit
we were leaking the state enough that it worked (though it would have had
bugs).

The key problem here is that AUTH_USER_MODEL directly affects ForeignKeys
and relationships but exists outside of the model history - and because
it's not versioned, changing it means the migrations get all broken. The
fix is to delete all migrations and restart from scratch if you change
AUTH_USER_MODEL; there's no other way of guaranteeing your database is
correct.

I'll update the error message to detect if the missing model is
AUTH_USER_MODEL and tell this to the user.

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

Re: [Django] #22568: FK to proxy model breaks migrate

2014-05-07 Thread Django

#22568: FK to proxy model breaks migrate
+--
 Reporter:  leftmoose   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7-beta-2
 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
+--

Comment (by leftmoose):

 what's the criteria for release blockers? this breaks foreign keys to
 proxy models...

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

Re: [Django] #901: Reload method for models

2014-05-07 Thread Django

#901: Reload method for models
-+-
 Reporter:  andreas@…|Owner:  adrian
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by carbonXT):

 * cc: mike@… (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/080.537d3581ef3535530e85a0ea55cbfd6f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22593: ABout the locale paths

2014-05-07 Thread Django

#22593: ABout the locale paths
---+--
 Reporter:  lushizhao@…|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:  invalid
 Keywords:  i18n,locale_paths  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timo):

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


Comment:

 https://code.djangoproject.com/wiki/TicketClosingReasons/UseSupportChannels

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

Re: [Django] #22592: AbstractBaseUser.str may return non-string (None)

2014-05-07 Thread Django

#22592: AbstractBaseUser.__str__ may return non-string (None)
+--
 Reporter:  david.fischer.ch@…  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  contrib.auth|  Version:  master
 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 timo):

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


Comment:

 Right, a `__str__()` method must return a string, not `None`. I'm still
 not convinced what you are doing merits a change to Django as a username
 of `None` doesn't seem to make sense (could you just as easily use an
 empty string instead?). Please reopen with further justification is you
 disagree.

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

Re: [Django] #16877: documentation code blocks cropped on mobile browsers

2014-05-07 Thread Django

#16877: documentation code blocks cropped on mobile browsers
-+
 Reporter:  dardub@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  *.djangoproject.com  |  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 mardini):

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


Comment:

 I tried to reproduce on several mobile devices/browsers, but it looks like
 the issue is fixed now, maybe because of how modern mobile browsers
 matured.

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

Re: [Django] #22470: Migrations fail with order_with_respect_to and ForeignKey to self

2014-05-07 Thread Django

#22470: Migrations fail with order_with_respect_to and ForeignKey to self
-+-
 Reporter:  Jonas|Owner:
 Type:  Bug  |  andrewgodwin
Component:  Migrations   |   Status:  assigned
 Severity:  Release blocker  |  Version:
 Keywords:  migrations   |  1.7-beta-1
  order_with_respect_to  |   Resolution:
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by andrewgodwin):

 Hmm, that might be possible - we could replace the AddField(ForeignKey)
 with AddField(IntegerField) (or whatever the underlying type is) and then
 have the second thing be the AlterField to a ForeignKey. I'll try that
 approach.

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

Re: [Django] #22592: AbstractBaseUser.str may return non-string (None)

2014-05-07 Thread Django

#22592: AbstractBaseUser.__str__ may return non-string (None)
+--
 Reporter:  david.fischer.ch@…  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.auth|  Version:  master
 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 david.fischer.ch@…):

 Calling str(instance) is what triggered the faulty code.

 I guess Python 3 does not allow implementing a __str__ method that
 something that is not an instance of str.


 {{{
 david@n750jv:~$ python3
 Python 3.4.0 (default, Apr 11 2014, 13:05:11)
 [GCC 4.8.2] on linux
 Type "help", "copyright", "credits" or "license" for more information.
 >>> str(None)
 'None'
 >>> class Test(object):
 ...  def __str__(self):
 ...   return None
 ...
 >>> Test()
 <__main__.Test object at 0x7fd076e4f860>
 >>> str(Test())
 Traceback (most recent call last):
   File "", line 1, in 
 TypeError: __str__ returned non-string (type NoneType)
 >>>

 }}}

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

[Django] #22593: ABout the locale paths

2014-05-07 Thread Django

#22593: ABout the locale paths
---+---
Reporter: lushizhao@…| Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized |Version: 1.6
Severity: Normal | Keywords: i18n,locale_paths
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
---+---
I want to make a django.po in the root of the project( contains all model
and templates )
in my settings.py

LOCAL_PATHS = (
'/path/to/project/locale/',
)
but it doesn't work.and here is my project structure. It seems the
django.po cannot be recognized.

project/
-app/
-app/
-project/
-settings.py
-urls.py
-templates/
-static/
-locale/

then i put the locale directory under an app directory and use the
makemessages tool,
it works. But it only contains the translation which marked in this app,
which means I can't make the translations that marked in templates or
other apps.
So is there any better solution for this situation?

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

Re: [Django] #22592: AbstractBaseUser.str may return non-string (None)

2014-05-07 Thread Django

#22592: AbstractBaseUser.__str__ may return non-string (None)
+--
 Reporter:  david.fischer.ch@…  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.auth|  Version:  master
 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
+--
Changes (by timo):

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


Comment:

 Doesn't look like a bug in Django to me... the exception is thrown by
 `cloudncode_base/models/signals.py`. Am I missing something?

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

[Django] #22592: AbstractBaseUser.str may return non-string (None)

2014-05-07 Thread Django

#22592: AbstractBaseUser.__str__ may return non-string (None)
+
 Reporter:  david.fischer.ch@…  |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  contrib.auth|Version:  master
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 Tested under Python 3.

 I am writing unit-tests to ensure my custom signal handler works well.
 The signal handler is registered to pre_save with sender=AUTH_USER_MODEL
 and it calls str(instance).

 In one of the tests I set user's username to None and save the model, ...

 user = User.objects.create(username='sam.fisher', first_name='Sam',
 last_name='Fisher', password='i_am_the_boss')

 user.username = None
 user.save()

 pre_save signal handler:

 ...
 str(instance)
 ...

 Traceback (most recent call last):
   File
 "/home/ubuntu/cloudncode_test/server/cloudncode_base/tests/test_models.py",
 line 44, in test_strip_none_works
 self.user.save()
   File
 "/home/ubuntu/cloudncode_test/venv/src/django/django/db/models/base.py",
 line 602, in save
 force_update=force_update, update_fields=update_fields)
   File
 "/home/ubuntu/cloudncode_test/venv/src/django/django/db/models/base.py",
 line 626, in save_base
 update_fields=update_fields)
   File
 "/home/ubuntu/cloudncode_test/venv/src/django/django/dispatch/dispatcher.py",
 line 198, in send
 response = receiver(signal=self, sender=sender, **named)
   File
 "/home/ubuntu/cloudncode_test/server/cloudncode_base/models/signals.py",
 line 55, in strip_strings_and_validate_model
 i = str(instance)
 TypeError: __str__ returned non-string (type NoneType)

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

Re: [Django] #18517: URLField does not support url with underscore

2014-05-07 Thread Django

Comment (by shai):

Replying to [comment:5 slaughninja]:
> If the Django URLValidator is aiming to meet the RFC1034/1035 then it
should be named DomainNameValidator. The RFC for URLs would be RFC1738,
which kinda, sorta allows for underscores to be used unquoted (it is a
reserved character).

RFC1738 may allow underscores in URLs generally, but not in the hostname.

>
> Also, the realitity is that there hosts out there that use underscores
in their name, especially in subdomains. Even if it is not standard or
recommended, hosts like that are still out there (and often outside the
control of the dev) and the current behaviour renders it unusable for
production.

What Claude said; if you disagree, the place to argue about it is the
DevelopersMailingList.

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

Re: [Django] #6327: Add has_module_permission to ModelAdmin

2014-05-07 Thread Django

#6327: Add has_module_permission to ModelAdmin
---+
 Reporter:  chrj   |Owner:
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by maxocub):

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

Re: [Django] #9025: Nested Inline Support in Admin

2014-05-07 Thread Django

#9025: Nested Inline Support in Admin
---+
 Reporter:  pixelcort  |Owner:
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  Bug?   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  1
---+

Comment (by AntoAngelino):

 +1

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

Re: [Django] #22340: Legacy Table Creation Methods Not Properly Deprecated

2014-05-07 Thread Django

#22340: Legacy Table Creation Methods Not Properly Deprecated
-+
 Reporter:  mlavin   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 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
-+

Comment (by Tim Graham ):

 In [changeset:"af06203cead2968f4d58a718100dedc0faa7c619"]:
 {{{
 #!CommitTicketReference repository=""
 revision="af06203cead2968f4d58a718100dedc0faa7c619"
 [1.7.x] Updated some docs for the delayed deprecation of legacy table
 creation; refs #22340.

 Backport of a2e3c96948 from master
 }}}

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

Re: [Django] #22340: Legacy Table Creation Methods Not Properly Deprecated

2014-05-07 Thread Django

#22340: Legacy Table Creation Methods Not Properly Deprecated
-+
 Reporter:  mlavin   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 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
-+

Comment (by Tim Graham ):

 In [changeset:"a2e3c9694823d6d451d6dd234e9d416600aacc68"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a2e3c9694823d6d451d6dd234e9d416600aacc68"
 Updated some docs for the delayed deprecation of legacy table creation;
 refs #22340.
 }}}

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

[django/django] af0620: [1.7.x] Updated some docs for the delayed deprecat...

2014-05-07 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: af06203cead2968f4d58a718100dedc0faa7c619
  
https://github.com/django/django/commit/af06203cead2968f4d58a718100dedc0faa7c619
  Author: Tim Graham 
  Date:   2014-05-07 (Wed, 07 May 2014)

  Changed paths:
M docs/howto/initial-data.txt
M docs/internals/deprecation.txt
M docs/releases/1.7.txt

  Log Message:
  ---
  [1.7.x] Updated some docs for the delayed deprecation of legacy table 
creation; refs #22340.

Backport of a2e3c96948 from master


-- 
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/536a2f5b852ab_2e3f1203d385222d%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] a2e3c9: Updated some docs for the delayed deprecation of l...

2014-05-07 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a2e3c9694823d6d451d6dd234e9d416600aacc68
  
https://github.com/django/django/commit/a2e3c9694823d6d451d6dd234e9d416600aacc68
  Author: Tim Graham 
  Date:   2014-05-07 (Wed, 07 May 2014)

  Changed paths:
M docs/howto/initial-data.txt
M docs/internals/deprecation.txt
M docs/releases/1.7.txt

  Log Message:
  ---
  Updated some docs for the delayed deprecation of legacy table creation; refs 
#22340.


-- 
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/536a2f4b61c51_242e60dd445852a%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22577: The makemigrations management command has a problem with migrations dir

2014-05-07 Thread Django

#22577: The makemigrations management command has a problem with migrations dir
-+-
 Reporter:  japrogramer@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  makemigrations,  | Triage Stage:
  fail, init, file   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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

Re: [Django] #22562: Each call of makemigrations creates a migration for custom user account.

2014-05-07 Thread Django

#22562: Each call of makemigrations creates a migration for custom user account.
-+--
 Reporter:  efrinut@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:  worksforme
 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 timo):

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


Comment:

 #22588 could be related.

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

Re: [Django] #22588: makemigrations and regexvalidators

2014-05-07 Thread Django

#22588: makemigrations and regexvalidators
-+--
 Reporter:  leftmoose|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.7-beta-2
 Severity:  Release blocker  |   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 timo):

 * needs_better_patch:  0 => 1
 * type:  Uncategorized => Bug
 * 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/067.88d4fa542cfc33ca80db884e1db76313%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 541310: Forward ported docs of security issues from df8162...

2014-05-07 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 541310023d5c46b280dcc8092c43cd36785d2634
  
https://github.com/django/django/commit/541310023d5c46b280dcc8092c43cd36785d2634
  Author: Tim Graham 
  Date:   2014-05-07 (Wed, 07 May 2014)

  Changed paths:
M docs/releases/security.txt

  Log Message:
  ---
  Forward ported docs of security issues from df81625da6.


-- 
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/536a25af47899_244efe3d3c306f5%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] ab2865: [1.7.x] Fixed some markup problems in docs/release...

2014-05-07 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: ab2865a48eb7163cd135e34fbfa35e62136ff1d8
  
https://github.com/django/django/commit/ab2865a48eb7163cd135e34fbfa35e62136ff1d8
  Author: Tim Graham 
  Date:   2014-05-07 (Wed, 07 May 2014)

  Changed paths:
M docs/releases/security.txt

  Log Message:
  ---
  [1.7.x] Fixed some markup problems in docs/releases/security.txt.


-- 
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/536a24e1b6582_214fa87d34875eb%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22340: Legacy Table Creation Methods Not Properly Deprecated

2014-05-07 Thread Django

#22340: Legacy Table Creation Methods Not Properly Deprecated
-+
 Reporter:  mlavin   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 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
-+

Comment (by Tim Graham ):

 In [changeset:"10327be1f3f9fed5dc40f6fe42e5494afcf7aa76"]:
 {{{
 #!CommitTicketReference repository=""
 revision="10327be1f3f9fed5dc40f6fe42e5494afcf7aa76"
 [1.7.x] Bump DatabaseCreation deprecation to 2.0 (refs #22340)

 Backport of 61da5f3f02 from master
 }}}

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

[django/django] 10327b: [1.7.x] Bump DatabaseCreation deprecation to 2.0 (...

2014-05-07 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 10327be1f3f9fed5dc40f6fe42e5494afcf7aa76
  
https://github.com/django/django/commit/10327be1f3f9fed5dc40f6fe42e5494afcf7aa76
  Author: Tim Graham 
  Date:   2014-05-07 (Wed, 07 May 2014)

  Changed paths:
M docs/internals/deprecation.txt

  Log Message:
  ---
  [1.7.x] Bump DatabaseCreation deprecation to 2.0 (refs #22340)

Backport of 61da5f3f02 from master


-- 
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/536a241490e9c_1d5c693d401021e8%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22591: Changing of HTTP status code in form_invalid()

2014-05-07 Thread Django

#22591: Changing of HTTP status code in form_invalid()
-+--
 Reporter:  kevmo314@…   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  forms| Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+--
Changes (by timo):

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


Comment:

 The main issue I see with this is that you're hijacking `kwargs` for
 `render_to_response()`. It seems equally likely that someone could propose
 passing them to `get_context_data()`. To achieve what you're after, I
 wonder if it would be better to override `render_to_response()` with
 something like:
 {{{
 form = context.get('form')
 if form and not form.is_valid():
response_kwargs['status'] = 400
 super().render_to_response(context, **response_kwargs)
 }}}

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

Re: [Django] #22470: Migrations fail with order_with_respect_to and ForeignKey to self

2014-05-07 Thread Django

#22470: Migrations fail with order_with_respect_to and ForeignKey to self
-+-
 Reporter:  Jonas|Owner:
 Type:  Bug  |  andrewgodwin
Component:  Migrations   |   Status:  assigned
 Severity:  Release blocker  |  Version:
 Keywords:  migrations   |  1.7-beta-1
  order_with_respect_to  |   Resolution:
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by shai):

 * cc: shai (added)


Comment:

 This is odd. I'd expect all the fields to be created immediately, and only
 the constraint creation to be delayed.

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

Re: [Django] #9586: Shall upload_to return an urlencoded string or not?

2014-05-07 Thread Django

#9586: Shall upload_to return an urlencoded string or not?
--+
 Reporter:  eibaan|Owner:
 Type:  Bug   |   Status:  new
Component:  File uploads/storage  |  Version:  1.0
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by anonymous):

 Hi I just stumbled over this problem using Django 1.6.4 on windows.

 Is there any idea when this bug will be fixed,
 or is there a "howto" somewhere?

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

69 matches

Mail list logo