date:20130710

Re: [Django] #20699: Extra blank choice '-----' when using models.fields.NullBooleanField with custom choices.

2013-07-10 Thread Django

#20699: Extra blank choice '-' when using models.fields.NullBooleanField 
with
custom choices.
-+-
 Reporter:  tomas.krajca@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  NullBooleanField |  Needs documentation:  0
  extra blank choice |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by anonymous):

 The code snippet is for django 1.5 as a quick patch, I could make a proper
 patch for the master.

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

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

Re: [Django] #20699: Extra blank choice '-----' when using models.fields.NullBooleanField with custom choices.

2013-07-10 Thread Django

#20699: Extra blank choice '-' when using models.fields.NullBooleanField 
with
custom choices.
-+-
 Reporter:  tomas.krajca@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  NullBooleanField |  Needs documentation:  0
  extra blank choice |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by tomas.krajca@…):

 * cc: tomas.krajca@… (added)


Comment:

 I like the option number 2 - detect the situation. The
 NullBooleanField.formfield could be easily fixed like this:


 {{{
 def formfield(self, **kwargs):
 defaults = {
 'form_class': forms.NullBooleanField,
 'required': not self.blank,
 'label': capfirst(self.verbose_name),
 'help_text': self.help_text}
 if self.choices:
 defaults['choices'] = self.get_choices(include_blank=False)

 defaults.update(kwargs)
 return super(NullBooleanField, self).formfield(**defaults)

 }}}
 This is inspired by BooleanField.formfield, I assume that if the user
 gives custom choices, he/she takes care of the blank field (it's a
 NullBooleanField so the Null option should be implied). This looks
 reasonably simple to me and I am happy to create a pull request if it is
 accepted. Would this also need tests?

 I think customizing the option labels is a reasonably common use case so I
 would be against not supporting it.

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

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

[Django] #20732: Writing your First Django App, part 3, error

2013-07-10 Thread Django

#20732: Writing your First Django App, part 3, error
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 When creating a template for the first poll application (Writing your
 first django app - part 3), the tutorial states:

 "First, create a directory called templates in your polls directory."

 Index.html cannot be found in this directory though, in the end I put my
 index.html in the templates/polls directory. So shouldn't the tutorial
 state:

 "First, create a directory called polls in your templates directory."

 Thanks for clearing that up

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

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

[Django] #20731: Requested enhancement of djangoproject.com website

2013-07-10 Thread Django

I've recently noticed that every time I visit the djangoproject.com
website, I have to select which version of the django docs to view. I am
aware that the URLs reflect which version of the documentation to view,
but I invariably Google the question to see if there is an answer on
StackOverflow or elsewhere, before clicking on the relevant link displayed
in my Google search results and ending up back on the django docs website.

I'd like to humbly request an enhancement to the site where after I've
chosen a version of the django docs to view, the site remembers which
version I'm viewing (perhaps be setting a cookie), and upon subsequent
visits, the site does not ask me which version of the django docs to view.

Cordially,

John O'Brien

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

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

Re: [Django] #542: ujfzhjptfdrw (was: byzosywnmsnv)

2013-07-10 Thread Django

#542: ujfzhjptfdrw
-+-
 Reporter:  Jason Huggins|Owner:  wilson
 Type:  enhancement  |   Status:  closed
Component:  contrib.admin|  Version:  1.4-rc-1
 Severity:  trivial  |   Resolution:  wontfix
 Keywords:  tjxnywpotvxp | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by flhdjrlmfwhu):

 * keywords:  xgwkhhorfnzz => tjxnywpotvxp


Comment:

 loving the site qjwmaqyxtk http://www.fjofjvbmcrua.com";>click
 here :( rdqsborbslwfwgk, :( vyakzbodbg
 [url="http://www.fjofjvbmcrua.net"]or here[/url] =) eoujmqxf, :3
 gcpladycmp http://fjofjvbmcrua.info >:-O ylgyd, O:-) mweiaiohnr
 [url=http://fjofjvbmcrua.ru]qzgqzzsyby[/url] :-X ylgyd, <3 xgcyoankvv
 [link=http://fjofjvbmcrua.se]fvrmfitotw[/link] :-X ylgyd, :|]

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

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

Re: [Django] #542: byzosywnmsnv (was: [patch] Add an "or cancel" link to add, edit, and delete admin views.)

2013-07-10 Thread Django

#542: byzosywnmsnv
-+-
 Reporter:  Jason Huggins|Owner:  wilson
 Type:  enhancement  |   Status:  closed
Component:  contrib.admin|  Version:  1.4-rc-1
 Severity:  trivial  |   Resolution:  wontfix
 Keywords:  xgwkhhorfnzz | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by nmbmrzzqjuwl):

 * keywords:  cancel link => xgwkhhorfnzz
 * ui_ux:   => 0
 * version:   => 1.4-rc-1
 * easy:   => 0


Comment:

 incredible post eafeaefzcw http://www.mwpwxkkleukd.com";>click
 here :3 yxsom, 8| cmcfhcehtr [url="http://www.mwpwxkkleukd.net"]or
 here[/url] :/ fhljyyblsuoxzfd, :-/ mkogsbzltl http://mwpwxkkleukd.info :[
 grtcdju, 8| byhczhykhz [url=http://mwpwxkkleukd.ru]jtfoybrzbw[/url] <3
 yxsom, B-| oafnucuwhv [link=http://mwpwxkkleukd.se]uuwcgplrly[/link] :-*
 aivleeec, :D

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

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

Re: [Django] #20729: Django Admin site activated by default

2013-07-10 Thread Django

#20729: Django Admin site activated by default
---+--
 Reporter:  deelo555@… |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.5
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by russellm):

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


Comment:

 Feature, not bug. We made a decision to rationalize the startup template
 for new projects, and given that 99% of Django projects -- and 100% of
 projects running the tutorial -- use the admin, we opted to turn it on by
 default. If you don't want the admin, you can always turn it off.

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

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

Re: [Django] #11762: Chilean localflavor - Regions, Provinces and Comunas

2013-07-10 Thread Django

#11762: Chilean localflavor - Regions, Provinces and Comunas
-+-
 Reporter:  jkunst   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  contrib.localflavor  |  Version:  1.1
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  chile, region,   | Triage Stage:  Accepted
  comuna, provincia, |  Needs documentation:  0
  localflavorsplit   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-

Comment (by glarrain):

 Replying to [comment:7 aaugustin]:
 > `django.contrib.localflavor` is now deprecated — see
 https://docs.djangoproject.com/en/dev/ref/contrib/localflavor/
 >
 > A repository was created for each localflavor at
 https://github.com/django/django-localflavor-**? (Replace ** with the
 country code.)
 >
 > If you're still interested in this ticket, could you create a pull
 request on that repository?
 >
 > Sorry for not resolving this issue earlier, and thanks for your input!

 The correct link is
 https://docs.djangoproject.com/en/1.5/ref/contrib/localflavor
 /#deprecation-policy (the abovementioned was too general and returns a
 404)

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

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

[Django] #20730: Error in docs / auth / Programmatically creating permissions

2013-07-10 Thread Django

#20730: Error in docs / auth / Programmatically creating permissions
---+---
 Reporter:  glarrain   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  master
 Severity:  Normal |   Keywords:  permissions, content type
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  1  |  UI/UX:  0
---+---
 In the example included in
 https://docs.djangoproject.com/en/dev/topics/auth/default
 /#programmatically-creating-permissions (versions 1.4, 1.5, and dev) there
 is a mistake in the sentence

 {{{
 content_type = ContentType.objects.get(app_label='myapp',
 model='BlogPost')
 }}}

 since that will raise

 {{{
 DoesNotExist: ContentType matching query does not exist.
 }}}

 since `model` argument must be in lower case. Thus the correct sentence
 would be

 {{{
 content_type = ContentType.objects.get(app_label='myapp',
 model='blogpost')
 }}}

 Perhaps an overall improvement would be to use method `get_for_model` of
 `ContentTypeManager` instead of `get` because it

   "Returns the ContentType object for a given model, '''creating the
 ContentType if necessary'''. Lookups are cached so that '''subsequent
 lookups for the same model don't hit the database'''."

 In that case, the proposed solution is to replace the abovementioned
 sentence with:

 {{{
 from myapp.models import BlogPost
 content_type = ContentType.objects.get_for_model(BlogPost)
 }}}

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

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

Re: [Django] #10491: Passing a unicode-proxy to HttpResponse classes doesn't work

2013-07-10 Thread Django

#10491: Passing a unicode-proxy to HttpResponse classes doesn't work
-+-
 Reporter:  liangent |Owner:  ajeeshvt
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by claudep):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #19031: Add a warning that @override_settings may not work with DATABASES (was: Add a warning that @override_settings may not work with DATABASES and CACHES)

2013-07-10 Thread Django

#19031: Add a warning that @override_settings may not work with DATABASES
---+
 Reporter:  jonash |Owner:  joeri
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  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 timo):

 * needs_better_patch:  1 => 0
 * version:  1.4 => master


Comment:

 On further investigating of #20075, `CACHES` can be overridden but there
 are some caveats. I've updated the proposed documentation change with
 these details and removed `CACHES` from generating a warning.  New
 [https://github.com/django/django/pull/1348 PR].

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

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

Re: [Django] #20289: Unpickling of dynamic model classes broken in 1.5

2013-07-10 Thread Django

#20289: Unpickling of dynamic model classes broken in 1.5
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:  fixed
 Severity:  Release blocker  | 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 akaariai):

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


Comment:

 I think it is time to close this one. This ticket is still missing an
 example of the claimed regression. I believe the problem is actually in
 trying to use model pickling across versions. In my understanding that
 isn't officially supported.

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

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

Re: [Django] #20075: Cache session test fails when using a cache other than LocMemCache

2013-07-10 Thread Django

#20075: Cache session test fails when using a cache other than LocMemCache
--+
 Reporter:  mlarente  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.sessions  |  Version:  1.5
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"2f9378223d0c92447e2529d5eeaad7d301b78b84"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2f9378223d0c92447e2529d5eeaad7d301b78b84"
 [1.5.x] Fixed #20075 -- Fixed session test fail when using a cache other
 than LocMemCache.

 As override_settings was used after the initialization of the session
 backend,
 we need to use a new session backend here.

 Backport of 8c1cc4b3b0 from master
 }}}

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

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

[django/django] 2f9378: [1.5.x] Fixed #20075 -- Fixed session test fail wh...

2013-07-10 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 2f9378223d0c92447e2529d5eeaad7d301b78b84
  
https://github.com/django/django/commit/2f9378223d0c92447e2529d5eeaad7d301b78b84
  Author: Mathijs de Bruin 
  Date:   2013-07-10 (Wed, 10 Jul 2013)

  Changed paths:
M django/contrib/sessions/tests.py

  Log Message:
  ---
  [1.5.x] Fixed #20075 -- Fixed session test fail when using a cache other than 
LocMemCache.

As override_settings was used after the initialization of the session backend,
we need to use a new session backend here.

Backport of 8c1cc4b3b0 from master



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51ddb08c75ca3_33db649de411623c%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20075: Cache session test fails when using a cache other than LocMemCache

2013-07-10 Thread Django

#20075: Cache session test fails when using a cache other than LocMemCache
--+
 Reporter:  mlarente  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.sessions  |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by timo):

 This was fixed in master by 8c1cc4b3b04f639ae40bc806380bc4a9dd568eb0 (re-
 initializing the session backend). I will backport the fix to 1.5.x.

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

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

[Django] #20729: Django Admin site activated by default

2013-07-10 Thread Django

#20729: Django Admin site activated by default
---+
 Reporter:  deelo555@… |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 The latest version of Django the admin site is disabled by default

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

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

Re: [Django] #20429: Add QuerySet.update_or_create method

2013-07-10 Thread Django

#20429: Add QuerySet.update_or_create method
-+-
 Reporter:  tunixman |Owner:
 Type:  New feature  |  elektrrrus
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

 * stage:  Ready for checkin => Accepted


Comment:

 I've updated the patch, changing the signature of `get_or_create` and
 `update_or_create` to `(defaults=None, **kwargs)`. I'd like another person
 to review the patch before committing it.

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

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

Re: [Django] #14857: has_results cleanup

2013-07-10 Thread Django

#14857: has_results cleanup
---+--
 Reporter:  wkornewald |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:  duplicate
 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 timo):

 * resolution:  wontfix => duplicate
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


Comment:

 Duplicate of #17339 which has been merged.

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

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

Re: [Django] #20625: Custom Chainable QuerySets

2013-07-10 Thread Django

#20625: Custom Chainable QuerySets
-+-
 Reporter:  danols   |Owner:  loic84
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  QuerySet,|  Needs documentation:  0
  models.Manager, chainable  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by loic84):

 Squashed down to a single commit that applies on top of the latest master.
 Hopefully this is RFC.

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

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

Re: [Django] #20625: Custom Chainable QuerySets

2013-07-10 Thread Django

#20625: Custom Chainable QuerySets
-+-
 Reporter:  danols   |Owner:  loic84
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  QuerySet,|  Needs documentation:  0
  models.Manager, chainable  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by timo):

 Docs look good to me.

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

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

Re: [Django] #20728: name field on auth_permission too short

2013-07-10 Thread Django

#20728: name field on auth_permission too short
-+-
 Reporter:  pvilas@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  1.5
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  auth_permission, | Triage Stage:
  name   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

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


Comment:

 Duplicate of #8162.

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

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

Re: [Django] #10491: Passing a unicode-proxy to HttpResponse classes doesn't work

2013-07-10 Thread Django

#10491: Passing a unicode-proxy to HttpResponse classes doesn't work
---+
 Reporter:  liangent   |Owner:  ajeeshvt
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by anonymous):

 I only hit upon this bug a couple of days ago. My use case was fairly
 common: automatic redirection to the login screen via the login_required
 decorator with LOGIN_URL setting being a lazily reversed url.

 It used to work in Python 2.7 but fails in Python 3.3 inside urlparse()
 (that is assuming that HttpResponseRedirectBase has not changed lately).

 Considering that Django allows lazy url-reverse for several versions now,
 I think fixing this is important.

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

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

Re: [Django] #20723: model_to_dict requires True, False, or '' instead of 0, 1, or '' when NullBooleanField

2013-07-10 Thread Django

#20723: model_to_dict requires True, False, or '' instead of 0, 1, or '' when
NullBooleanField
-+-
 Reporter:  helen.mayhew@…   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 `model_to_dict` doesn't appear to be documented. I sort of understand your
 issue, but it seems like it may be fairly specific to your app and I'm not
 quite sure what documentation to add. Could you propose some text or a
 patch?

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

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

Re: [Django] #19196: Add tests/requirements.txt

2013-07-10 Thread Django

#19196: Add tests/requirements.txt
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"e8971345b4bf0e7ce2124d033ee3385919f47309"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e8971345b4bf0e7ce2124d033ee3385919f47309"
 [1.4.x] Fixed #19196 -- Added test/requirements

 Backport of 4d92a0bd86 from master
 }}}

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

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

[django/django] e89713: [1.4.x] Fixed #19196 -- Added test/requirements

2013-07-10 Thread GitHub

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: e8971345b4bf0e7ce2124d033ee3385919f47309
  
https://github.com/django/django/commit/e8971345b4bf0e7ce2124d033ee3385919f47309
  Author: Tim Graham 
  Date:   2013-07-10 (Wed, 10 Jul 2013)

  Changed paths:
M docs/internals/contributing/writing-code/unit-tests.txt
A tests/requirements/base.txt
A tests/requirements/mysql.txt
A tests/requirements/oracle.txt
A tests/requirements/postgres.txt

  Log Message:
  ---
  [1.4.x] Fixed #19196 -- Added test/requirements

Backport of 4d92a0bd86 from master



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51dd880869c00_34f1e81de089777%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 14b507: [1.5.x] Added a missing test requirement in the do...

2013-07-10 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 14b50739787d9bb69e763894f78b10971fe2bc63
  
https://github.com/django/django/commit/14b50739787d9bb69e763894f78b10971fe2bc63
  Author: Tim Graham 
  Date:   2013-07-10 (Wed, 10 Jul 2013)

  Changed paths:
M docs/internals/contributing/writing-code/unit-tests.txt

  Log Message:
  ---
  [1.5.x] Added a missing test requirement in the docs; refs #19196



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51dd87a411918_58d3785dd4115741%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19196: Add tests/requirements.txt

2013-07-10 Thread Django

#19196: Add tests/requirements.txt
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"14b50739787d9bb69e763894f78b10971fe2bc63"]:
 {{{
 #!CommitTicketReference repository=""
 revision="14b50739787d9bb69e763894f78b10971fe2bc63"
 [1.5.x] Added a missing test requirement in the docs; refs #19196
 }}}

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

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

[Django] #20728: name field on auth_permission too short

2013-07-10 Thread Django

#20728: name field on auth_permission too short
--+---
 Reporter:  pvilas@…  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  contrib.auth  |Version:  1.5
 Severity:  Normal|   Keywords:  auth_permission, name
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+---
 If the verbose_name of the table is over 80 characters the syncdb command
 will silently fail.

 The name field on auth_permissions table is too short to store if
 verbose_name are that long, so it doesn't update and you cannot assign
 permissions.

 The obvious workaround is to manually change the field length.

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

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

[django/django] 2e3250: [1.6.x] Added some missing test requirements in th...

2013-07-10 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 2e3250fc90499b2977c39ca8af8d0c245c9bcd77
  
https://github.com/django/django/commit/2e3250fc90499b2977c39ca8af8d0c245c9bcd77
  Author: Tim Graham 
  Date:   2013-07-10 (Wed, 10 Jul 2013)

  Changed paths:
M docs/internals/contributing/writing-code/unit-tests.txt

  Log Message:
  ---
  [1.6.x] Added some missing test requirements in the docs; refs #19196

Backport of 77856dc875 from master



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51dd85bb81c11_33ce9e1de4350cd%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19196: Add tests/requirements.txt

2013-07-10 Thread Django

#19196: Add tests/requirements.txt
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"2e3250fc90499b2977c39ca8af8d0c245c9bcd77"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2e3250fc90499b2977c39ca8af8d0c245c9bcd77"
 [1.6.x] Added some missing test requirements in the docs; refs #19196

 Backport of 77856dc875 from master
 }}}

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

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

Re: [Django] #19196: Add tests/requirements.txt

2013-07-10 Thread Django

#19196: Add tests/requirements.txt
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"77856dc875ca17cc86944e028e4c9a36b0b46dbe"]:
 {{{
 #!CommitTicketReference repository=""
 revision="77856dc875ca17cc86944e028e4c9a36b0b46dbe"
 Added some missing test requirements in the docs; refs #19196
 }}}

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

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

[django/django] 77856d: Added some missing test requirements in the docs; ...

2013-07-10 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 77856dc875ca17cc86944e028e4c9a36b0b46dbe
  
https://github.com/django/django/commit/77856dc875ca17cc86944e028e4c9a36b0b46dbe
  Author: Tim Graham 
  Date:   2013-07-10 (Wed, 10 Jul 2013)

  Changed paths:
M docs/internals/contributing/writing-code/unit-tests.txt

  Log Message:
  ---
  Added some missing test requirements in the docs; refs #19196



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51dd859ecdc0f_485d9dfddc684eb%40hookshot-fe6-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20727: cyrillic in django-admin

2013-07-10 Thread Django

#20727: cyrillic in django-admin
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Uncategorized  |  Version:  1.5
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by aaugustin):

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


Comment:

 This isn't a bug in Django; your `object_repr` method doesn't deal with
 unicode correctly. Please see TicketClosingReasons/UseSupportChannels.

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

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

Re: [Django] #897: Bi-Directional ManyToMany in Admin

2013-07-10 Thread Django

#897: Bi-Directional ManyToMany in Admin
---+
 Reporter:  anonymous  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by kux):

 For people who still bump into this, it might be worth checking
 https://github.com/kux/django-admin-extend

 It provides a mechanism for injecting bidirectional many-to-many fields in
 ModelAdmins that have already been defined by other apps.

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

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

Re: [Django] #19196: Add tests/requirements.txt

2013-07-10 Thread Django

#19196: Add tests/requirements.txt
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"13546cae9c7922088266c32a5be2bda77545a04b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="13546cae9c7922088266c32a5be2bda77545a04b"
 [1.5.x] Fixed #19196 -- Added test/requirements

 Backport of 4d92a0bd86 from master.
 }}}

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

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

[django/django] 13546c: [1.5.x] Fixed #19196 -- Added test/requirements

2013-07-10 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 13546cae9c7922088266c32a5be2bda77545a04b
  
https://github.com/django/django/commit/13546cae9c7922088266c32a5be2bda77545a04b
  Author: Tim Graham 
  Date:   2013-07-10 (Wed, 10 Jul 2013)

  Changed paths:
M docs/internals/contributing/writing-code/unit-tests.txt
A tests/requirements/base.txt
A tests/requirements/mysql.txt
A tests/requirements/oracle.txt
A tests/requirements/postgres.txt
A tests/requirements/py2.txt
A tests/requirements/py3.txt

  Log Message:
  ---
  [1.5.x] Fixed #19196 -- Added test/requirements

Backport of 4d92a0bd86 from master.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51dd7f2ab07cb_5cf123dde49766a%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20727: cyrillic in django-admin

2013-07-10 Thread Django

#20727: cyrillic in django-admin
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Hello,

 When I add Cyrillic strings into django-admin I alway get an error
 Warning at /admin/table/data/1/

 Incorrect string value: '\xD0\xA4\xD0\xB8\xD1\x80...' for column
 'object_repr' at row 1

 Request Method: POST
 Request URL:http://localhost:8000/admin/table/data/1/
 Django Version: 1.5.1
 Exception Type: Warning
 Exception Value:

 Incorrect string value: '\xD0\xA4\xD0\xB8\xD1\x80...' for column
 'object_repr' at row 1

 Exception Location: /usr/lib/python2.7/dist-
 packages/MySQLdb/cursors.py in _warning_check, line 92
 Python Executable:  /usr/bin/python
 Python Version: 2.7.3
 Python Path:

 ['/home/tmacbg/Web/polycontact',
  '/usr/local/lib/python2.7/dist-packages/setuptools-0.6c11-py2.7.egg',
  '/usr/local/lib/python2.7/dist-packages/Django-1.5.1-py2.7.egg',
  '/usr/local/lib/python2.7/dist-
 packages/django_grappelli-2.4.5-py2.7.egg',
  '/usr/local/lib/python2.7/dist-packages/Unidecode-0.04.13-py2.7.egg',
  '/usr/lib/python2.7',
  '/usr/lib/python2.7/plat-linux2',
  '/usr/lib/python2.7/lib-tk',
  '/usr/lib/python2.7/lib-old',
  '/usr/lib/python2.7/lib-dynload',
  '/usr/local/lib/python2.7/dist-packages',
  '/usr/lib/python2.7/dist-packages',
  '/usr/lib/python2.7/dist-packages/PIL',
  '/usr/lib/python2.7/dist-packages/gst-0.10',
  '/usr/lib/python2.7/dist-packages/gtk-2.0',
  '/usr/lib/pymodules/python2.7']

 Server time:Ср, 10 Юли 2013 16:53:09 +0300
 How can I  enter cyrillic strings ?!

 Thank you and have a nice day

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

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

[django/django] aecbaa: [1.6.x] Fixed #19196 -- Added test/requirements

2013-07-10 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: aecbaaed0c1a0d7da99a8d3deb9328ad2b5c601d
  
https://github.com/django/django/commit/aecbaaed0c1a0d7da99a8d3deb9328ad2b5c601d
  Author: Tim Graham 
  Date:   2013-07-10 (Wed, 10 Jul 2013)

  Changed paths:
M docs/internals/contributing/writing-code/unit-tests.txt
A tests/requirements/base.txt
A tests/requirements/mysql.txt
A tests/requirements/oracle.txt
A tests/requirements/postgres.txt
A tests/requirements/py2.txt
A tests/requirements/py3.txt
M tests/runtests.py

  Log Message:
  ---
  [1.6.x] Fixed #19196 -- Added test/requirements

Backport of 4d92a0bd86 from master.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51dd66e510dda_5b3ef8fde010036a%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19196: Add tests/requirements.txt

2013-07-10 Thread Django

#19196: Add tests/requirements.txt
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"aecbaaed0c1a0d7da99a8d3deb9328ad2b5c601d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="aecbaaed0c1a0d7da99a8d3deb9328ad2b5c601d"
 [1.6.x] Fixed #19196 -- Added test/requirements

 Backport of 4d92a0bd86 from master.
 }}}

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

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

Re: [Django] #16433: Missing 'help_text' in admin form when showing the back reference for a OneToOne field.

2013-07-10 Thread Django

#16433: Missing 'help_text' in admin form when showing the back reference for a
OneToOne field.
---+
 Reporter:  chris@…|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by frankoid):

 * cc: frankoid (added)


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

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

[django/django] 4d92a0: Fixed #19196 -- Added test/requirements

2013-07-10 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4d92a0bd8630affbb6f289317f71d60607d26369
  
https://github.com/django/django/commit/4d92a0bd8630affbb6f289317f71d60607d26369
  Author: Tim Graham 
  Date:   2013-07-10 (Wed, 10 Jul 2013)

  Changed paths:
M docs/internals/contributing/writing-code/unit-tests.txt
A tests/requirements/base.txt
A tests/requirements/mysql.txt
A tests/requirements/oracle.txt
A tests/requirements/postgres.txt
A tests/requirements/py2.txt
A tests/requirements/py3.txt
M tests/runtests.py

  Log Message:
  ---
  Fixed #19196 -- Added test/requirements



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51dd624528513_1a9e81de0486fe%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19196: Add tests/requirements.txt

2013-07-10 Thread Django

#19196: Add tests/requirements.txt
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"4d92a0bd8630affbb6f289317f71d60607d26369"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4d92a0bd8630affbb6f289317f71d60607d26369"
 Fixed #19196 -- Added test/requirements
 }}}

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

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

Re: [Django] #20718: Geoqueryset method do not return a value

2013-07-10 Thread Django

#20718: Geoqueryset method do not return a value
+--
 Reporter:  burton449geo@…  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  GIS |  Version:  1.5-rc-1
 Severity:  Normal  |   Resolution:  worksforme
 Keywords:  geodjango   | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by burton449geo@…):

 Ok, I understand that the methods do not return values but something seems
 to be wrong anyway

 bounds = Feature.objects.filter(id=feature.id).geojson()
 print(bounds.geojson)

 >>> ]>

 With Spatialite 4.0.0 the area() method just not work:
 bounds = Feature.objects.filter(id=feature.id).area()
 print(bounds.area)

 >>> no such table: spatial_ref_sys

 But the table spatial_ref_sys do exists in the db

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

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

Re: [Django] #20726: Django development server time different from server time

2013-07-10 Thread Django

#20726: Django development server time different from server time
+--
 Reporter:  ncatdesigner@…  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Uncategorized   |  Version:  1.5
 Severity:  Normal  |   Resolution:  worksforme
 Keywords:  time| 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):

 Actually, it happens regardless of the value of `USE_TZ`.

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

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

Re: [Django] #20726: Django development server time different from server time

2013-07-10 Thread Django

#20726: Django development server time different from server time
+--
 Reporter:  ncatdesigner@…  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Uncategorized   |  Version:  1.5
 Severity:  Normal  |   Resolution:  worksforme
 Keywords:  time| Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by claudep):

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


Comment:

 Yes, if your settings contain `USE_TZ=True` and a `TIME_ZONE` setting
 different from your current physical timezone, this may happen.

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

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

Re: [Django] #19196: Add tests/requirements.txt

2013-07-10 Thread Django

#19196: Add tests/requirements.txt
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by loic84):

 * stage:  Accepted => Ready for checkin


Comment:

 Looks good to me; I've tried the various requirements files in a fresh
 virtualenv.

 Optionally for GeoDjango we could have a paragraph in
 `internals/contributing/writing-code/unit-tests.txt` that links to
 https://docs.djangoproject.com/en/dev/ref/contrib/gis/install/.

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

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

46 matches

Mail list logo