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

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

 * needs_better_patch:  1 => 0
 * needs_docs:  1 => 0


Comment:

 I think this is now ready for checkin, but as this is a non-trivial new
 feature I'd like to get this reviewed before marking ready for checkin.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/080.c794c017f0825ef65688cb71320ac03e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23714: `date` filter raises an exception for naive datetimes during DST change (was: Django-1.7 doesn't display 500 error pages during DST change)

2014-11-18 Thread Django 
#23714: `date` filter raises an exception for naive datetimes during DST change
-+
 Reporter:  mbertheau|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  timezone | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by tricoder42):

 * keywords:   => timezone


Comment:

 That's right, with installed `pytz` I can see the exception.

 Minimal code to reproduce the problem:
 {{{#!python
 from django.conf import settings
 settings.configure(USE_TZ=True, TIME_ZONE='Europe/Amsterdam')

 import datetime
 from django.utils.dateformat import DateFormat

 right_now = datetime.datetime.now().replace(2014, 10, 26, 2, 30)
 print(DateFormat(right_now).format('Z'))
 }}}

 In my opinion it's more serious because it doesn't affect just 500 debug
 page, but all templates that uses `date` filter with `r`, `O` or `Z`.

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

Re: [Django] #23852: Timezone works inconsistently under Cygwin and Windows

2014-11-18 Thread Django 
#23852: Timezone works inconsistently under Cygwin and Windows
-+-
 Reporter:  wlnirvana|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.6
  commands)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:  timezone |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by wlnirvana):

 Replying to [comment:4 aaugustin]:
 > As explained in the documentation, you must set TIME_ZONE to the name of
 the HKT time zone in the tz database. Windows doesn't support doing things
 in a time zone that isn't the system time zone.
 >
 > Cygwin appears not to suffer from this limitation and manages to run
 your project in UTC as required by your settings file.
 I got it. I mistook the note as you must explicitly set {{{TIME_ZONE}}} in
 windows. Thanks a lot.

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

[Django] #23867: Remove hacks required by .dates() queries

2014-11-18 Thread Django 
#23867: Remove hacks required by .dates() queries
-+-
   Reporter:  akaariai   |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |Version:  master
  Component:  Database   |   Keywords:
  layer (models, ORM)|  Has patch:  0
   Severity:  Normal |Needs tests:  0
   Triage Stage:  Ready for  |  Easy pickings:  0
  checkin|
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 The dates() queries implementation uses custom QuerySet, Query and
 Compiler classes. Before expressions and database value converters were
 added there were no other way to convert the database values than addition
 of these subclasses to hack around the limitations in Django. But now with
 expressions and converters support it is possible to implement the dates
 queries by using public APIs only.

 This is implemented in https://github.com/django/django/pull/3570.

 As I don't think anybody wants to keep the old way around, and also I
 think the patch is ready for merge, so I'll mark this directly as ready
 for checkin.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.327a9607168851883929dc86d575d08c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23862: ManyToManyRel.get_related_field() doesn't account for defined through to_field

2014-11-18 Thread Django 
#23862: ManyToManyRel.get_related_field() doesn't account for defined through
to_field
-+-
 Reporter:  charettes|Owner:  charettes
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by akaariai):

 * stage:  Accepted => Ready for checkin


--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.e5ca1781ce4b89b2d90572175d234134%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23849: Document the locmem template loader

2014-11-18 Thread Django 
#23849: Document the locmem template loader
--+
 Reporter:  prestontimmons|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Carl Meyer ):

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


Comment:

 In [changeset:"536795f79a956febc06a7fa5c86e3a395f2c94eb"]:
 {{{
 #!CommitTicketReference repository=""
 revision="536795f79a956febc06a7fa5c86e3a395f2c94eb"
 Fixed #23849 -- Documented the locmem.Loader class.
 }}}

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

Re: [Django] #23760: ModelForm wrong default value on field without fields Meta attribute neither initial data.

2014-11-18 Thread Django 
#23760: ModelForm wrong default value on field without fields Meta attribute
neither initial data.
-+-
 Reporter:  aRkadeFR |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.6
Component:  Forms|   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:  form, modelform, |  Unreviewed
  default, value |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by schinckel):

 For what it's worth, if you need to know if something has been explicitly
 selected as Yes/No, then you _can_ write a form field that renders as a
 radio input, with two selections, neither of which is initially selected.
 Probably similar in concept to a NullBooleanField.

 You may even be able to use a NullBooleanField, and have custom form logic
 that rejects the None under certain circumstances.

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

Re: [Django] #23866: Broken link on 403 forbidden "CSRF token missing or incorrect." page

2014-11-18 Thread Django 
#23866: Broken link on 403 forbidden "CSRF token missing or incorrect." page
-+
 Reporter:  nikolas  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.7
 Severity:  Release blocker  |   Resolution:
 Keywords:  csrf | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+

Comment (by bmispelon):

 Replying to [comment:2 claudep]:
 > `from django.utils.version import get_major_version` :-)

 That would help, yes. But not for the development version though :)

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

Re: [Django] #23866: Broken link on 403 forbidden "CSRF token missing or incorrect." page

2014-11-18 Thread Django 
#23866: Broken link on 403 forbidden "CSRF token missing or incorrect." page
-+
 Reporter:  nikolas  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.7
 Severity:  Release blocker  |   Resolution:
 Keywords:  csrf | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+

Comment (by claudep):

 `from django.utils.version import get_major_version` :-)

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

Re: [Django] #18714: Add an option to compilemessages to compile fuzzy translations

2014-11-18 Thread Django 
#18714: Add an option to compilemessages to compile fuzzy translations
-+-
 Reporter:  rasca|Owner:  bak1an
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  compilemessages  |  checkin
  fuzzy msgfmt   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"d63703f1cd373f2a1d52e1947835b44d9565c1e0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d63703f1cd373f2a1d52e1947835b44d9565c1e0"
 Fixed #18714 -- Added 'fuzzy' compilemessages option
 }}}

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

Re: [Django] #23866: Broken link on 403 forbidden "CSRF token missing or incorrect." page

2014-11-18 Thread Django 
#23866: Broken link on 403 forbidden "CSRF token missing or incorrect." page
-+
 Reporter:  nikolas  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.7
 Severity:  Release blocker  |   Resolution:
 Keywords:  csrf | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by bmispelon):

 * severity:  Normal => Release blocker
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 Hi,

 The offending line can be found here:
 https://github.com/django/django/blob/master/django/views/csrf.py#L69

 We should also make this link https instead of just http and I'm also
 wondering if the link should point to the version of Django being used
 instead of the `dev` version (not sure how feasible that is though).

 I'm going to bump the severity as well since we should backport that fix.

 Thanks.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.2d3297c1bdcbcff84eee69f73a790fe7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23799: squashmigrations --no-optimize still optimizes

2014-11-18 Thread Django 
#23799: squashmigrations --no-optimize still optimizes
+-
 Reporter:  Tilka   |Owner:  Tilka
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  | Triage Stage:  Ready for checkin
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+-

Comment (by Tim Graham ):

 In [changeset:"dfcac7d7f5f1f108ae2c561f0f755f08d75a1c27"]:
 {{{
 #!CommitTicketReference repository=""
 revision="dfcac7d7f5f1f108ae2c561f0f755f08d75a1c27"
 [1.7.x] Fixed #23799 -- Made makemigrations respect --no-optimize.

 Thanks to yamila-moreno for the idea of a skip message.

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

[Django] #23866: Broken link on 403 forbidden "CSRF token missing or incorrect." page

2014-11-18 Thread Django 
#23866: Broken link on 403 forbidden "CSRF token missing or incorrect." page
---+
 Reporter:  nikolas|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.7
 Severity:  Normal |   Keywords:  csrf
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 This page links to this page:

 http://docs.djangoproject.com/en/dev/ref/contrib/csrf/#ref-contrib-
 csrf

 Which is a 404. Maybe this should be:

 https://docs.djangoproject.com/en/1.7/ref/contrib/csrf/

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

Re: [Django] #23863: runtests should allow using the `keepdb` option.

2014-11-18 Thread Django 
#23863: runtests should allow using the `keepdb` option.
-+-
 Reporter:  charettes|Owner:  charettes
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Testing framework|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by tricoder42):

 * stage:  Unreviewed => Ready for checkin


Comment:

 Looks good, perfect!

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

Re: [Django] #23864: UnitTest and sites framework

2014-11-18 Thread Django 
#23864: UnitTest and sites framework
---+--
 Reporter:  tomaszrycz |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.7
 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 claudep):

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


Comment:

 Please use support channels and only use this tracker for bugs in Django.
 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/068.715104d5197474a1bc62e614aa601549%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23850: Test failure in migrations tests

2014-11-18 Thread Django 
#23850: Test failure in migrations tests
+--
 Reporter:  jphalip |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  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 jphalip):

 There seems to be some conflicts or side-effects between
 `test_makemigrations_migrations_modules_path_not_exist` and
 `test_makemigrations_with_custom_name`. If I comment out the former, then
 the latter passes. If I only run the two tests (`runtests.py
 
migrations.test_commands.MakeMigrationsTests.test_makemigrations_migrations_modules_path_not_exist
 
migrations.test_commands.MakeMigrationsTests.test_makemigrations_with_custom_name`),
 then I see the failure.

 Could you try running those two tests as in the command 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/065.76a6179afe3d173d5b82c445e3af0625%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23865: Document raising a `ValidationError` with a dictionary

2014-11-18 Thread Django 
#23865: Document raising a `ValidationError` with a dictionary
---+
 Reporter:  alasdairnicol  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Ticket #16986 allows you to report errors on individual fields by
 instantiating a `ValidationError` with a dictionary. However, this
 technique is an undocumented private API, and not mentioned in the
 
[https://docs.djangoproject.com/en/dev/ref/models/instances/#django.db.models.Model.clean
 Model.clean docs].

 I started a [https://groups.google.com/forum/#!topic/django-
 developers/6KGoVYeM3-Y thread on Django developers]

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/056.19078cf63f8c38d869f36d68d4421495%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23861: IPAddressField removal will break migrations and test suites

2014-11-18 Thread Django 
#23861: IPAddressField removal will break migrations and test suites
---+--
 Reporter:  spookylukey|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  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 carljm):

 I think that in fact, squashing old migrations does solve this problem,
 and that's the solution we should recommend. Even third-party apps can
 squash migrations and then later remove them without any problem. They
 just need to get started on that process with enough lead time so that any
 of their users who upgrade to Django 1.9 have already gotten through the
 squashed migration set and upgraded to the version of the third-party app
 that removes the old migrations.

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

Re: [Django] #22248: Model renaming doesn't work backwards

2014-11-18 Thread Django 
#22248: Model renaming doesn't work backwards
--+
 Reporter:  andrewgodwin  |Owner:  andrewgodwin
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by MarkusH):

 * cc: info+coding@… (added)
 * needs_better_patch:  0 => 1
 * needs_docs:  0 => 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/070.4cd7f365c1cad9523ae91c3a171004bd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23801: Warn when max_length is used with IntegerField

2014-11-18 Thread Django 
#23801: Warn when max_length is used with IntegerField
-+-
 Reporter:  eykd |Owner:
 Type:  New feature  |  MattBlack85
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by MattBlack85):

 I wrote a small patch for this, you can find it here.
 https://github.com/MattBlack85/django/compare/gh-mb-fix_23801?expand=1
 Is it ok for the intent?

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

Re: [Django] #22248: Model renaming doesn't work backwards

2014-11-18 Thread Django 
#22248: Model renaming doesn't work backwards
--+
 Reporter:  andrewgodwin  |Owner:  andrewgodwin
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by stratoukos):

 Sorry about that, this is my first code contribution to Django. I'll keep
 it in mind for the future.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.e3aaaf4610adf463d27d57f0f7be8375%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23841: TestCase.assertWarns doesn't work when using django's test runner.

2014-11-18 Thread Django 
#23841: TestCase.assertWarns doesn't work when using django's test runner.
--+--
 Reporter:  Matt3o12  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Python 3  |  Version:  1.6
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by tchaumeny):

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


Comment:

 I'm closing this ticket as six upgrade to 1.8.0 has been backported to
 Django 1.6 (see
 
https://github.com/django/django/commit/81477c91f68d7091f8da417a030dd4b9b776b70a).
 Upgrading Django will most likely resolve your problem.

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

Re: [Django] #23841: TestCase.assertWarns doesn't work when using django's test runner.

2014-11-18 Thread Django 
#23841: TestCase.assertWarns doesn't work when using django's test runner.
--+--
 Reporter:  Matt3o12  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Python 3  |  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 tchaumeny):

 * cc: t.chaumeny@… (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 This seems to be related https://bitbucket.org/gutworth/six/issue/68
 /assertwarns-and-six. six has been upgraded to 1.8.0 on master and I can't
 reproduce it (although I can with an older checkout).

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

[Django] #23864: UnitTest and sites framework

2014-11-18 Thread Django 
#23864: UnitTest and sites framework
---+
 Reporter:  tomaszrycz |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Testing framework  |Version:  1.7
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I can't pass test with sites framework.

 {{{
 python2.7 manage.py test --settings=project.settings_sport
 }}}


 {{{
 def main_page(request):
 site = get_current_site(request)

 print("%s" % site.name)

 if site.name == 'sport':
 return sport.views.main_page(request)
 }}}

 Test has failed because {{{site.name}}} during test has value
 {{{example.com}}} but this value doesn't exist in database.
 When I run server {{{site.name}}} value is correct ({{{sport}}}).

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

Re: [Django] #22248: Model renaming doesn't work backwards

2014-11-18 Thread Django 
#22248: Model renaming doesn't work backwards
--+
 Reporter:  andrewgodwin  |Owner:  andrewgodwin
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by charettes):

 * stage:  Unreviewed => Accepted


Comment:

 The '''Triage State''' refers to the ticket and not the patch.

 Having '''Has patch''' checked with '''Patch needs improvement'''
 unchecked will ensure your patch shows up in the review queue.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.78848af116d1f1cd3ba9605acbedcbfc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23862: ManyToManyRel.get_related_field() doesn't account for defined through to_field

2014-11-18 Thread Django 
#23862: ManyToManyRel.get_related_field() doesn't account for defined through
to_field
-+-
 Reporter:  charettes|Owner:  charettes
 Type:  Bug  |   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:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by charettes):

 * needs_better_patch:  1 => 0


Comment:

 Updated patch.

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

Re: [Django] #22248: Model renaming doesn't work backwards

2014-11-18 Thread Django 
#22248: Model renaming doesn't work backwards
--+
 Reporter:  andrewgodwin  |Owner:  andrewgodwin
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by stratoukos):

 * has_patch:  0 => 1
 * stage:  Accepted => Unreviewed


Comment:

 I've made a pull request for this:
 https://github.com/django/django/pull/3572.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.9aa7a3ef881b1a6d8ed149237ec88cd5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22248: Model renaming doesn't work backwards

2014-11-18 Thread Django 
#22248: Model renaming doesn't work backwards
--+
 Reporter:  andrewgodwin  |Owner:  andrewgodwin
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by stratoukos):

 * cc: stratoukos (added)
 * status:  closed => new
 * resolution:  fixed =>


Comment:

 Although this seems to be fixed by b568bdf, RenameModel.reversible is
 still False making RenameModel unreversible.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.e650dc5221179c6c89829d64922d2deb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23862: ManyToManyRel.get_related_field() doesn't account for defined through to_field

2014-11-18 Thread Django 
#23862: ManyToManyRel.get_related_field() doesn't account for defined through
to_field
-+-
 Reporter:  charettes|Owner:  charettes
 Type:  Bug  |   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 akaariai):

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

Re: [Django] #22153: Custom User Model giving error in 1.7a2 where as it ran successfully in 1.6

2014-11-18 Thread Django 
#22153: Custom User Model giving error in 1.7a2 where as it ran successfully in 
1.6
-+---
 Reporter:  just10minutes@…  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Uncategorized|  Version:  1.7-alpha-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+---

Comment (by rokj):

 Was banging my head to the wall for two hours, until I found your post. I
 accidently commented out AUTH_USER_MODEL, and then this...

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/081.a752ed901182475432333d5a26e0bf41%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23800: Middleware CSRF validation is unclear for PUT and DELETE

2014-11-18 Thread Django 
#23800: Middleware CSRF validation is unclear for PUT and DELETE
--+--
 Reporter:  MarkLC|Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.csrf  |  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 tricoder42):

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


Comment:

 During `POST` request, the `CSRF` token is taken from `request.POST`, all
 other "unsafe" methods, `PUT`, `PATCH`, `DELETE`, should set the
 `X-CSRFToken` as described in
 [https://docs.djangoproject.com/en/1.7/ref/contrib/csrf/#ajax
 documentation].

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

[Django] #23863: runtests should allow using the `keepdb` option.

2014-11-18 Thread Django 
#23863: runtests should allow using the `keepdb` option.
-+-
   Reporter:  charettes  |  Owner:  charettes
   Type: | Status:  new
  Cleanup/optimization   |Version:  master
  Component:  Testing|   Keywords:
  framework  |  Has patch:  1
   Severity:  Normal |Needs tests:  0
   Triage Stage: |  Easy pickings:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 The `keepdb` option that was added in #20550 is not exposed through the
 `runtests` script.

 It can be quite handy when testing a feature that doesn't involve
 migrations.

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

Re: [Django] #23852: Timezone works inconsistently under Cygwin and Windows

2014-11-18 Thread Django 
#23852: Timezone works inconsistently under Cygwin and Windows
-+-
 Reporter:  wlnirvana|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.6
  commands)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:  timezone |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 As explained in the documentation, you must set TIME_ZONE to the name of
 the HKT time zone in the tz database. Windows doesn't support doing things
 in a time zone that isn't the system time zone.

 Cygwin appears not to suffer from this limitation and manages to run your
 project in UTC as required by your settings file.

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

Re: [Django] #23861: IPAddressField removal will break migrations and test suites

2014-11-18 Thread Django 
#23861: IPAddressField removal will break migrations and test suites
---+--
 Reporter:  spookylukey|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  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 claudep):

 It's true that with migrations, we are now setting in stone some old
 code/symbols, and we have to take this new paradigm into account.
 I'm not happy at all about keeping stubs/old code forever in Django.

 Some crazy idea without any proof of concept: Add a new django.legacy
 module which contains old code and which dynamically injects compatibility
 shims into Django current modules only when migrations are run.

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