Re: [Django] #20034: Upload handlers provide no way to retrieve previously parsed POST variables

[Django]

#20034: Upload handlers provide no way to retrieve previously parsed POST 
variables
--+--
 Reporter:  rfkrocktk@…   |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--
Changes (by rfkrocktk@…):

 * has_patch:  0 => 1
 * type:  Uncategorized => New feature


-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20034: Upload handlers provide no way to retrieve previously parsed POST variables

[Django]

#20034: Upload handlers provide no way to retrieve previously parsed POST 
variables
---+--
 Reporter:  rfkrocktk@…|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Core (Other)   |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by rfkrocktk@…):

 Here's a workaround I came up with by adapting the Django code in a custom
 handler: http://stackoverflow.com/a/15377990/128967

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20034: Upload handlers provide no way to retrieve previously parsed POST variables

[Django]

#20034: Upload handlers provide no way to retrieve previously parsed POST 
variables
---+--
 Reporter:  rfkrocktk@…|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Core (Other)   |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by rfkrocktk@…):

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


Comment:

 Pull request with patch here: https://github.com/django/django/pull/898

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20034: Upload handlers provide no way to retrieve previously parsed POST variables

[Django]

#20034: Upload handlers provide no way to retrieve previously parsed POST 
variables
---+
 Reporter:  rfkrocktk@…|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Core (Other)   |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 In a custom Django upload handler like the one here, it is impossible to
 get other POST variables sent along with the multipart request until the
 handler has completed the upload entirely. Often, it'd be nice to be able
 to grab the variables as they're parsed to do something with them.
 Essentially, a method should be added to
 django.core.files.uploadhandler.FileUploadHandler called something like
 "variable_complete" which would provide the name and content type of each
 non-file variable passed with the multipart request:

 {{{
 class FileUploadHandler:

 # ...
 def variable_complete(self, variable_name, variable_value):
 """
 Called after a POST variable has been successfully parsed from the
 multipart request.
 """
 pass
 }}}

 This would save me the trouble of manually having to parse the multipart
 request myself in "handle_raw_input".

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #5586: Comments are not allowed in json fixtures

[Django]

#5586: Comments are not allowed in json fixtures
-+-
 Reporter:  jwickers@…   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Core |  Version:  master
  (Serialization)|   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:  json fixture |  Unreviewed
  comment|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by hobsonlane@…):

 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


Comment:

 You could implement an ignore of any "__comment" object attribute names
 (at the level of "pk") to make Django fixtures comment-friendly without
 violating the "strict subset of json" rule.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20031: validators.EmailValidator

[Django]

#20031: validators.EmailValidator
--+--
 Reporter:  Elec  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  Version:  1.5
 Severity:  Normal|   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 claudep):

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


Comment:

 Duplicate of #12027

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19964: A query including other query affects and breaks the first one

[Django]

#19964: A query including other query affects and breaks the first one
-+-
 Reporter:  Kronuz   |Owner:  akaariai
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  fixed
 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|
-+-

Comment (by akaariai):

 I solved this with 1) after all.

 2) ended up being too clever (patch is available from:
 
https://github.com/akaariai/django/commit/22c6136adb7eec3cca366511d3b4d29ff7509282).
 The two main problems is that it is hard to verify everything is actually
 using alias_id instead of alias, and that I have a feeling that sometimes
 you really want to have the alias instead of an ID in the leaf structures.
 Also, if you don't happen to have quote_name_unless_alias available, then
 the alias_id alone is useless (gis has this problem, and it isn't solved
 in the patch for 2).

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #12380: Shouldn't the pluralize filter consider 0 to be singular?

[Django]

#12380: Shouldn't the pluralize filter consider 0 to be singular?
-+-
 Reporter:  aleray   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Template system  |  Version:  1.5
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  pluralize| Triage Stage:
  templatetag|  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
 * resolution:   => invalid


Comment:

 I think that `pluralize` is mainly targeted to the English language. For
 any other language, you are probably better off creating your own
 specialized filter. You can then propose it as an external app or even as
 part of a localflavor.

 Please discuss it on django-dev first, and if a real solution emerges,
 then reopen the ticket.

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

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

Re: [Django] #19964: A query including other query affects and breaks the first one

[Django]

#19964: A query including other query affects and breaks the first one
-+-
 Reporter:  Kronuz   |Owner:  akaariai
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  fixed
 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 Anssi Kääriäinen ):

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


Comment:

 In [changeset:"d744c550d51955fd623897884446b7f34318e94d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d744c550d51955fd623897884446b7f34318e94d"
 Fixed #19964 -- Removed relabel_aliases from some structs

 Before there was need to have both .relabel_aliases() and .clone() for
 many structs. Now there is only relabeled_clone() for those structs
 where alias is the only mutable attribute.
 }}}

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] d744c5: Fixed #19964 -- Removed relabel_aliases from some ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d744c550d51955fd623897884446b7f34318e94d
  
https://github.com/django/django/commit/d744c550d51955fd623897884446b7f34318e94d
  Author: Anssi Kääriäinen 
  Date:   2013-03-12 (Tue, 12 Mar 2013)

  Changed paths:
M django/db/models/fields/__init__.py
M django/db/models/fields/related.py
M django/db/models/sql/aggregates.py
M django/db/models/sql/datastructures.py
M django/db/models/sql/expressions.py
M django/db/models/sql/query.py
M django/db/models/sql/where.py
M tests/queries/models.py
M tests/queries/tests.py

  Log Message:
  ---
  Fixed #19964 -- Removed relabel_aliases from some structs

Before there was need to have both .relabel_aliases() and .clone() for
many structs. Now there is only relabeled_clone() for those structs
where alias is the only mutable attribute.



-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19438: Install docs - admin static files - clarification

[Django]

#19438: Install docs - admin static files - clarification
-+-
 Reporter:  bb42 |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:  wontfix
 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
-+-

Comment (by aaugustin):

 If you've followed my work on the docs you know very well that this isn't
 my philosophy.

 Sorry, I shouldn't have spent 10 minutes replying to you. Please just
 ignore 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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20033: Bug: collecstatic makes static files executable

[Django]

#20033: Bug: collecstatic makes static files executable
-+
 Reporter:  jon@…|  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  contrib.staticfiles  |Version:  1.4
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 The static files in my app directories have mode 0664. After calling
 `./manage.py collectstatic` the collected static files have a mode of
 0775. Why is the mode changed to executable? This seems incorrect and
 unintentional.

 My app static directory: `-rw-rw-r-- 1 jon jon 1614 Mar  7 14:07 base.css`

 My collected static directory: `-rwxrwxr-x 1 jon jon 1614 Mar 12 12:11
 base.css`

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20032: Allow override_settings to delete settings

[Django]

#20032: Allow override_settings to delete settings
-+-
 Reporter:  coolRR   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Testing framework|   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 claudep):

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


Comment:

 You can do that currently by deleting a setting when settings are
 overriden, something like:

 {{{
 @override_settings()
 def test_something(self):
 del settings.SOME_SETTING
 ...
 }}}

 Sufficient or not? A documentation issue?

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

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

Re: [Django] #2705: gmekorgakuqq (was: ubnbklnqgvuu)

[Django]

#2705: gmekorgakuqq
-+-
 Reporter:  Hawkeye  |Owner:
 Type:  New feature  |  brunobraga
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  bmbqvrwktljo | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by kowyjcelagcx):

 * keywords:  mfobltctvbqd => bmbqvrwktljo


Comment:

 many thanks for this msmfbseozs http://www.bbxybfptzhcw.com";>click here 3:-) I love bats, O:)
 ieslvxletl [url="http://www.bbxybfptzhcw.net"]or here[/url] :-/ looks
 good, O:-) tdeipfmdse http://bbxybfptzhcw.info =( hcg diet, 3:-)
 okkjsoobyq [url=http://bbxybfptzhcw.ru]xectxmlvlv[/url] >:o thanks, 3:-)
 uhbxsysvls [link=http://bbxybfptzhcw.se]otrajyafjy[/link] :V sounds 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 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #2705: ubnbklnqgvuu (was: [patch] Add optional FOR UPDATE clause to QuerySets)

[Django]

#2705: ubnbklnqgvuu
-+-
 Reporter:  Hawkeye  |Owner:
 Type:  New feature  |  brunobraga
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  mfobltctvbqd | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by ezrfkddnvsdp):

 * keywords:   => mfobltctvbqd
 * ui_ux:   => 0
 * easy:   => 0


Comment:

 wonderful site thanks htmuhxtoia http://www.hkfhukehoqqx.com";>click here O:-) hcg diet, :D
 dissxebnlm [url="http://www.hkfhukehoqqx.net"]or here[/url] :-/ cheap
 insurance, =( chvgfdsqrk http://hkfhukehoqqx.info :-( hcg diet, =)
 jiphunbwxq [url=http://hkfhukehoqqx.ru]giaqjajsbt[/url] ;) seo expert, :D
 sdkdwynbnj [link=http://hkfhukehoqqx.se]djiasdwwtq[/link] :'( find out, :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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19438: Install docs - admin static files - clarification

[Django]

#19438: Install docs - admin static files - clarification
-+-
 Reporter:  bb42 |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:  wontfix
 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
-+-

Comment (by bb42):

 I can not follow your arguments, the current docs are unclear, and the
 staticfiles app can not be understood completely and configured correctly
 quickly.
 I spent two hours after learning that the apache-alias is the reasonable
 solution; and I admin and configure web-apps for years. The basic-usage
 paragraph just did not work for me (debian).
 And "people how can't write an Alias directive by themselves" deploy tons
 of non-django apps on their webserver.
 The idea that you should only use what you understand completely is very
 .. romantic. Did you ever take a plane?
 But I understood your point about the Django philosophy, something like
 "Let's keep it just as complicated so that current PHP users stay away."

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20032: Allow override_settings to delete settings

[Django]

#20032: Allow override_settings to delete settings
--+
 Reporter:  coolRR|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Testing framework |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 `override_settings` is used to change settings' values. Sometimes you want
 to delete a setting (not just set it to an empty value), and then have it
 restored later. `override_settings` should be able to do this, probably by
 using some kind of constant like `DELETE_FROM_SETTINGS` as the value given
 to 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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20031: validators.EmailValidator

[Django]

#20031: validators.EmailValidator
--+
 Reporter:  Elec  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Core (Other)  |Version:  1.5
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Email validator not correct chek email address with dot at end domain
 name:

 {{{
 >>> from django.core import validators
 >>> bool(validators.EmailValidator('boglache...@mail.ru.'))
 True
 }}}

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

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

Re: [Django] #12380: Shouldn't the pluralize filter consider 0 to be singular?

[Django]

#12380: Shouldn't the pluralize filter consider 0 to be singular?
-+-
 Reporter:  aleray   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Template system  |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  pluralize| Triage Stage:
  templatetag|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by etienned):

 * status:  closed => new
 * severity:   => Normal
 * type:   => Uncategorized
 * component:  Contrib apps => Template system
 * version:  1.1 => 1.5
 * easy:   => 0
 * ui_ux:   => 0
 * resolution:  invalid =>


Comment:

 And what about other languages such as French where the plural form is not
 use for zero (see Wikipedia article)? Maybe `pluralize` should take into
 account the active language and do the right thing for each language? I
 know this is not simple.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20030: django.db.backends.BaseDatabaseWrapper.supports_transactions eats database exceptions

[Django]

#20030: django.db.backends.BaseDatabaseWrapper.supports_transactions eats 
database
exceptions
-+-
 Reporter:  gcc  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 As of yesterday, this code is deprecated.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20030: django.db.backends.BaseDatabaseWrapper.supports_transactions eats database exceptions

[Django]

#20030: django.db.backends.BaseDatabaseWrapper.supports_transactions eats 
database
exceptions
--+
 Reporter:  gcc   |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.5
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+
 When there's a problem with the database configuration, running tests can
 generate this error:

 {{{
 ==
 ERROR: test_admin_interface_can_view_curriculum
 (lessons.tests.LessonsAppTest)
 --
 Traceback (most recent call last):
   File
 
"/home/installuser/Dropbox/projects/ischool/user_manager/django/project/.ve/local/lib/python2.7
 /site-packages/django/test/testcases.py", line 259, in __call__
 self._pre_setup()
   File
 
"/home/installuser/Dropbox/projects/ischool/user_manager/django/project/intranet_binder/test_utils.py",
 line 205, in _pre_setup
 super(AptivateEnhancedTestCase, self)._pre_setup()
   File
 
"/home/installuser/Dropbox/projects/ischool/user_manager/django/project/.ve/local/lib/python2.7
 /site-packages/django/test/testcases.py", line 479, in _pre_setup
 self._fixture_setup()
   File
 
"/home/installuser/Dropbox/projects/ischool/user_manager/django/project/.ve/local/lib/python2.7
 /site-packages/django/test/testcases.py", line 829, in _fixture_setup
 if not connections_support_transactions():
   File
 
"/home/installuser/Dropbox/projects/ischool/user_manager/django/project/.ve/local/lib/python2.7
 /site-packages/django/test/testcases.py", line 816, in
 connections_support_transactions
 for conn in connections.all())
   File
 
"/home/installuser/Dropbox/projects/ischool/user_manager/django/project/.ve/local/lib/python2.7
 /site-packages/django/test/testcases.py", line 816, in 
 for conn in connections.all())
   File
 
"/home/installuser/Dropbox/projects/ischool/user_manager/django/project/.ve/local/lib/python2.7
 /site-packages/django/utils/functional.py", line 43, in __get__
 res = instance.__dict__[self.func.__name__] = self.func(instance)
   File
 
"/home/installuser/Dropbox/projects/ischool/user_manager/django/project/.ve/local/lib/python2.7
 /site-packages/django/db/backends/__init__.py", line 455, in
 supports_transactions
 self.connection.leave_transaction_management()
   File
 
"/home/installuser/Dropbox/projects/ischool/user_manager/django/project/.ve/local/lib/python2.7
 /site-packages/django/db/backends/__init__.py", line 138, in
 leave_transaction_management
 "Transaction managed block ended with pending COMMIT/ROLLBACK")
 TransactionManagementError: Transaction managed block ended with pending
 COMMIT/ROLLBACK
 }}}

 Which totally hides the nature of the error, which was:

 {{{
 Traceback (most recent call last):
   File
 
"/home/installuser/Dropbox/projects/ischool/user_manager/django/project/.ve/local/lib/python2.7
 /site-packages/django/test/testcases.py", line 259, in __call__
 self._pre_setup()
   File
 
"/home/installuser/Dropbox/projects/ischool/user_manager/django/project/intranet_binder/test_utils.py",
 line 205, in _pre_setup
 super(AptivateEnhancedTestCase, self)._pre_setup()
   File
 
"/home/installuser/Dropbox/projects/ischool/user_manager/django/project/.ve/local/lib/python2.7
 /site-packages/django/test/testcases.py", line 479, in _pre_setup
 self._fixture_setup()
   File
 
"/home/installuser/Dropbox/projects/ischool/user_manager/django/project/.ve/local/lib/python2.7
 /site-packages/django/test/testcases.py", line 829, in _fixture_setup
 if not connections_support_transactions():
   File
 
"/home/installuser/Dropbox/projects/ischool/user_manager/django/project/.ve/local/lib/python2.7
 /site-packages/django/test/testcases.py", line 816, in
 connections_support_transactions
 for conn in connections.all())
   File
 
"/home/installuser/Dropbox/projects/ischool/user_manager/django/project/.ve/local/lib/python2.7
 /site-packages/django/test/testcases.py", line 816, in 
 for conn in connections.all())
   File
 
"/home/installuser/Dropbox/projects/ischool/user_manager/django/project/.ve/local/lib/python2.7
 /site-packages/django/utils/functional.py", line 43, in __get__
 res = instance.__dict__[self.func.__name__] = self.func(instance)
   File
 
"/home/installuser/Dropbox/projects/ischool/user_manager/django/project/.ve/local/lib/python2.7
 /site-packages/django/db/backends/__init__.py", line 445, in
 supports_transactions
 cursor.execute('CREATE TABLE ROLLBACK_TEST (X INT)')
   File
 
"/home/installuser/Dropbox/projects/ischool/user_manager/django/project/.ve/local

Re: [Django] #10164: sqlite3 backend: AutoField values aren't monotonically increasing

[Django]

#10164: sqlite3 backend: AutoField values aren't monotonically increasing
-+-
 Reporter:  malte|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  sqlite   |  Needs documentation:  1
  autoincrement  |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-

Comment (by anonymous):

 Is there any workaround to have not re-used ids for Django 1.4.3 model
 with SQLite?

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #14030: Use F() objects in aggregates(), annotates() and values()

[Django]

#14030: Use F() objects in aggregates(), annotates() and values()
-+-
 Reporter:  delfick  |Owner:  nate_b
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  aggregate, annotate  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by titanjer@…):

 * cc: titanjer@… (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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 679af4: Restricted a workaround for a bug in Python to the...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 679af4058dae8a54438d95ceb943f449e78448c1
  
https://github.com/django/django/commit/679af4058dae8a54438d95ceb943f449e78448c1
  Author: Aymeric Augustin 
  Date:   2013-03-12 (Tue, 12 Mar 2013)

  Changed paths:
M django/utils/decorators.py

  Log Message:
  ---
  Restricted a workaround for a bug in Python to the affected versions.



-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19944: django 1.5 is not compatible with pypy 1.9 because of django.test._doctest

[Django]

#19944: django 1.5 is not compatible with pypy 1.9 because of 
django.test._doctest
--+-
 Reporter:  kmike |Owner:  aaugustin
 Type:  Bug   |   Status:  assigned
Component:  Python 2  |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:  pypy  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-
Changes (by aaugustin):

 * component:  Testing framework => Python 2


-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19944: django 1.5 is not compatible with pypy 1.9 because of django.test._doctest

[Django]

#19944: django 1.5 is not compatible with pypy 1.9 because of 
django.test._doctest
---+-
 Reporter:  kmike  |Owner:  aaugustin
 Type:  Bug|   Status:  assigned
Component:  Testing framework  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords:  pypy   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by aaugustin):

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


Comment:

 I filed an issue against six to figure out whether this is an oversight in
 six or whether there's a better alternative:
 https://bitbucket.org/gutworth/six/issue/21/additional-object-model-
 compatibility

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20023: Admin Inline form validation must go in Model.clean() if AdminInline.form is not specified (was: Admin Inline form validation must go in Model.clean())

[Django]

#20023: Admin Inline form validation must go in Model.clean() if 
AdminInline.form
is not specified
-+-
 Reporter:  chris.freeman.pdx@…  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  admin inline form| Triage Stage:
  validation |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

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

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

Re: [Django] #20023: Admin Inline form validation must go in Model.clean()

[Django]

#20023: Admin Inline form validation must go in Model.clean()
-+-
 Reporter:  chris.freeman.pdx@…  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  admin inline form| Triage Stage:
  validation |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by chris.freeman.pdx@…):

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


Comment:

 I had a similar question open on StackOverflow
 (http://stackoverflow.com/questions/15330490/django-clean-field-is-not-
 being-called-for-updates-on-admin-inline-form).  It was answered by
 pointing to
 
(https://docs.djangoproject.com/en/dev/ref/contrib/admin/#django.contrib.admin.InlineModelAdmin.form),
 which implies the answer: Since no form is specified, a model will be
 used.  However, if I specify the form, but ''not'' the model, I get a
 {{{'model' is required attribute of 'ModelAdmin.inlines[0]'}}}.
 Also, if form defaults to ModelForm, then it is not obvious that
 ModelForm.clean_myfield() will not be called and only Model.clean() will
 be called.

 It would be much clearer if there were an Admin Inline example where both
 AdminInline.model and AdminInline.form were defined for the same class.

 The '''best''' solution would be to have a detailed example for the Admin
 validation precedence (including Inlines) similar to what is described for
 the model validation.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19944: django 1.5 is not compatible with pypy 1.9 because of django.test._doctest

[Django]

#19944: django 1.5 is not compatible with pypy 1.9 because of 
django.test._doctest
---+
 Reporter:  kmike  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords:  pypy   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by aaugustin):

 Now I remember. I was sloppy for this module. I skimmed Vinay Sajip's
 patch and applied it.

 Obviously I should have re-done the porting myself, like I did for every
 other module in Django.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20029: Django 1.5 / gunicorn 0.17.2 won't start

[Django]

#20029: Django 1.5 / gunicorn 0.17.2 won't start
-+-
 Reporter:  andreas@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.5
  commands)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:  django, gunicorn,|  Unreviewed
  connection |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 Please read TicketClosingReasons/UseSupportChannels

 `connection` isn't deprecated:
 https://docs.djangoproject.com/en/1.5/internals/deprecation/

 However, `gunicorn_django` is:
 https://docs.djangoproject.com/en/dev/howto/deployment/wsgi/gunicorn/

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20029: Django 1.5 / gunicorn 0.17.2 won't start

[Django]

#20029: Django 1.5 / gunicorn 0.17.2 won't start
-+-
 Reporter:  andreas@…|  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Core (Management |Version:  1.5
  commands)  |   Keywords:  django, gunicorn,
 Severity:  Normal   |  connection
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 Starting with Django 1.5
 {{{
 gunicorn_django --settings="project.settings" --pythonpath="."
 }}}

 Produces the following in the logfile:
 {{{
 Traceback (most recent call last):
   File "/home/aneumeier/web/env/local/lib/python2.7/site-
 packages/gunicorn/arbiter.py", line 485, in spawn_worker
 worker.init_process()
   File "/home/aneumeier/web/env/local/lib/python2.7/site-
 packages/gunicorn/workers/base.py", line 100, in init_process
 self.wsgi = self.app.wsgi()
   File "/home/aneumeier/web/env/local/lib/python2.7/site-
 packages/gunicorn/app/base.py", line 103, in wsgi
 self.callable = self.load()
   File "/home/aneumeier/web/env/local/lib/python2.7/site-
 packages/gunicorn/app/djangoapp.py", line 101, in load
 return mod.make_wsgi_application()
   File "/home/aneumeier/web/env/local/lib/python2.7/site-
 packages/gunicorn/app/django_wsgi.py", line 36, in make_wsgi_application
 if get_validation_errors(s):
   File "/home/aneumeier/web/env/local/lib/python2.7/site-
 packages/django/core/management/validation.py", line 28, in
 get_validation_errors
 from django.db import models, connection
   File "/home/aneumeier/web/env/local/lib/python2.7/site-
 packages/django/db/__init__.py", line 11, in 
 if settings.DATABASES and DEFAULT_DB_ALIAS not in settings.DATABASES:
   File "/home/aneumeier/web/env/local/lib/python2.7/site-
 packages/django/conf/__init__.py", line 52, in __getattr__
 self._setup(name)
   File "/home/aneumeier/web/env/local/lib/python2.7/site-
 packages/django/conf/__init__.py", line 47, in _setup
 self._wrapped = Settings(settings_module)
   File "/home/aneumeier/web/env/local/lib/python2.7/site-
 packages/django/conf/__init__.py", line 132, in __init__
 raise ImportError("Could not import settings '%s' (Is it on
 sys.path?): %s" % (self.SETTINGS_MODULE, e))
 ImportError: Could not import settings 'project.settings' (Is it on
 sys.path?): cannot import name connection
 }}}


 The way I read documentation for 1.5 is, that `connection` is deprectated.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19965: Problem with __unicode__ in your tutorial

[Django]

#19965: Problem with __unicode__ in your tutorial
-+-
 Reporter:  petergoldsborough@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  unicode, tutorial,   | Triage Stage:  Ready for
  python 3.2 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"e5c57fe1b429b401d47ac7bf8f9056b707c5ec07"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e5c57fe1b429b401d47ac7bf8f9056b707c5ec07"
 [1.5.x] Fixed #19965 - Added a warning that the tutorial is written for
 Python 2.

 Thanks itsallvoodoo for the patch.

 Backport of e1bafdbffa 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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] e5c57f: [1.5.x] Fixed #19965 - Added a warning that the tu...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: e5c57fe1b429b401d47ac7bf8f9056b707c5ec07
  
https://github.com/django/django/commit/e5c57fe1b429b401d47ac7bf8f9056b707c5ec07
  Author: Tim Graham 
  Date:   2013-03-12 (Tue, 12 Mar 2013)

  Changed paths:
M docs/intro/tutorial01.txt

  Log Message:
  ---
  [1.5.x] Fixed #19965 - Added a warning that the tutorial is written for 
Python 2.

Thanks itsallvoodoo for the patch.

Backport of e1bafdbffa 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19965: Problem with __unicode__ in your tutorial

[Django]

#19965: Problem with __unicode__ in your tutorial
-+-
 Reporter:  petergoldsborough@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  unicode, tutorial,   | Triage Stage:  Ready for
  python 3.2 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"e1bafdbffa6e8b13db12c995eaa53508e047c83c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e1bafdbffa6e8b13db12c995eaa53508e047c83c"
 Fixed #19965 - Added a warning that the tutorial is written for Python 2.

 Thanks itsallvoodoo for the 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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] e1bafd: Fixed #19965 - Added a warning that the tutorial i...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e1bafdbffa6e8b13db12c995eaa53508e047c83c
  
https://github.com/django/django/commit/e1bafdbffa6e8b13db12c995eaa53508e047c83c
  Author: Tim Graham 
  Date:   2013-03-12 (Tue, 12 Mar 2013)

  Changed paths:
M docs/intro/tutorial01.txt

  Log Message:
  ---
  Fixed #19965 - Added a warning that the tutorial is written for Python 2.

Thanks itsallvoodoo for the patch.



-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20028: transaction.atomic doesn't work on callable instances

[Django]

#20028: transaction.atomic doesn't work on callable instances
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (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 Aymeric Augustin ):

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


Comment:

 In [changeset:"885d98d24ac842708347c36644c61fc323c081ec"]:
 {{{
 #!CommitTicketReference repository=""
 revision="885d98d24ac842708347c36644c61fc323c081ec"
 Fixed #20028 -- Made atomic usable on callable instances.

 Thanks Anssi 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 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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 4846e2: Removed unused imports.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4846e2b744f4a376f9c364a90c5a852312a0ceaf
  
https://github.com/django/django/commit/4846e2b744f4a376f9c364a90c5a852312a0ceaf
  Author: Aymeric Augustin 
  Date:   2013-03-12 (Tue, 12 Mar 2013)

  Changed paths:
M django/contrib/gis/db/backends/spatialite/base.py

  Log Message:
  ---
  Removed unused imports.

One of these functions didn't exist anymore.


  Commit: 885d98d24ac842708347c36644c61fc323c081ec
  
https://github.com/django/django/commit/885d98d24ac842708347c36644c61fc323c081ec
  Author: Aymeric Augustin 
  Date:   2013-03-12 (Tue, 12 Mar 2013)

  Changed paths:
M django/db/transaction.py
M tests/transactions/tests.py

  Log Message:
  ---
  Fixed #20028 -- Made atomic usable on callable instances.

Thanks Anssi for the report.


Compare: https://github.com/django/django/compare/7e26f4cb799d...885d98d24ac8

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20028: transaction.atomic doesn't work on callable instances

[Django]

#20028: transaction.atomic doesn't work on callable instances
-+-
   Reporter:  aaugustin  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  master
  layer (models, ORM)|   Keywords:
   Severity:  Release|  Has patch:  0
  blocker|Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 It's the same problem as #13093, and it's a bug in Python:
 http://bugs.python.org/issue3445#msg100933
 Reported by Anssi.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19964: A query including other query affects and breaks the first one

[Django]

#19964: A query including other query affects and breaks the first one
-+-
 Reporter:  Kronuz   |Owner:  akaariai
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   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|
-+-

Comment (by akaariai):

 I have been thinking about this problem somewhat. It seems the current way
 of relabel_aliases() + clone() is fragile. Before, when `__deepcopy__` was
 used it was a bit less fragile.

 I have a couple of ideas how to improve the situation:
   1. Rename relabel_aliases() to relabeled_clone() for those things where
 the only mutable element is the alias. Thus, you can't accidentally only
 implement relabel_aliases() but not clone. This will also make cloning
 more efficient, as normal cloning will not need to clone all the
 structures. The clone needs to be done only on relabel time, and those
 times are rare.
   2. Instead of storing an alias in the outer structures (like the
 where.Constraint, SQLEvaluator, ...), just store an ID that the query can
 map back to alias. This way the outer structures are immutable, and there
 is no way to miss writing correct relabel_aliases().
   3. Do the same as in 2. but for all aliases in the query. Generate the
 final aliases at compile time and convert to those at as_sql() time
 everywhere.

 Of these 2. and 3. seem good as there is no way to miss or write incorrect
 relabel_aliases() methods. Both will be a lot of work, but no. 3 is even
 harder to implement correctly. No. 3 doesn't give any extra performance
 gain as the query structures need to be cloned in any case because alias
 is not the only mutable thing.

 So, I will see if no. 2 is easy to implement. If not, then no.1 it is.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20027: manage.py shebang should reflect used python executable

[Django]

#20027: manage.py shebang should reflect used python executable
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Python 3   |  Version:  1.5
 Severity:  Normal |   Resolution:  wontfix
 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 aaugustin):

 If you're going to share the code — either because it's open source, or
 with co-workers — this could still be a problem. (Rewriting sheebangs
 always causes trouble.)

 The recommended way to deal with this is to create a virtualenv with the
 Python binary you want, and to activate it whenever your work on your
 Django project.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20027: manage.py shebang should reflect used python executable

[Django]

#20027: manage.py shebang should reflect used python executable
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Python 3   |  Version:  1.5
 Severity:  Normal |   Resolution:  wontfix
 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 anonymous):

 Right, so what about using the name of the binary that was used? As in
 sys.executable.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20027: manage.py shebang should reflect used python executable

[Django]

#20027: manage.py shebang should reflect used python executable
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Python 3   |  Version:  1.5
 Severity:  Normal |   Resolution:  wontfix
 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:   => wontfix
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 There isn't any guarantee that the executables for Python 2 and 3 are
 called python and python3. They may just as well be called python2 and
 python.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20027: manage.py shebang should reflect used python executable

[Django]

#20027: manage.py shebang should reflect used python executable
+
 Reporter:  anonymous   |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Python 3|Version:  1.5
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 Hi,
 since Django now supports both Python 2 and Python 3, it seems that
 shebang in generated manage.py in new projects should reflect this.
 Currently, manage.py always points to "python", but IMHO when generated
 with python3, it should point to "python3". I think it makes sense to
 manage a project with python version that was used to generate 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.
For more options, visit https://groups.google.com/groups/opt_out.