date:20120820

Re: [Django] #18814: setting up view permission to user

2012-08-20 Thread Django

#18814: setting up view permission to user
-+--
 Reporter:  digambar |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  contrib.auth |  Version:  1.3
 Severity:  Release blocker  |   Resolution:  duplicate
 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 russellm):

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


Comment:

 Marking as a duplicate of #820 and #7150.

 Repeating something that I've said on the mailing list in the past: Django
 1.2 added two features that lead me to believe that the time may have
 come to revisit the earlier decisions to avoid view permissions.

 Firstly, we added readonly fields. Ultimately, a readonly view is just
 a view where all the fields are readonly; to me, it seems like a small
 jump from "specifying an admin with N readonly fields" to "specifying
 an admin that is all readonly fields".

 Secondly, we added a framework for per-object permissions. Although
 the API is in place for this, I'm not convinced that the consequences
 of this change have been fully reflected in the admin. After all, it's
 now possible to have a list of objects, but only have access to edit
 some of those objects - but that doesn't mean you can't *see* the
 remaining object - especially in the context of foreign key relations.

 So -- I'm at least willing to entertain the discussion about adding
 this as a first-class feature of the admin. If this is a feature that
 you are enthused by, then put together a full proposal describing
 exactly what you would like to add (possibly with a prototype patch),
 and we can have the discussion over whether we should add this feature
 to trunk -- or whether, like with per-object permissions, we just need
 to expose an better API to make it easier to add view permissions as
 an end-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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18637: FK.limit_choices_to doc says it's for admin, but works in ModelForm

2012-08-20 Thread Django

#18637: FK.limit_choices_to doc says it's for admin, but works in ModelForm
---+
 Reporter:  Tuttle |Owner:  stumbles
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by stumbles):

 * owner:  nobody => stumbles
 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18637: FK.limit_choices_to doc says it's for admin, but works in ModelForm

2012-08-20 Thread Django

#18637: FK.limit_choices_to doc says it's for admin, but works in ModelForm
---+
 Reporter:  Tuttle |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by stumbles):

 * cc: stumbles (added)
 * has_patch:  0 => 1


Comment:

 I've updated several places where "admin" is used as a synonym for
 automatically generated forms.

 I was hoping that using :class:`~django.forms.widgets.TextInput` would
 give a hyperlink to the widget documentation, but it doesn't seem to.
 Happy to fix this if there's a better way.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18823: Clear with a M2M field with a through model

2012-08-20 Thread Django

#18823: Clear with a M2M field with a through model
--+
 Reporter:  anonymous |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 This ticket deals with similar issues as #15161.

 When you have a M2M field with a through model where one of the foreign
 keys uses a to_field, the to_field is ignored by add, remove and clear.
 Only clear is available when using a normal through but it would be nice
 to fix for all of them.

 To see the currently wrong behavior try something like this:

 {{{
 class Through(models.Model):
 ffrom = models.ForeignKey('Two', to_field='slug')
 to = models.ForeignKey('One')

 class One(models.Model):
 name = models.CharField(max_length=100)

 class Two(models.Model):
 slug = models.CharField(max_length=24, unique=True)
 ones = models.ManyToManyField(One, through=Through)

 o = One(name='test')
 t = Two(slug='test2')
 Through(ffrom=t, to=o).save()
 t.ones.clear()
 }}}

 You'll see the relationship not being cleared as the queries use the value
 for the pk of t instead of the value of 'slug' on t ('test2').

 The fix could be as simple as changing ManyRelatedManager._pk_val to not
 be pk value but to lookup the correct value for the field. (line 534)

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18822: Social Commissions Bonus

2012-08-20 Thread Django

#18822: Social Commissions Bonus
--+--
 Reporter:  anonymous |  Owner:  IinslUi
 Type:  Bug   | Status:  new
Component:  contrib.sessions  |Version:  1.1-beta-1
 Severity:  Normal|   Keywords:  Social Commissions Bonus
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  1 |  UI/UX:  1
--+--
 [http://www.commissionpayload.info/2012/08/social-commissions.html  Click
 Here]
  Visit Website The following time I read a weblog, I hope that it doesnt
 disappoint me as much as this one. I mean, I do know it was my option to
 read, but I actually thought youd have one thing interesting to say. All I
 hear is a bunch of whining about one thing that you may fix if you happen
 to werent too busy searching for attention.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18657: Inconsistent db names in example

2012-08-20 Thread Django

#18657: Inconsistent db names in example
---+
 Reporter:  msb@…  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by stumbles):

 * cc: stumbles (added)


Comment:

 The database example chop and change a bit throughout the document,
 starting out with "default" and "users", then switching to "other",
 "master", "slave1" and "slave2" for the automatic routing examples, then
 switching back to simpler examples for manual routing.

 Perhaps this page could be simplified by rearranging to discuss manual
 routing first. It could briefly mentioning that automatic routing is the
 easiest solution, but then discussi manual routing followed by the detail
 on automatic routing. Sound ok?

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18821: freehold property

2012-08-20 Thread Django

#18821: freehold property
---+---
 Reporter:  anonymous  |  Owner:  YoKoyf
 Type:  Bug| Status:  new
Component:  contrib.sites  |Version:  1.1
 Severity:  Normal |   Keywords:  freehold property
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  1  |  UI/UX:  1
---+---
 [http://skiesmiltonia-sg.com/floor-plans/  sky miltonia] Under extreme
 circumstances, you may consider having an alarm system installed. When you
 have to go to court or file an insurance claim. To qualify, you must take
 steps to issue an eviction notice.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18820: Visit This Website

2012-08-20 Thread Django

#18820: Visit This Website
-+
 Reporter:  anonymous|  Owner:  FIRLpqc
 Type:  Bug  | Status:  new
Component:  Core (Cache system)  |Version:  1.0-alpha-2
 Severity:  Normal   |   Keywords:  Visit This Website
 Triage Stage:  Unreviewed   |  Has patch:  1
Easy pickings:  1|  UI/UX:  1
-+
 [http://www.commissionpayload.info/2012/08/social-commissions.html Social
 Commissions]
  Visit This Website That is the proper blog for anyone who desires to
 search out out about this topic. You notice a lot its virtually exhausting
 to argue with you (not that I truly would need…HaHa). You undoubtedly put
 a new spin on a subject thats been written about for years. Great stuff,
 simply great!

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18819: Typo: PDKDF instead of PBKDF

2012-08-20 Thread Django

#18819: Typo: PDKDF instead of PBKDF
--+
 Reporter:  jonaskoelker@…|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  closed
Component:  Documentation |Version:  1.4
 Severity:  Normal| Resolution:  fixed
 Keywords:  typo  |   Triage Stage:  Unreviewed
Has patch:  0 |  Easy pickings:  1
UI/UX:  1 |
--+
Changes (by Alex Gaynor ):

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


Comment:

 In [831f2846dd9b3a93344e3c5cb3ea57d76317ae2c]:
 {{{
 #!CommitTicketReference repository=""
 revision="831f2846dd9b3a93344e3c5cb3ea57d76317ae2c"
 Fixed #18819 -- fixed some typos in the auth docs
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 831f28: Fixed #18819 -- fixed some typos in the auth docs

2012-08-20 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 831f2846dd9b3a93344e3c5cb3ea57d76317ae2c
  
https://github.com/django/django/commit/831f2846dd9b3a93344e3c5cb3ea57d76317ae2c
  Author: Alex Gaynor 
  Date:   2012-08-20 (Mon, 20 Aug 2012)

  Changed paths:
M docs/topics/auth.txt

  Log Message:
  ---
  Fixed #18819 -- fixed some typos in the auth docs



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18819: Typo: PDKDF instead of PBKDF

2012-08-20 Thread Django

#18819: Typo: PDKDF instead of PBKDF
--+
 Reporter:  jonaskoelker@…|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.4
 Severity:  Normal|   Keywords:  typo
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  1
--+
 Password-''derived'' key derivation function? :-)

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17966: Tests fail with trivial usage of AUTH_PROFILE_MODULE

2012-08-20 Thread Django

#17966: Tests fail with trivial usage of AUTH_PROFILE_MODULE
--+
 Reporter:  slacy |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.auth  |  Version:  1.4
 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
--+

Comment (by anonymous):

 Replying to [comment:20 dokterbob]:
 > Replying to [comment:19 Claude Paroz ]:
 > > In [531878302735e6a2b36d82b584947bbf8eae8111]:
 > > {{{
 > > #!CommitTicketReference repository=""
 revision="531878302735e6a2b36d82b584947bbf8eae8111"
 > > Fixed #17966 -- Isolated ProfileTestCase from custom
 AUTH_PROFILE_MODULE
 > >
 > > Thanks Rob Golding for helping on the patch.
 > > }}}
 >
 > The patch seems to fix the initial problem but the tests now fail due to
 `SiteProfileNotAvailable` now not being raised in my specific setup. It
 seems as though `override_settings` is not doing quite what it ought to
 do:
 >
 > * With `AUTH_PROFILE_MODULE` commented out in my settings, the test runs
 fine.
 > * When I comment out the full `@override_settings` line the test runs
 fine.
 > * When I remove the `AUTH_PROFILE_MODULE` override, the test fails with
 `AttributeError: AUTH_PROFILE_MODULE` as in the original bug report.
 > * When I remove the `USE_TZ` override, I get the
 `SiteProfileNotAvailable` exception not being raised.
 >
 > No doubt this is a weird and difficult problem. Let me know if more
 feedback is required - I personally have no real clue what's going on here
 and do not have the time to delve much deeper but would love to help this
 bug get fixed.
 >
 > Lastly, it seems that Rob Golding's original patch from the pull request
 passes the unittest just fine.

 Just wanted to note that I'm having the same issue on Python 2.7, Django
 1.5.0. What seems to be occurring is that prior to line 15: del
 settings.AUTH_PROFILE_MODULE, settings.AUTH_PROFILE_MODULE reports itself
 as an empty string. However, after the del call,
 settings.AUTH_PROFILE_MODULE reports itself as the model defined in my
 settings.py. As a result, user.get_profile() is able to run fine and thus
 causes a test failure by not raising an error.

 I was able to replicate the issue by doing the following:

 - from a fresh project and app, creating a UserProfile model following
 these instructions: https://docs.djangoproject.com/en/dev/topics/auth
 /#storing-additional-information-about-users
 - this includes registering a handler as shown in the instructions
 - adding an AUTH_PROFILE_MODULE setting to settings.py pointing to the
 UserProfile model

 At this point, running python manage.py test exhibits the problematic
 behavior described above where settings.AUTH_PROFILE_MODULE defaults to
 what I defined in settings.py after the attribute is deleted.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16926: Custom SQL with Windows or Mac end-of-lines fail with Python 3

2012-08-20 Thread Django

#16926: Custom SQL with Windows or Mac end-of-lines fail with Python 3
--+
 Reporter:  adsworth  |Owner:  adsworth
 Type:  Bug   |   Status:  closed
Component:  Python 3  |  Version:  1.3
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by aaugustin):

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


Comment:

 This was fixed in [4e7f04cd].

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17040: In utils.crypto.constant_time_compare only call ord on non ints.

2012-08-20 Thread Django

#17040: In utils.crypto.constant_time_compare only call ord on non ints.
--+
 Reporter:  adsworth  |Owner:  adsworth
 Type:  Bug   |   Status:  closed
Component:  Python 3  |  Version:  1.3
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Aymeric Augustin ):

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


Comment:

 In [62954ba04c86c4cea3b17a872ba6a0837730e17d]:
 {{{
 #!CommitTicketReference repository=""
 revision="62954ba04c86c4cea3b17a872ba6a0837730e17d"
 [py3] Fixed #17040 -- ported django.utils.crypto.constant_time_compare.

 This is a private API; adding a type check is acceptable.
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 62954b: [py3] Fixed #17040 -- ported django.utils.crypto.c...

2012-08-20 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 62954ba04c86c4cea3b17a872ba6a0837730e17d
  
https://github.com/django/django/commit/62954ba04c86c4cea3b17a872ba6a0837730e17d
  Author: Aymeric Augustin 
  Date:   2012-08-20 (Mon, 20 Aug 2012)

  Changed paths:
M django/utils/crypto.py
M tests/regressiontests/utils/crypto.py
M tests/regressiontests/utils/tests.py

  Log Message:
  ---
  [py3] Fixed #17040 -- ported django.utils.crypto.constant_time_compare.

This is a private API; adding a type check is acceptable.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18818: Typo: PDKDF instead of PBKDF

2012-08-20 Thread Django

#18818: Typo: PDKDF instead of PBKDF
--+
 Reporter:  jonaskoelker@…|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.4
 Severity:  Normal|   Keywords:  typo
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  1
--+
 Password-''derived'' key derivation function? :-)

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18817: asphalt driveway crack repair

2012-08-20 Thread Django

#18817: asphalt driveway crack repair
---+---
 Reporter:  anonymous  |  Owner:  DEpHyheQ
 Type:  Bug| Status:  new
Component: |Version:  1.1
  contrib.staticfiles  |   Keywords:  asphalt driveway crack repair
 Severity:  Normal |  Has patch:  1
 Triage Stage:  Unreviewed |  UI/UX:  1
Easy pickings:  1  |
---+---
 How goes it, great web site you have got right now. Also please write
 about diy asphalt driveway repair more, like this:
 [http://www.drivewayrepair.org/asphalt-driveway-repair/ how to repair
 asphalt driveway cracks]

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18805: Superuser not created (python 3.2.3 and DJango 1.5)

2012-08-20 Thread Django

#18805: Superuser not created (python 3.2.3 and DJango 1.5)
-+
 Reporter:  sunsesh@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Python 3 |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  Decode, STR  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Aymeric Augustin ):

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


Comment:

 In [54899d810dfb892558699ddbd5f724a358dc96e1]:
 {{{
 #!CommitTicketReference repository=""
 revision="54899d810dfb892558699ddbd5f724a358dc96e1"
 [py3] Fixed #18805 -- ported createsuperuser.

 Thanks sunsesh at gmail.com for the report.
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 54899d: [py3] Fixed #18805 -- ported createsuperuser.

2012-08-20 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 54899d810dfb892558699ddbd5f724a358dc96e1
  
https://github.com/django/django/commit/54899d810dfb892558699ddbd5f724a358dc96e1
  Author: Aymeric Augustin 
  Date:   2012-08-20 (Mon, 20 Aug 2012)

  Changed paths:
M django/contrib/auth/management/__init__.py
M django/contrib/auth/tests/management.py

  Log Message:
  ---
  [py3] Fixed #18805 -- ported createsuperuser.

Thanks sunsesh at gmail.com for the report.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18816: Remove "trim" argument from add_filter()

2012-08-20 Thread Django

#18816: Remove "trim" argument from add_filter()
--+
 Reporter:  akaariai  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 The sql.query.Query.split_exclude() needs to trim one final join when it
 adds filters to the original query. It does this by passing "trim" to
 add_filter(), and add_filter() then knows to trim the last join.

 We can likely directly trim the last part of the join path in
 split_exclude() directly. This will remove the need to burden the
 add_filter() with the trim argument, and thus makes the ORM code easier to
 follow.

 The patch in https://github.com/akaariai/django/tree/remove_trim is not
 commit ready. There are two problems in need of an answer:
   - is the unconditional use of `"pk__in"` as the lookup in case there
 were just one lookup part in the path correct? It seems the pk would need
 to be changed to something else in case there is a to_field argument for
 the relation used.
   - removing the trim argument from add_filter() will result in allow_m2m
 value being different when add_filter() is called from split_exclude().

 For the above reasons: while tests pass with the above patch, I don't
 think it is correct.

 The removal of trim arg would also maybe make it possible to remove the
 current trim_joins() altogether when combined with the patch from #10790,
 and this in turn would allow to change the return value from setup_joins()
 to something nicer. So, this is one more part in trying to clean the ORM.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18023: Stop bundling simplejson and deprecate the module

2012-08-20 Thread Django

#18023: Stop bundling simplejson and deprecate the module
-+-
 Reporter:  ogier|Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core |   Resolution:  fixed
  (Serialization)| Triage Stage:  Accepted
 Severity:  Release blocker  |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [610746f6cb89c13b364c27fc41ecc9592cbe1605]:
 {{{
 #!CommitTicketReference repository=""
 revision="610746f6cb89c13b364c27fc41ecc9592cbe1605"
 Fixed #18023 -- Documented simplejson issues.

 Thanks Luke Plant for reporting the issue and Alex Ogier for thoroughly
 investigating 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 610746: Fixed #18023 -- Documented simplejson issues.

2012-08-20 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 610746f6cb89c13b364c27fc41ecc9592cbe1605
  
https://github.com/django/django/commit/610746f6cb89c13b364c27fc41ecc9592cbe1605
  Author: Aymeric Augustin 
  Date:   2012-08-20 (Mon, 20 Aug 2012)

  Changed paths:
M docs/releases/1.5.txt

  Log Message:
  ---
  Fixed #18023 -- Documented simplejson issues.

Thanks Luke Plant for reporting the issue and Alex Ogier for thoroughly
investigating it.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18809: MultipleObjectTemplateResponseMixin should handle a generic EmptyQuerySet

2012-08-20 Thread Django

#18809: MultipleObjectTemplateResponseMixin should handle a generic 
EmptyQuerySet
---+--
 Reporter:  benjaoming |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Generic views  |  Version:  1.4
 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 benjaoming):

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


Comment:

 This bug would be straight-up invalid in case an EmptyQuerySet is never
 supposed to have been instantiated without the model kwarg, ie.
 EmptyQuerySet(model=MyModel) is mandatory.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18815: click here

2012-08-20 Thread Django

#18815: click here
--+
 Reporter:  anonymous |  Owner:  XYCTpL
 Type:  Bug   | Status:  new
Component:  contrib.sessions  |Version:  1.1-beta-1
 Severity:  Normal|   Keywords:  click here
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  1 |  UI/UX:  1
--+
 [http://fyple.co.uk/company/your-accountants-leeds-qme7mzz  click here]

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18814: setting up view permission to user

2012-08-20 Thread Django

#18814: setting up view permission to user
-+--
 Reporter:  digambar |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.auth |  Version:  1.3
 Severity:  Release blocker  |   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 digambar):

 * needs_docs:   => 0
 * version:  1.4 => 1.3
 * type:  Uncategorized => New feature
 * needs_tests:   => 0
 * needs_better_patch:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18814: setting up view permission to user

2012-08-20 Thread Django

#18814: setting up view permission to user
-+
 Reporter:  digambar |  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  contrib.auth |Version:  1.4
 Severity:  Release blocker  |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 There is no "Can view profile" permission available for user.
 When admin wants to create a new user which will only view profile
 when you set the "Can view profile" permission.
 That user should not add & edit profile. It only can view the profile.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #15089: contrib.sites and multitenancy

2012-08-20 Thread Django

#15089: contrib.sites and multitenancy
-+-
 Reporter:  legutierr|Owner:  apollo13
 Type:  New feature  |   Status:  new
Component:  contrib.sites|  Version:
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  1
 |UI/UX:  0
-+-
Changes (by rizumu):

 * cc: tom@… (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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17789: when i use a custom FieldListFilter class for a given field.

2012-08-20 Thread Django

#17789: when i use a custom FieldListFilter class for a given field.
-+--
 Reporter:  Kidwind  |Owner:  julien
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.4
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  FieldListFilter  | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by KyleMac):

 My issue is that I wanted to use custom filters to change the titles of
 filters to clarify their purpose. However you can't do this with filters
 that span relationships because of the subject of this ticket.

 There is currently no other way to change the title of a filter other than
 using `verbose_name` on the field itself but that has a much wider effect.

 What I was trying to do was something like the following:

 {{{
 class PastSupplierFilter(RelatedFieldListFilter):
 def __init__(self, *args, **kwargs):
 super(PastSupplierFilter, self).__init__(*args, **kwargs)
 self.title = _('past supplier')


 class ReorderAdmin(admin.ModelAdmin):
 list_filter = (
 ('product__suppliers', PastSupplierFilter),
 )
 }}}

 A better solution but a more complex change would be to allow
 `list_filter` to accept a third value as the title of the filter. Django
 currently assumes that the name of a field and the purpose/effect of a
 filter are the same, which is not always the case especially when spanning
 relationships.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #11642: Specify default namespace in urls.py

2012-08-20 Thread Django

#11642: Specify default namespace in urls.py
-+-
 Reporter:  mrmachine|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (URLs)  |  Version:  1.1
 Severity:  Normal   |   Resolution:
 Keywords:  url namespace| Triage Stage:  Accepted
  default|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * component:  Core (Other) => Core (URLs)


-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 128857: Made an example more readable in the URLs docs.

2012-08-20 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1288572d9203472be8aa28e956027899fec3ed92
  
https://github.com/django/django/commit/1288572d9203472be8aa28e956027899fec3ed92
  Author: Aymeric Augustin 
  Date:   2012-08-20 (Mon, 20 Aug 2012)

  Changed paths:
M docs/topics/http/urls.txt

  Log Message:
  ---
  Made an example more readable in the URLs docs.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18813: TEST_MIRROR functionality broken for sqlite

2012-08-20 Thread Django

#18813: TEST_MIRROR functionality broken for sqlite
---+--
 Reporter:  adsva  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.4
 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 adsva):

 * component:  Uncategorized => Testing framework
 * needs_better_patch:   => 0
 * type:  Uncategorized => Bug
 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18813: TEST_MIRROR functionality broken for sqlite

2012-08-20 Thread Django

#18813: TEST_MIRROR functionality broken for sqlite
---+
 Reporter:  adsva  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+
 I do understand that SQLite doesn't really support replication, so the
 test_mirror setting might be a little silly, but I'm using postgres with a
 master/slave setup in production and would like to use SQLite when running
 the tests for simplicity and performance. Following what seems like a
 somewhat common practice of switching the DATABASES setting for testing:

 {{{
 if 'test' in sys.argv:

 DATABASES = {
 "default": {
 "ENGINE": "django.db.backends.sqlite3",
 },
 "slave": {
 "ENGINE": "django.db.backends.sqlite3",
 'TEST_MIRROR': 'default',
 },
 }

 }}}

 But when I try to use `connections['slave']` after database initialization
 is done in the test runner I get an uninitialized in-memory database, and
 not the `connections['default']` database. The reason seems to be that the
 test runner just copies the name and features of the 'default' connection
 to the 'slave' connection. I guess this is sufficient for the other
 database engines, where the name ensures the connections use the same
 database, but each SQLite connection to ':memory:' gets its own database.

 The attached patch changes that behavior to simply point
 `connections['slave']` to `connections['master']`, and that seems to solve
 the problem, but maybe there was good reason for the current behavior?

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18812: Social Commissions Review

2012-08-20 Thread Django

#18812: Social Commissions Review
-+-
 Reporter:  anonymous|  Owner:  vZYEyeKQ
 Type:   | Status:  new
  Cleanup/optimization   |Version:  1.4
Component:  GIS  |   Keywords:  Social Commissions
 Severity:  Release blocker  |  Review
 Triage Stage:  Unreviewed   |  Has patch:  1
Easy pickings:  1|  UI/UX:  1
-+-
 [http://www.commissionpayload.info/2012/08/social-commissions.html  Visit
 This Website]
  Visit Website Would you be focused on exchanging links?

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18648: ConditionalGetMiddleware does not work with Internet Explorer

2012-08-20 Thread Django

#18648: ConditionalGetMiddleware does not work with Internet Explorer
---+--
 Reporter:  KyleMac|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  HTTP handling  |  Version:  1.4
 Severity:  Normal |   Resolution:  needsinfo
 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 KyleMac):

 Yes, the anon comment is me.

 The reason the middleware fails to parse the header from IE is pretty
 simple. The whole header value is passed to `parse_http_date_safe` which
 returns None due to the extra stuff IE adds to the end. The simple fix is
 something like:

 if_modified_since =
 parse_http_date_safe(if_modified_since.split(';')[0])

 This bug has nothing to do with the middleware adding headers but is
 instead about how it parses headers sent by the browser. The mystery is
 what does runserver do that causes IE to send an invalid header while IE
 responds to Apache + mod_wsgi with a valid header.

 This bug is minor but really annoying if you're actually developing views
 that are meant to be cached. Since Webkit, Firefox and IE all have
 slightly different caching behaviour you do need to test thoroughly in
 each browser and this bug makes that harder.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18811: associates degree

2012-08-20 Thread Django

#18811: associates degree
--+---
 Reporter:  anonymous |  Owner:  ZYzEpsxo
 Type:  Cleanup/optimization  | Status:  new
Component:  ORM aggregation   |Version:  1.4-beta-1
 Severity:  Release blocker   |   Keywords:  associates degree
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  1 |  UI/UX:  1
--+---
 [http://hclaweb.org/your-online-certificate-programs-options  online
 associates degree] It is my hope that my personal experience talking to
 representatives on the phone, having my son test the curriculum and the
 infrastructure. No traffic to fight to get the types of urban planner
 jobs. For example the University of Texas, Austin - McCombs School of
 Business The University of Oklahoma is home of the degree market.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18767: Admin's calendar for datetime fields doesn't show right values with russian and some other locales

2012-08-20 Thread Django

#18767: Admin's calendar for datetime fields doesn't show right values with 
russian
and some other locales
---+--
 Reporter:  void   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  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
---+--

Comment (by void):

 I believe it's enough to have `LANGUAGE_CODE = 'ru-ru'` in the
 `settings.py`

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18810: Visit This Website

2012-08-20 Thread Django

#18810: Visit This Website
--+
 Reporter:  anonymous |  Owner:  SLlrrdAa
 Type:  Cleanup/optimization  | Status:  new
Component:  Python 2  |Version:  1.4-alpha-1
 Severity:  Release blocker   |   Keywords:  Visit This Website
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  1 |  UI/UX:  1
--+
 [http://www.commissionpayload.info/2012/08/social-commissions.html Social
 Commissions]
  Visit This Website I'm usually to blogging and i actually appreciate your
 content. The article has actually peaks my interest. I am going to
 bookmark your web site and maintain checking for brand spanking new
 information.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18809: MultipleObjectTemplateResponseMixin should handle a generic EmptyQuerySet

2012-08-20 Thread Django

#18809: MultipleObjectTemplateResponseMixin should handle a generic 
EmptyQuerySet
---+
 Reporter:  benjaoming |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Generic views  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 In get_template_names:

 {{{#!python
 if hasattr(self.object_list, 'model'):
 opts = self.object_list.model._meta
 names.append("%s/%s%s.html" % (opts.app_label,
 opts.object_name.lower(), self.template_name_suffix))
 }}}


 ...it should be verified that self.object_list is not None as it
 apparently may be in some cases where an EmptyQuerySet instance has been
 generated with no relation to its model class.

 On a secondary note, I don't understand why get_template_names is even
 called when I have defined template_name -- seems like bug?

 The work-around is to override get_template_names in your own ListView
 inheritor:

 {{{#!python
 def get_template_names(self):
 # WHY IS THIS CALLED?
 return [self.__class__.template_name]
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18767: Admin's calendar for datetime fields doesn't show right values with russian and some other locales

2012-08-20 Thread Django

#18767: Admin's calendar for datetime fields doesn't show right values with 
russian
and some other locales
---+--
 Reporter:  void   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  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
---+--

Comment (by anonymous):

 I do not have that problem, describe the regional settings that are
 installed on your system.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18808: Visit This Website

2012-08-20 Thread Django

#18808: Visit This Website
---+
 Reporter:  anonymous  |  Owner:  qVAxP
 Type:  Bug| Status:  new
Component:  contrib.webdesign  |Version:  1.0-beta-1
 Severity:  Normal |   Keywords:  Visit This Website
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  1  |  UI/UX:  1
---+
 [http://www.commissionpayload.info/2012/08/social-commissions.html  Visit
 Website]
  Social Commissions Bonus I found your weblog web site on google and test
 just a few of your early posts. Proceed to keep up the superb operate. I
 just extra up your RSS feed to my MSN Information Reader. Looking for
 ahead to studying more from you later on!

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 4e82d6: Added links in URLs doc for consistency.

2012-08-20 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4e82d614002f3fb46a3504b3a4fa2dcbf7f53dab
  
https://github.com/django/django/commit/4e82d614002f3fb46a3504b3a4fa2dcbf7f53dab
  Author: Aymeric Augustin 
  Date:   2012-08-20 (Mon, 20 Aug 2012)

  Changed paths:
M docs/topics/http/urls.txt
M docs/topics/http/views.txt

  Log Message:
  ---
  Added links in URLs doc for consistency.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18807: Inconsistency in the default views

2012-08-20 Thread Django

#18807: Inconsistency in the default views
+
   Reporter:  aaugustin |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Core (Other)  |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 `django.views.defaults.permission_denied` will respond ``403
 Forbidden`` if no ``403.html`` template is found. This behavior was
 introduced to provide
 [https://code.djangoproject.com/ticket/5515#comment:16 backwards
 compatibility]. Generally speaking, it is a reasonable fallback.

 I believe that `page_not_found` and `server_error` could benefit from a
 similar fallback.

 That would prevent 404s from turning into 500s when there's no 404.html
 template. I know we want to encourage custom error pages, but in case a
 developer skips them, a bare ``404 Not Found`` is less damaging
 than a 500 with a backtrace or no content at all.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17209: Dogfood class-based views in contrib.auth

2012-08-20 Thread Django

#17209: Dogfood class-based views in contrib.auth
-+-
 Reporter:  melinath |Owner:  andrews
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  contrib.auth |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  class-based views|  Needs documentation:  0
  admin auth |  Patch needs improvement:  1
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by mjtamlyn):

 Ok, I've got all of the tests working again and updated the wrapping of
 the new views with the old ones.

 The code is visible here: https://github.com/mjtamlyn/django/compare/auth-
 cbv

 The last thing to add to the list above is integrating these changes with
 the rest of django. The auth views are used by the admin, flatpages and
 other parts of auth and these should be updated to use the new cbv
 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18661: special characters like "é" or "è" in sqlite3 file path raise a "sqlite3.OperationalError: unable to open database file"

2012-08-20 Thread Django

#18661: special characters like "é" or "è" in sqlite3 file path raise a
"sqlite3.OperationalError: unable to open database file"
-+-
 Reporter:  oncleben31   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:  windows  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by kmtracey):

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


Comment:

 I have verified that so long as the database name string is unicode
 (prefixed with `u''`, or in a file with `from __future__ import
 unicode_literals`), a sqlite file name with non-ascii characters works
 fine, on Windows. Tried 1.4 and current master, on current master tried
 both py2 and py3. The unicode warning noted above only happens when the DB
 name string is not unicode.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18806: How You Can Get Cars Via Bad Credit

2012-08-20 Thread Django

#18806: How You Can Get Cars Via Bad Credit
-+-
 Reporter:  anonymous|  Owner:  DnRAO
 Type:   | Status:  new
  Cleanup/optimization   |Version:  1.4-beta-1
Component:  ORM aggregation  |   Keywords:  How You Can Get Cars
 Severity:  Release blocker  |  Via Bad Credit
 Triage Stage:  Unreviewed   |  Has patch:  1
Easy pickings:  1|  UI/UX:  1
-+-
 [http://www.pamokos.net/2010/05/05/are-there-legitimate-car-loan-
 companies-for-bad-credit-that-help-people-in-the-real-world/ How to Get
 Approved for a Car Loan If You Have Bad Credit] I am sure that the Fit is
 projected to be just as outraged as me who published all eighteen codes.
 Your monthly lease amount will invariably be less initially, than the
 Nitro.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18805: Superuser not created (python 3.2.3 and DJango 1.5)

2012-08-20 Thread Django

#18805: Superuser not created (python 3.2.3 and DJango 1.5)
-+
 Reporter:  sunsesh@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Python 3 |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  Decode, STR  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by aaugustin):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Accepted
 * version:  1.4 => master
 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18805: Superuser not created (python 3.2.3 and DJango 1.5)

2012-08-20 Thread Django

#18805: Superuser not created (python 3.2.3 and DJango 1.5)
+-
 Reporter:  sunsesh@…   |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Python 3|Version:  1.4
 Severity:  Normal  |   Keywords:  Decode, STR
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+-
 As I was testing the tutorial (Poll), I encountered the above error during
 the first dbsync.

 When I said yes for creation of the superuser, I got the error:

 AttributeError: 'str' object has no attribute 'decode'

 and the superuser was not created.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #3011: Allow for extendable auth_user module

2012-08-20 Thread Django

#3011: Allow for extendable auth_user module
---+
 Reporter:  nowell strite  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.auth   |  Version:
 Severity:  Normal |   Resolution:
 Keywords:  auth_user  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by sergzach):

 * cc: sergzach (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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16455: Postgis 2.0 Compatibility

2012-08-20 Thread Django

#16455: Postgis 2.0 Compatibility
-+
 Reporter:  ckarrie  |Owner:  jbronn
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  postgis 2.0  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by akaariai):

 * needs_better_patch:  1 => 0


Comment:

 I have now an updated patch in
 https://github.com/akaariai/django/tree/postgis2. This needs another
 review.

 I do get errors from the test suite:
 {{{
 ==
 FAIL: test01_retrieve
 (django.contrib.gis.tests.test_spatialrefsys.SpatialRefSysTest)
 Testing retrieval of SpatialRefSys model objects.
 --
 Traceback (most recent call last):
   File
 
"/home/akaariai/projects/django/tests/django/contrib/gis/tests/test_spatialrefsys.py",
 line 58, in test01_retrieve
 self.assertEqual(srtext, srs.wkt)
 AssertionError: 'GEOGCS["WGS 84",DATUM["WGS_1984",SPHEROID["WGS
 
84",6378137,298.257223563,AUTHORITY["EPSG","7030"]],AUTHORITY["EPSG","6326"]],PRIMEM["Greenwich",0,AUTHORITY["EPSG","8901"]],UNIT["degree",0.01745329251994328,AUTHORITY["EPSG","9122"]],AUTHORITY["EPSG","4326"]]'
 != u'GEOGCS["WGS 84",DATUM["WGS_1984",SPHEROID["WGS
 
84",6378137,298.257223563,AUTHORITY["EPSG","7030"]],AUTHORITY["EPSG","6326"]],PRIMEM["Greenwich",0,AUTHORITY["EPSG","8901"]],UNIT["degree",0.0174532925199433,AUTHORITY["EPSG","9122"]],AUTHORITY["EPSG","4326"]]'

 ==
 FAIL: test02_osr
 (django.contrib.gis.tests.test_spatialrefsys.SpatialRefSysTest)
 Testing getting OSR objects from SpatialRefSys model objects.
 --
 Traceback (most recent call last):
   File
 
"/home/akaariai/projects/django/tests/django/contrib/gis/tests/test_spatialrefsys.py",
 line 88, in test02_osr
 self.assertEqual(srtext, srs.wkt)
 AssertionError: 'GEOGCS["WGS 84",DATUM["WGS_1984",SPHEROID["WGS
 
84",6378137,298.257223563,AUTHORITY["EPSG","7030"]],AUTHORITY["EPSG","6326"]],PRIMEM["Greenwich",0,AUTHORITY["EPSG","8901"]],UNIT["degree",0.01745329251994328,AUTHORITY["EPSG","9122"]],AUTHORITY["EPSG","4326"]]'
 != 'GEOGCS["WGS 84",DATUM["WGS_1984",SPHEROID["WGS
 
84",6378137,298.257223563,AUTHORITY["EPSG","7030"]],AUTHORITY["EPSG","6326"]],PRIMEM["Greenwich",0,AUTHORITY["EPSG","8901"]],UNIT["degree",0.0174532925199433,AUTHORITY["EPSG","9122"]],AUTHORITY["EPSG","4326"]]'

 --
 Ran 27 tests in 0.017s

 FAILED (failures=2)
 }}}

 The failures seem to be about float conversion. On my laptop I got
 different errors, again related to float rounding. The question is if this
 is related to the updated PostGIS & dependencies, or if it is a pre-
 existing failure. At least on the laptop these errors seem to be present
 even using PostGIS 1.5.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17026: Message storage backends section missing "just use x"

2012-08-20 Thread Django

#17026: Message storage backends section missing "just use x"
-+-
 Reporter:  coolRR   |Owner:  aaugustin
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * owner:  nobody => aaugustin
 * status:  reopened => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] bfc380: [py3] Prepared MySQL backend for Python 3 compatib...

2012-08-20 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: bfc380baeaca359ac7b36eb35a2415e6a37e836c
  
https://github.com/django/django/commit/bfc380baeaca359ac7b36eb35a2415e6a37e836c
  Author: Claude Paroz 
  Date:   2012-08-20 (Mon, 20 Aug 2012)

  Changed paths:
M django/db/backends/mysql/compiler.py
M django/db/backends/mysql/introspection.py

  Log Message:
  ---
  [py3] Prepared MySQL backend for Python 3 compatibility



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18804: Class based view documentation is a bit confusing

2012-08-20 Thread Django

#18804: Class based view documentation is a bit confusing
--+
 Reporter:  anthonyb  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:  class based views | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by mjtamlyn):

 * cc: marc.tamlyn@… (added)
 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 If we're adding JSON related examples to the docs, we should also
 integrate the example here: https://github.com/django/django/pull/195
 (which handles AJAX post data)

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #14093: Confusing error when failing to create a session key because the cache is unavailable

2012-08-20 Thread Django

#14093: Confusing error when failing to create a session key because the cache 
is
unavailable
-+-
 Reporter:  szymon@… |Owner:  stumbles
 Type:  Bug  |   Status:  assigned
Component:  contrib.sessions |  Version:  1.2
 Severity:  Normal   |   Resolution:
 Keywords:  session, cache,  | Triage Stage:  Accepted
  session key|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by stumbles):

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


Comment:

 I've updated the exception message in the attached 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18766: Models with datetime fields fail to save when date is below 1900 and USE_TZ is True

2012-08-20 Thread Django

#18766: Models with datetime fields fail to save when date is below 1900 and 
USE_TZ
is True
---+--
 Reporter:  void   |Owner:  aaugustin
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  timezone, tz   | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by aaugustin):

 See also #17262.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17262: Refactor the implementations of tzinfo classes

2012-08-20 Thread Django

#17262: Refactor the implementations of tzinfo classes
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Core (Other) |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  timezone tzinfo  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 See also #18766.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18804: Class based view documentation is a bit confusing

2012-08-20 Thread Django

#18804: Class based view documentation is a bit confusing
--+---
 Reporter:  anthonyb  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.4
 Severity:  Normal|   Keywords:  class based views
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  1 |  UI/UX:  0
--+---
 I've attached a patch which fixes some of the wording and structure of the
 docs for class based views. I've moved the JSONResponseMixin class into
 the later mixin section, since it doesn't really fit in the introductory
 section.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18766: Models with datetime fields fail to save when date is below 1900 and USE_TZ is True

2012-08-20 Thread Django

#18766: Models with datetime fields fail to save when date is below 1900 and 
USE_TZ
is True
---+--
 Reporter:  void   |Owner:  aaugustin
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  timezone, tz   | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by aaugustin):

 Indeed, this is a limitation of `django.utils.tzinfo.LocalTimezone`.

 Could you try installing `pytz` (as strongly recommeded by the docs)? If
 that fixes the problem, I'd lean towards a documentation fix rather than
 extending the huge hack that is `LocalTimezone`.

 Note that dates after 2038 are handled by returning incorrect data rather
 than crashing. I deeply dislike that, but I can't change it easily, for
 backwards-compatibility reasons.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #14694: defer() doesn't work with reverse relations

2012-08-20 Thread Django

#14694: defer() doesn't work with reverse relations
-+-
 Reporter:  sayane   |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  defer only   |  Needs documentation:  0
  OneToOneField reverse  |  Patch needs improvement:  0
  relationship   |UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by akaariai):

 The idea about iterator ended up not working without altering the queryset
 iterator behavior. See #18702.

 I will try to find some time to get this one committed.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #14885: is_valid for ModelForm changes instance if instance is provided

2012-08-20 Thread Django

#14885: is_valid for ModelForm changes instance if instance is provided
-+-
 Reporter:  italomaia|Owner:  stumbles
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.2
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  forms, is_valid, |  Needs documentation:  0
  bad data   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by stumbles):

 * status:  reopened => new
 * owner:  nobody => stumbles
 * has_patch:  0 => 1


Comment:

 I've added a patch to point out both that `is_valid()` causes the model
 instance to be modified in place, and also that this modification can be
 partial.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18794: When timezone support is enabled, permalinks for DateDetailView are impossible.

2012-08-20 Thread Django

#18794: When timezone support is enabled, permalinks for DateDetailView are
impossible.
---+--
 Reporter:  void   |Owner:  aaugustin
 Type:  Bug|   Status:  closed
Component:  Generic views  |  Version:  master
 Severity:  Normal |   Resolution:  wontfix
 Keywords:  timezone, tz   | Triage Stage:  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:   => wontfix


Comment:

 I can now confirm that the behavior described by the reporter was
 introduced on purpose in 78ba9670af.

 Basically, this is an ill-defined problem: convert between dates and
 datetimes in a time zone aware world.

 [https://docs.djangoproject.com/en/dev/ref/class-based-views/mixins-date-
 based/#datemixin As documented here], the best solution is to back your
 date-based CBV on a `DateField` and not on a `DateTimeField`.
 Alternatively you could override `get_object`.

 

 Assuming there is a per-user timezone selection mechanism that sets the
 current time zone, and that the date-based CBV are backed on a
 `DateTimeField` -- otherwise none of these problems occur -- there are two
 possible default implementations for the date-based CBV (I say "default"
 because the point of CBVs is to let you override the bits you want):
 - use the default time zone (`settings.TIME_ZONE`)
   - the same items will always be displayed at the same URL, and the
 `DateDetailView` URLs will be permalinks
   - the date of the items, as displayed to the end user, may not match the
 URL
 - use the current time zone (the end user's time zone) -- this is what
 Django currently does
   - the same URL may display different items
   - the date of the items will always match the URL

 Both solutions are bound to annoy a subset of Django users. I've chosen
 the second one because I've heard "this page displays items for yesterday
 / tomorrow!" more often "the URL changes depending on the user!". Also,
 Django consistently works in the default time zone in the model layer and
 in the current time zone in the view / template layer. That said, to be
 honest, the CBVs span these layers, and I hesitated a lot before deciding
 to use the current time zone.

 Finally, when implementing this, I also considered forbidding date-based
 CBVs backed on `DateTimeField`s when `USE_TZ = True`. But they work
 perfectly when the current time zone isn't set per-user and stays
 identical to the default time zone, so I preferred to leave them available
 and add a warning in the docs.

 

 If you think my decisions in this area are incorrect -- which is totally
 possible as I got very little feedback during the implementation of these
 parts -- please start a discussion on the django-developers mailing-list.

 For now I will mark this "wontfix" because you're seeing a known behavior.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18803: Django FormWizard.as_view condition_dict callable called multiple times?

2012-08-20 Thread Django

#18803: Django FormWizard.as_view condition_dict callable called multiple times?
-+-
 Reporter:   |  Owner:  nobody
  mikewatsup@…   | Status:  new
 Type:  Bug  |Version:  1.4
Component:   |   Keywords:  form wizard, as_view,
  contrib.formtools  |  condition_dict argument
 Severity:  Release  |  Has patch:  0
  blocker|  UI/UX:  0
 Triage Stage:   |
  Unreviewed |
Easy pickings:  0|
-+-
 The following is a snippet of how I have setup my FormWizard. When I hit
 this view function, 'bar' gets printed once and 'foo' gets printed 7
 times:

 {{{
 #!python
 # views.py
 def _show_repair_item_form_condition(wizard):
 print 'foo'
 return True

 @login_required
 def workshop(request):
 print 'bar'
 cw = WorkshopWizard.as_view([WorkshopRepairItemFormSet, EmptyForm],
 condition_dict={'0': _show_repair_item_form_condition})
 return cw(request)
 }}}

 I have looked at the implmentation of the as_view function and can't find
 any trace of a bug causing this to happen. There is no documentation on
 the web about this issue either.

 Any ideas?

 Thanks, Mike

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #14694: defer() doesn't work with reverse relations

2012-08-20 Thread Django

#14694: defer() doesn't work with reverse relations
-+-
 Reporter:  sayane   |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  defer only   |  Needs documentation:  0
  OneToOneField reverse  |  Patch needs improvement:  0
  relationship   |UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by DrMeers):

 akaariai do you want to create another ticket before we close/commit this
 one so it doesn't get forgotten?

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17818: Generic edit generic views don't create `fail_silently` success messages anymore.

2012-08-20 Thread Django

#17818: Generic edit generic views don't create `fail_silently` success messages
anymore.
-+-
 Reporter:  charettes|Owner:  charettes
 Type:  New feature  |   Status:  new
Component:  Generic views|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  views generic edit   | Triage Stage:  Accepted
  messages   |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by mjtamlyn):

 * cc: marc.tamlyn@… (added)
 * needs_docs:  0 => 1
 * version:  1.3 => master
 * needs_tests:  0 => 1


Comment:

 I'm +1 on this feature being reintroduced, but -1 on it being on by
 default, especially as this would constitute a backwards incompatibility
 to me. We have views around which create messages similar to this, and
 turning it back on by default would mean duplicate messages, or messages
 where none were expected.

 That said it's probably a useful feature by default, but I think there
 should be an upgrade path.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18801: This ticket only created to try and duplicate the bug

2012-08-20 Thread Django

#18801: This ticket only created to try and duplicate the bug
-+-
 Reporter:  javier@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Djangoproject.com|  Version:
  Web site   |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by anonymous):

 * status:  new => closed
 * needs_better_patch:   => 0
 * resolution:   => fixed
 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18802: This ticket only created to try and duplicate the bug

2012-08-20 Thread Django

#18802: This ticket only created to try and duplicate the bug
-+-
 Reporter:  javier@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Djangoproject.com|  Version:
  Web site   |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by anonymous):

 * status:  new => closed
 * needs_better_patch:   => 0
 * resolution:   => fixed
 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18063: repr() should return only ascii, not unicode

2012-08-20 Thread Django

#18063: repr() should return only ascii, not unicode
-+-
 Reporter:  guettli  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 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 Simon Meers ):

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


Comment:

 In [3fce0d2a9162cf6e749a6de0b18890dea8955e89]:
 {{{
 #!CommitTicketReference repository=""
 revision="3fce0d2a9162cf6e749a6de0b18890dea8955e89"
 Fixed #18063 -- Avoid unicode in Model.__repr__ in python 2

 Thanks guettli and mrmachine.
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 3fce0d: Fixed #18063 -- Avoid unicode in Model.repr in...

2012-08-20 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3fce0d2a9162cf6e749a6de0b18890dea8955e89
  
https://github.com/django/django/commit/3fce0d2a9162cf6e749a6de0b18890dea8955e89
  Author: Simon Meers 
  Date:   2012-08-19 (Sun, 19 Aug 2012)

  Changed paths:
M django/db/models/base.py
M tests/regressiontests/model_regress/tests.py

  Log Message:
  ---
  Fixed #18063 -- Avoid unicode in Model.__repr__ in python 2

Thanks guettli and mrmachine.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18802: This ticket only created to try and duplicate the bug

2012-08-20 Thread Django

#18802: This ticket only created to try and duplicate the bug
+
 Reporter:  javier@…|  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Djangoproject.com Web site  |Version:
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  1
+
 https://code.djangoproject.com/ticket/18788 says unregistered unlogged
 users can't create tickets. This ticket is a replication test. If the
 ticket goes through, I will try and cancel it. If it doesn't, I will
 comment the above ticket 18788 as "bug reproduced".

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18801: This ticket only created to try and duplicate the bug

2012-08-20 Thread Django

#18801: This ticket only created to try and duplicate the bug
+
 Reporter:  javier@…|  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Djangoproject.com Web site  |Version:
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  1
+
 https://code.djangoproject.com/ticket/18788 says unregistered unlogged
 users can't create tickets. This ticket is a replication test. If the
 ticket goes through, I will try and cancel it. If it doesn't, I will
 comment the above ticket 18788 as "bug reproduced".

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18661: special characters like "é" or "è" in sqlite3 file path raise a "sqlite3.OperationalError: unable to open database file"

2012-08-20 Thread Django

#18661: special characters like "é" or "è" in sqlite3 file path raise a
"sqlite3.OperationalError: unable to open database file"
-+-
 Reporter:  oncleben31   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  windows  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by akaariai):

 The settings snippet seems to be missing the most important part of the
 information, the database's NAME. Make sure the name is an unicode string,
 something like this:
 {{{
 'NAME': u'name_containing_é'
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18661: special characters like "é" or "è" in sqlite3 file path raise a "sqlite3.OperationalError: unable to open database file"

2012-08-20 Thread Django

#18661: special characters like "é" or "è" in sqlite3 file path raise a
"sqlite3.OperationalError: unable to open database file"
-+-
 Reporter:  oncleben31   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  windows  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by javier@…):

 * keywords:   => windows
 * needs_tests:  0 => 1


Comment:

 Under linux, django will run fine with a sqlite database with a non-ascii
 pathname. However, it will print out a UnicodeWarning. This is the output
 of django manage.py runserver:
 {{{
 (...)
 Django version 1.5.dev20120820010350, using settings
 'ticket18661.settings'
 Development server is running at http://127.0.0.1:8000/
 Quit the server with CONTROL-C.
 /home/kandinski/.virtualenvs/django-
 bug-18661/src/django/django/db/backends/sqlite3/base.py:344:
 UnicodeWarning: Unicode unequal comparison failed to convert both
 arguments to Unicode - interpreting them as being unequal
   if self.settings_dict['NAME'] != ":memory:":
 [20/Aug/2012 01:25:08] "GET /admin/ HTTP/1.1" 200 3301
 [20/Aug/2012 01:26:06] "GET /admin/auth/user/ HTTP/1.1" 200 6059
 [20/Aug/2012 01:26:06] "GET /admin/jsi18n/ HTTP/1.1" 200 2164
 [20/Aug/2012 01:26:13] "GET /admin/auth/user/add/ HTTP/1.1" 200 4615
 [20/Aug/2012 01:26:13] "GET /admin/jsi18n/ HTTP/1.1" 200 2164
 [20/Aug/2012 01:26:25] "POST /admin/auth/user/add/ HTTP/1.1" 302 0
 [20/Aug/2012 01:26:25] "GET /admin/auth/user/2/ HTTP/1.1" 200 12995
 [20/Aug/2012 01:26:25] "GET /admin/jsi18n/ HTTP/1.1" 200 2164
 }}}
 And a snippet from my settings:
 {{{
 # Django settings for ticket18661 project.
 # coding: utf8
 (...)
 DATABASES = {
 'default': {
 'ENGINE': 'django.db.backends.sqlite3', # Add
 'postgresql_psycopg2', 'mysql', 'sqlite3' or 'oracle'.
 (...)
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18794: When timezone support is enabled, permalinks for DateDetailView are impossible.

2012-08-20 Thread Django

#18794: When timezone support is enabled, permalinks for DateDetailView are
impossible.
---+--
 Reporter:  void   |Owner:  aaugustin
 Type:  Bug|   Status:  new
Component:  Generic views  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  timezone, tz   | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by aaugustin):

 * owner:  nobody => aaugustin
 * status:  reopened => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18794: When timezone support is enabled, permalinks for DateDetailView are impossible.

2012-08-20 Thread Django

#18794: When timezone support is enabled, permalinks for DateDetailView are
impossible.
---+--
 Reporter:  void   |Owner:  nobody
 Type:  Bug|   Status:  reopened
Component:  Generic views  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  timezone, tz   | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by aaugustin):

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


Comment:

 My first impression was that the OP is right, but this is an expected
 behavior.

 I'd like to double check this before closing the ticket. 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

73 matches

Mail list logo