date:20140519

Re: [Django] #22661: MakeMigrationTests placed inside MigrateTests class

2014-05-19 Thread Django

#22661: MakeMigrationTests placed inside MigrateTests class
-+-
 Reporter:  whoshuu  |Owner:  whoshuu
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:
Component:  Migrations   |  1.7-beta-2
 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 whoshuu):

 * has_patch:  0 => 1


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

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

Re: [Django] #22654: DecimalField and DECIMAL_SEPARATOR (in admin)

2014-05-19 Thread Django

#22654: DecimalField and DECIMAL_SEPARATOR (in admin)
--+-
 Reporter:  matija@…  |Owner:
 Type:  Bug   |   Status:  new
Component:  Forms |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Someday/Maybe
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-

Comment (by matija@…):

 ACTUALLY this is DJANGO problem. Remove type="number". The ValidationError
 on Django side is the issue, not browser side.

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

Re: [Django] #18729: Admin changelist view defaults to `DISTINCT`, unusable on reasonably sized databases

2014-05-19 Thread Django

#18729: Admin changelist view defaults to `DISTINCT`, unusable on reasonably 
sized
databases
-+-
 Reporter:  hcarvalhoalves   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin sql distinct   | Triage Stage:
  slow performance   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by AlexMalek):

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


Comment:

 I think it is a different issue.
 It is possible to alter the check that examines list_filter to determine
 if distinct() is needed based on if the field appears in the query/request
 but this does not address the deeper issues in #15819
 For example in Django 1.5.2 I think the following changes solves the
 issue:

 django/contrib/admin/util.py:
 20c20
 < def lookup_needs_distinct(opts, lookup_path, query_dict=None):
 ---
 > def lookup_needs_distinct(opts, lookup_path):
 29,31c29
 <  not field.field.unique) and
 <(query_dict is None or (field_name in
 ",".join(query_dict.keys(
 <   ):
 ---
 >  not field.field.unique)):

 django/contrib/admin/views/main.py:
 128c128
 <   field_path,
 lookup_params))
 ---
 >   field_path))

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

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

Re: [Django] #22661: MakeMigrationTests placed inside MigrateTests class

2014-05-19 Thread Django

#22661: MakeMigrationTests placed inside MigrateTests class
-+-
 Reporter:  whoshuu  |Owner:  whoshuu
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:
Component:  Migrations   |  1.7-beta-2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by whoshuu):

 Opened up a pull request for this
 [https://github.com/django/django/pull/2688 here].

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

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

Re: [Django] #21978: Add optional gunicorn support to runserver

2014-05-19 Thread Django

Comment (by berkerpeksag):

> I was thinking that if gunicorn is installed, then runserver would use
that automatically (passing data to --reload and --bind from the current
runserver options).

Ah, that is a good idea. Also, we can pass the `settings.DEBUG` setting to
Gunicorn's configration.

> Do you think that approach would be too limiting from a user
perspective?

No. I think that approach is a good start. It's a development server
afterall.

BTW, my WIP patch is at https://github.com/berkerpeksag/django/compare
/ticket-21978_gunicorn I will update it later.

Thanks!

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

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

Re: [Django] #22661: MakeMigrationTests placed inside MigrateTests class

2014-05-19 Thread Django

#22661: MakeMigrationTests placed inside MigrateTests class
-+-
 Reporter:  whoshuu  |Owner:  whoshuu
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:
Component:  Migrations   |  1.7-beta-2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by whoshuu):

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


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

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

Re: [Django] #22661: MakeMigrationTests placed inside MigrateTests class

2014-05-19 Thread Django

#22661: MakeMigrationTests placed inside MigrateTests class
-+-
 Reporter:  whoshuu  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Migrations   |  1.7-beta-2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timo):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Accepted
 * needs_tests:   => 0
 * needs_docs:   => 0


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

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

Re: [Django] #21978: Add optional gunicorn support to runserver

2014-05-19 Thread Django

#21978: Add optional gunicorn support to runserver
-+-
 Reporter:  timo |Owner:
 Type:  New feature  |  berkerpeksag
Component:  Core (Management |   Status:  assigned
  commands)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timo):

 I envisioned a more transparent integration. I was thinking that if
 gunicorn is installed, then `runserver` would use that automatically
 (passing data to `--reload` and `--bind` from the current `runserver`
 options). You can always use the full gunicorn integration if you need the
 other options. Do you think that approach would be too limiting from a
 user perspective?

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

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

Re: [Django] #22602: Complete test coverage for makemigrations command

2014-05-19 Thread Django

#22602: Complete test coverage for makemigrations command
-+-
 Reporter:  claudep  |Owner:  whoshuu
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:
Component:  Migrations   |  1.7-beta-2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by whoshuu):

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


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

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

Re: [Django] #10811: Assigning unsaved model to a ForeignKey leads to silent failures

2014-05-19 Thread Django

#10811: Assigning unsaved model to a ForeignKey leads to silent failures
-+-
 Reporter:  Glenn|Owner:
 Type:  Bug  |  anubhav9042
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by altlist):

 One could do this and it does what I expect in Django 1.6

 {{{
 book.author.save()
 book.author = book.author  # refresh id
 book.save()
 }}}

 So I extended the original patch in #8892 (ticket) and wrote a
 save_with_refresh(obj) function.

 {{{
 book.author.save()
 refresh.save_with_refresh(book)
 book.save()
 }}}

 One could modify models.base.save() to accept a "refresh" keyword that
 would do the above.

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

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

Re: [Django] #21978: Add optional gunicorn support to runserver

2014-05-19 Thread Django

#21978: Add optional gunicorn support to runserver
-+-
 Reporter:  timo |Owner:
 Type:  New feature  |  berkerpeksag
Component:  Core (Management |   Status:  assigned
  commands)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by berkerpeksag):

 * cc: berker.peksag@… (added)
 * owner:  nobody => berkerpeksag
 * status:  new => assigned


Comment:

 I have a WIP patch for this ticket. Before open a pull request, I'd like
 to discuss structure of the runserver command.

 Current choices:

 1. Add a new "--gunicorn" option to runserver: ./manage.py runserver
 --gunicorn -c gunicorn_conf.py

 If the -c option is not given, use existing runserver options e.g.:

 ./manage.py runserver --gunicorn [--noreload] [optional port number, or
 ipaddr:port]

 2. Add a new "rungunicorn" command.

 Options:

 * -c conf.py
 * -b --bind
 * -w --workers
 * -l --logfile
 * --debug
 * --reload
 * probably other options from
 http://docs.gunicorn.org/en/latest/settings.html

 Use cases:

 * Use default options: ./manage.py rungunicorn (same as ./manage.py
 runserver)
 * Read config information from a file: ./manage.py rungunicorn -c conf.py
 (this is the configuration file used by Gunicorn)

 Thoughts?

 Thanks!

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

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

[Django] #22661: MakeMigrationTests placed inside MigrateTests class

2014-05-19 Thread Django

#22661: MakeMigrationTests placed inside MigrateTests class
--+
 Reporter:  whoshuu   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Migrations|Version:  1.7-beta-2
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 In `tests/migrations/test_commands.py`, the tests
 
[https://github.com/django/django/blob/master/tests/migrations/test_commands.py#L88-L109
 here] should be moved into the `MakeMigrationsTests` class because they
 test the `makemigration` command, not the `migrate` command.

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

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

Re: [Django] #22660: Dependencies between non-migrated and migrated apps break migration

2014-05-19 Thread Django

#22660: Dependencies between non-migrated and migrated apps break migration
-+-
 Reporter:  yakky|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Migrations   |  Version:
 Severity:  Normal   |  1.7-beta-2
 Keywords:  migrations,  |   Resolution:
  dependencies   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by yakky):

 I added the two tracebacks that occurs in the demo project:
  * `resolving_bases.txt` happens if  the first migrated model in
 `app_main.migrations.0001_initial` is different from `app_main.ClassPl`
 thus resulting in error when `app_sec.ClassB` is scanned for bases
  * `model_load.txt` occurs when `app_main.ClassPl` is the first model
 declaration in `app_main.migrations.0001_initial`

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

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

Re: [Django] #22660: Dependencies between non-migrated and migrated apps break migration

2014-05-19 Thread Django

#22660: Dependencies between non-migrated and migrated apps break migration
-+-
 Reporter:  yakky|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Migrations   |  Version:
 Severity:  Normal   |  1.7-beta-2
 Keywords:  migrations,  |   Resolution:
  dependencies   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by yakky):

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


Comment:

 This case is similar to #22568, but does not involve proxy models.

 Also: squashing migrations or manually arranging classes in the migrations
 either solves the bases resolving issue or the model lookup one.

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

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

[Django] #22660: Dependencies between non-migrated and migrated apps break migration

2014-05-19 Thread Django

#22660: Dependencies between non-migrated and migrated apps break migration
---+--
Reporter: yakky | Owner: nobody
Type: Uncategorized | Status: new
Component: Migrations |Version: 1.7-beta-2
Severity: Normal | Keywords: migrations, dependencies
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
---+--
If models for `app_sec` depends on models from `app_main` (because of
foreign keys or parentship) and models in `app_main` have non trivial
dependencies between them, migrate cannot resolve bases or cannot load
models.
I've setup an example project https://github.com/yakky/migrations_poc to
clarify class relationships.
Transform `app_sec` in a migrated app or using `run_before` attribute on
`app_main` migrations may not be a viable solution: `app_sec` may not be
under developer control or can be unknown at the time of creating
migrations (e.g.: if `app_main` is a general available application and
`app_sec` is a random application reusing models from `app_main`).

Real world case here is django CMS

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

[Django] #22659: parent_link relationships ignored by migrations

2014-05-19 Thread Django

#22659: parent_link relationships ignored by migrations
-+
 Reporter:  tbartelmess  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Migrations   |Version:  1.7-beta-2
 Severity:  Release blocker  |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 The parent_link property on OneToOne relationships is ignored by the
 migration system. This causes the database to end up with two parent
 relationships.

 For example if you have a model like this:

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

 class FooCompany(Company):
 parent_company = models.OneToOneField(Company, primary_key = True,
 parent_link=True)
 }}}

 without migrations the generated tables are correct


 {{{
 BEGIN;
 CREATE TABLE "foo_company" (
 "id" integer NOT NULL PRIMARY KEY AUTOINCREMENT,
 "name" varchar(100) NOT NULL
 )
 ;
 CREATE TABLE "foo_foocompany" (
 "parent_company_id" integer NOT NULL PRIMARY KEY REFERENCES
 "foo_company" ("id")
 )
 ;

 COMMIT;
 }}}

 the migration system however ignores that there is a parent link set and
 generate the tables like this

 {{{
 CREATE TABLE "foo_company" (
 "id" integer NOT NULL PRIMARY KEY AUTOINCREMENT, "name" varchar(100)
 NOT NULL
 );

 CREATE TABLE "foo_foocompany" (
 "company_ptr_id" integer NOT NULL UNIQUE REFERENCES "foo_company"
 ("id"),
 "parent_company_id" integer NOT NULL PRIMARY KEY REFERENCES
 "foo_company" ("id")
 );
 }}}

 I've categorized this as a blocker, because it makes parent_links
 unusable, since the ORM won't know about the additional 'company_ptr_id'
 column causing inserts to fail because of the NOT NULL violation on that
 column

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

Re: [Django] #22653: Need to add database features flag in some of the test cases

2014-05-19 Thread Django

#22653: Need to add database features  flag in some of the test cases
-+-
 Reporter:  rahul.priyadarshi@…  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Testing framework|  Version:
 Severity:  Normal   |  1.7-beta-2
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by rahul.priyadarshi@…):

 Yes, It would be good if always use {{{skipUnlessDBFeature}}}. In new
 attached patch(patch2.diff) I have made this modification.

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

Re: [Django] #21773: development server sometimes takes a long time to restart after source has been changed

2014-05-19 Thread Django

#21773: development server sometimes takes a long time to restart after source 
has
been changed
-+-
 Reporter:  clime|Owner:  mardini
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by mardini):

 * version:  1.6 => master


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

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

Re: [Django] #21773: development server sometimes takes a long time to restart after source has been changed

2014-05-19 Thread Django

#21773: development server sometimes takes a long time to restart after source 
has
been changed
-+-
 Reporter:  clime|Owner:  mardini
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  1.6
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by mardini):

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


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

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

Re: [Django] #22658: Exception in Shell handler with unicode character on 1.7

2014-05-19 Thread Django

#22658: Exception in Shell handler with unicode character on 1.7
-+-
 Reporter:  rbenedum@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:
  Internationalization   |  1.7-beta-1
 Severity:  Normal   |   Resolution:
 Keywords:   |  worksforme
Has patch:  0| Triage Stage:
  Needs tests:  0|  Unreviewed
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by rbenedum@…):

 hi thanks for the reply -
 However, normal python shell is working fine, this appears to be only
 happening in django shell.
 See below that my shell works fine without django.
 Am I missing some django configuration?
 {{{
 [rbenedum@rbpythondev app]$ /usr/local/bin/python2.7
 Python 2.7.6 (default, Mar 31 2014, 18:28:33)
 [GCC 4.4.7 20120313 (Red Hat 4.4.7-4)] on linux2
 Type "help", "copyright", "credits" or "license" for more information.
 >>> 'Le Désert'
 'Le D\xe9sert'
 >>>
 }}}

 Here is a more complete dump of the previous error through django shell


 {{{
 [rbenedum@rbpythondev app]$ /usr/local/bin/python2.7 manage.py shell
 Python 2.7.6 (default, Mar 31 2014, 18:28:33)
 [GCC 4.4.7 20120313 (Red Hat 4.4.7-4)] on linux2
 Type "help", "copyright", "credits" or "license" for more information.
 (InteractiveConsole)
 >>> 'Le Désert'
 Traceback (most recent call last):
   File "manage.py", line 12, in 
 execute_from_command_line(sys.argv)
   File
 "/home/rbenedum/venv/e7e81f830beaf416aee8ababe202ee184aeb71df/lib/python2.7
 /site-packages/django/core/management/__init__.py", line 427, in
 execute_from_command_line
 utility.execute()
   File
 "/home/rbenedum/venv/e7e81f830beaf416aee8ababe202ee184aeb71df/lib/python2.7
 /site-packages/django/core/management/__init__.py", line 419, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File
 "/home/rbenedum/venv/e7e81f830beaf416aee8ababe202ee184aeb71df/lib/python2.7
 /site-packages/django/core/management/base.py", line 288, in run_from_argv
 self.execute(*args, **options.__dict__)
   File
 "/home/rbenedum/venv/e7e81f830beaf416aee8ababe202ee184aeb71df/lib/python2.7
 /site-packages/django/core/management/base.py", line 337, in execute
 output = self.handle(*args, **options)
   File
 "/home/rbenedum/venv/e7e81f830beaf416aee8ababe202ee184aeb71df/lib/python2.7
 /site-packages/django/core/management/base.py", line 532, in handle
 return self.handle_noargs(**options)
   File
 "/home/rbenedum/venv/e7e81f830beaf416aee8ababe202ee184aeb71df/lib/python2.7
 /site-packages/django/core/management/commands/shell.py", line 109, in
 handle_noargs
 code.interact(local=imported_objects)
   File "/usr/local/lib/python2.7/code.py", line 306, in interact
 console.interact(banner)
   File "/usr/local/lib/python2.7/code.py", line 238, in interact
 line = line.decode(encoding)
   File "/usr/local/lib/python2.7/encodings/utf_8.py", line 16, in decode
 return codecs.utf_8_decode(input, errors, True)
 UnicodeDecodeError: 'utf8' codec can't decode byte 0xe9 in position 5:
 invalid continuation byte
 [rbenedum@rbpythondev app]$

 }}}

 This is running on CentOS 6.5 with custom compiled Python 2.7

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

Re: [Django] #22658: Exception in Shell handler with unicode character on 1.7

2014-05-19 Thread Django

#22658: Exception in Shell handler with unicode character on 1.7
-+-
 Reporter:  rbenedum@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:
  Internationalization   |  1.7-beta-1
 Severity:  Normal   |   Resolution:
 Keywords:   |  worksforme
Has patch:  0| Triage Stage:
  Needs tests:  0|  Unreviewed
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by anonymous):

 Hi, I am also having this problem; can you offer a suggestion for how to
 get this fixed? The normal Python shell works fine, only manage.py shell
 breaks.

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

Re: [Django] #22658: Exception in Shell handler with unicode character on 1.7

2014-05-19 Thread Django

#22658: Exception in Shell handler with unicode character on 1.7
-+-
 Reporter:  rbenedum@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:
  Internationalization   |  1.7-beta-1
 Severity:  Normal   |   Resolution:
 Keywords:   |  worksforme
Has patch:  0| Triage Stage:
  Needs tests:  0|  Unreviewed
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 Your shell appears not to be configured correctly — it doesn't pass input
 as utf-8.

 {{{
 % ./manage.py shell
 Python 2.7.5 (default, Aug 25 2013, 00:04:04)
 [GCC 4.2.1 Compatible Apple LLVM 5.0 (clang-500.0.68)] on darwin
 Type "help", "copyright", "credits" or "license" for more information.
 (InteractiveConsole)
 >>> 'Le Désert'
 'Le D\xc3\xa9sert'
 }}}

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

Re: [Django] #21773: development server sometimes takes a long time to restart after source has been changed

2014-05-19 Thread Django

#21773: development server sometimes takes a long time to restart after source 
has
been changed
-+-
 Reporter:  clime|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  1.6
  commands)  |   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 mardini):

 It's probably not a bug in Django, it might be caused by ThreadingMixIn of
 Python's SocketServer module, which Django relies on. I didn't investigate
 it thoroughly though, so I'm not sure.

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

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

[Django] #22658: Exception in Shell handler with unicode character on 1.7

2014-05-19 Thread Django

#22658: Exception in Shell handler with unicode character on 1.7
--+
 Reporter:  rbenedum@…|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Internationalization  |Version:  1.7-beta-1
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 When attempting to execute command 'Le Désert' from django shell and error
 occurs and shell quits.

 Steps to repo from
 python manage.py shell
 '>>>'Le Désert'

 Traceback (most recent call last):
   File "manage.py", line 12, in 
 execute_from_command_line(sys.argv)
   File "[path_removed]/python2.7/site-
 packages/django/core/management/__init__.py", line 427, in
 execute_from_command_line
 utility.execute()
   File "[path_removed]/python2.7/site-
 packages/django/core/management/__init__.py", line 419, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "[path_removed]/python2.7/site-
 packages/django/core/management/base.py", line 288, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "[path_removed]/python2.7/site-
 packages/django/core/management/base.py", line 337, in execute
 output = self.handle(*args, **options)
   File "[path_removed]/python2.7/site-
 packages/django/core/management/base.py", line 532, in handle
 return self.handle_noargs(**options)
   File "[path_removed]/python2.7/site-
 packages/django/core/management/commands/shell.py", line 109, in
 handle_noargs
 code.interact(local=imported_objects)
   File "/usr/local/lib/python2.7/code.py", line 306, in interact
 console.interact(banner)
   File "/usr/local/lib/python2.7/code.py", line 238, in interact
 line = line.decode(encoding)
   File "/usr/local/lib/python2.7/encodings/utf_8.py", line 16, in decode
 return codecs.utf_8_decode(input, errors, True)
 UnicodeDecodeError: 'utf8' codec can't decode byte 0xe9 in position 5:
 invalid continuation byte

 Django Versions tried: 1.7b1, 1.7b4

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

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

Re: [Django] #22656: Adding check for FK that blank=False when null=False

2014-05-19 Thread Django

#22656: Adding check for FK that blank=False when null=False
-+-
 Reporter:  anubhav9042  |Owner:
 Type:  Bug  |  anubhav9042
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:
Has patch:  1|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 Agreed with Tim, that's a use case we want to support.

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

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

Re: [Django] #22638: Form wizard may raise unreasonable exceptions in case of SECRET_KEY change

2014-05-19 Thread Django

#22638: Form wizard may raise unreasonable exceptions in case of SECRET_KEY 
change
-+-
 Reporter:  erikr|Owner:  erikr
 Type:  Bug  |   Status:  closed
Component:  contrib.formtools|  Version:  1.6
 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 Erik Romijn ):

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


Comment:

 In [changeset:"ba5ddf7aed542d25f0fdb25a04d87305de0f3972"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ba5ddf7aed542d25f0fdb25a04d87305de0f3972"
 Fixed #22638 -- Changed CookieWizardView to ignore invalid cookies
 }}}

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

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

[django/django] ba5ddf: Fixed #22638 -- Changed CookieWizardView to ignore...

2014-05-19 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ba5ddf7aed542d25f0fdb25a04d87305de0f3972
  
https://github.com/django/django/commit/ba5ddf7aed542d25f0fdb25a04d87305de0f3972
  Author: Erik Romijn 
  Date:   2014-05-19 (Mon, 19 May 2014)

  Changed paths:
R django/contrib/formtools/exceptions.py
M django/contrib/formtools/tests/wizard/test_cookiestorage.py
M django/contrib/formtools/wizard/storage/cookie.py
M docs/releases/1.8.txt

  Log Message:
  ---
  Fixed #22638 -- Changed CookieWizardView to ignore invalid cookies


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

Re: [Django] #13776: is_valid() with null field value on ModelForms from models with non-nullable ForeignKeys causes ValueError

2014-05-19 Thread Django

#13776: is_valid() with null field value on ModelForms from models with non-
nullable ForeignKeys causes ValueError
-+-
 Reporter:  peterbe  |Owner:
 Type:  Bug  |  anubhav9042
Component:  Forms|   Status:  assigned
 Severity:  Normal   |  Version:  1.2
 Keywords:  ModelForm|   Resolution:
  ForeignKey | 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):

 I think `blank=True` with `null=False` is acceptable. For example, you
 might fill in the value of the `ForeignKey` in the object's `save()`
 method.

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

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

Re: [Django] #22656: Adding check for FK that blank=False when null=False

2014-05-19 Thread Django

#22656: Adding check for FK that blank=False when null=False
-+-
 Reporter:  anubhav9042  |Owner:
 Type:  Bug  |  anubhav9042
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  1|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by timo):

 I'm not sure this is something we want to add as it will break backwards
 compatibility. For example, "Leaving a field blank and filling it in in
 the model's save() method seems to be a pretty common case" -from
 [https://groups.google.com/d/msg/django-users/jqgDy4oo5ZQ/KUSz2gyJ8m0J
 django-users].

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

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

Re: [Django] #22646: MySQL dbshell command should respect the encryption flag

2014-05-19 Thread Django

#22646: MySQL dbshell command should respect the encryption flag
-+-
 Reporter:  zsoldosp |Owner:  zsoldosp
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  1
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by erikr):

 * needs_better_patch:  1 => 0


Comment:

 Apologies, I am completely mistaken. I misread
 `settings_dict['OPTIONS'].get('ssl', {}).get('ca')` as
 `settings_dict['OPTIONS'].get('ca')`. I completely concur now that the
 current format should be supported by both MySQLdb and our DatabaseClient.

 With that out of the way, there's just one issue: I think this deserves a
 short mention in the release notes (for 1.8). Could you add that to the
 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/066.42f0b02ce78dcfbcdfba47e4ba086ba3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22485: makemigrations fails with dependencies to unmigrated apps

2014-05-19 Thread Django

#22485: makemigrations fails with dependencies to unmigrated apps
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  migrations,  | Triage Stage:  Accepted
  unmigrated, makemigrations |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Anton Agestam ):

 I'm still seeing this in 1.7b4.

 Traceback:


 {{{
 (mcr-api)~/.virtualenvs/mcr-api ☕  m migrate clothing 0001
 Operations to perform:
   Target specific migration: 0001_initial, from clothing
 Running migrations:
   Applying clothing.0001_initial...Traceback (most recent call last):
   File "manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/Users/antonagestam/.virtualenvs/mcr-
 api/src/django/django/core/management/__init__.py", line 427, in
 execute_from_command_line
 utility.execute()
   File "/Users/antonagestam/.virtualenvs/mcr-
 api/src/django/django/core/management/__init__.py", line 419, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/Users/antonagestam/.virtualenvs/mcr-
 api/src/django/django/core/management/base.py", line 288, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/Users/antonagestam/.virtualenvs/mcr-
 api/src/django/django/core/management/base.py", line 337, in execute
 output = self.handle(*args, **options)
   File "/Users/antonagestam/.virtualenvs/mcr-
 api/src/django/django/core/management/commands/migrate.py", line 146, in
 handle
 executor.migrate(targets, plan, fake=options.get("fake", False))
   File "/Users/antonagestam/.virtualenvs/mcr-
 api/src/django/django/db/migrations/executor.py", line 62, in migrate
 self.apply_migration(migration, fake=fake)
   File "/Users/antonagestam/.virtualenvs/mcr-
 api/src/django/django/db/migrations/executor.py", line 90, in
 apply_migration
 if self.detect_soft_applied(migration):
   File "/Users/antonagestam/.virtualenvs/mcr-
 api/src/django/django/db/migrations/executor.py", line 134, in
 detect_soft_applied
 apps = project_state.render()
   File "/Users/antonagestam/.virtualenvs/mcr-
 api/src/django/django/db/migrations/state.py", line 86, in render
 model=lookup_model,
 ValueError: Lookup failed for model referenced by field
 admin.LogEntry.user: user.User
 (mcr-api)~/.virtualenvs/mcr-api ☕  python -c "import django; print
 django.get_version()"
 1.7b4
 }}}

 Here's the migration:

 {{{
 # encoding: utf8
 from __future__ import unicode_literals

 from django.db import models, migrations


 class Migration(migrations.Migration):

 dependencies = [
 ]

 operations = [
 migrations.CreateModel(
 name=b'ClothingStart',
 fields=[
 (b'id', models.AutoField(serialize=False,
 primary_key=True)),
 (b'clothing_id', models.IntegerField()),
 (b'created_at', models.DateTimeField()),
 (b'updated_at', models.DateTimeField()),
 ],
 options={
 'db_table': b'clothing_start',
 },
 bases=(models.Model,),
 ),
 migrations.CreateModel(
 name=b'ClothingWebshop',
 fields=[
 (b'id', models.AutoField(serialize=False,
 primary_key=True)),
 (b'clothing_id', models.IntegerField()),
 (b'brand_id', models.IntegerField()),
 (b'url', models.CharField(max_length=255)),
 (b'created_at', models.DateTimeField()),
 (b'updated_at', models.DateTimeField()),
 (b'star_id', models.IntegerField()),
 ],
 options={
 'db_table': b'clothing_webshop',
 },
 bases=(models.Model,),
 ),
 ]
 }}}

-- 
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.c167350beb6d3bbc4bea73b37832e17f%40djangoproject.com.
For more options, visit

Re: [Django] #22656: Adding check for FK that blank=False when null=False

2014-05-19 Thread Django

#22656: Adding check for FK that blank=False when null=False
-+-
 Reporter:  anubhav9042  |Owner:
 Type:  Bug  |  anubhav9042
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  1|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by aaugustin):

 I assume you meant "blank=False when null=False" instead of "null=True
 with blank=True"?

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

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

Re: [Django] #22514: Postgres index generator does not expect db_type to be None

2014-05-19 Thread Django

#22514: Postgres index generator does not expect db_type to be None
-+-
 Reporter:  vzima|Owner:  vzima
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by vzima):

 * owner:  nobody => vzima
 * status:  new => assigned
 * has_patch:  0 => 1
 * stage:  Accepted => Ready for checkin


Comment:

 I've made a PR from the patch.

 PR: https://github.com/django/django/pull/2687

 This patch only patches up the postgres issue. It might be worth to not
 generate indexes on virtual fields in general.

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

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

[Django] #22657: Can't disconnect signal if connected using @reeiver tag

2014-05-19 Thread Django

#22657: Can't disconnect signal if connected using @reeiver tag
-+-
 Reporter:  michalsicker@…   |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Database layer   |Version:  1.6
  (models, ORM)  |   Keywords:  @receiver signal
 Severity:  Normal   |  disconnect
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 I got signal handler function hooked to pre_save signal using @receiver.

 When I tried to disconnect that signal handler temporarily in TestCase, I
 couldn't achieve that. The lookup key generated in dispatcher (lookup_key
 = (_make_id(receiver), _make_id(sender))) in order to match function which
 should be disconnected has other value than it should have so the function
 can't be found in self.receivers and handler doesn't get disconnected.

 That's probably because in self.receivers there is a lookup key generated
 based on "wrapper" function which had been taken to generate that lookup
 when registering handler, not the original one, that's why importing
 original function and passing it to .disconnect() doesn't work.

 When signal connected without using @receiver but using pre_save.connect
 it works as expected.

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

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

Re: [Django] #22654: DecimalField and DECIMAL_SEPARATOR (in admin)

2014-05-19 Thread Django

* status: assigned => new
* type: Uncategorized => Bug
* component: Uncategorized => Forms
* owner: sabinemaennel =>
* stage: Unreviewed => Someday/Maybe

Comment:

This is actually an HTML5 Problem. The admin form for the input of a
number uses the following HTML5 statement:
``.
`step=` in HTML5 can only be defined that way with a `.`as delimiter. Then
the browser will show it on the screen according to local browser
settings. Mine showed it as a dot, but I read on stackoverflow, that some
other users see it with a
comma.[http://stackoverflow.com/questions/6178332/force-decimal-point-
instead-of-comma-in-html5-number-input-client-side].

I think HTML5 will develop further and this behaviour can be corrected via
a Javascript-Library-Use in the meantime. I am not sure what to do with
this bug. I would probably place it outside the influence of Django even
though I can see that it is annoying. Django decided to use HTML5 for its
forms and this is due to the actual state of HTML5. I feel Django is not
responsible to correct HTML5 behaviour, but I would really like to know
the opinion of some more experienced Django contributers on this. So I am
handing the ticket back.

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

Re: [Django] #22650: Regression from f51c1f59 with select_related + prefetch_related

2014-05-19 Thread Django

#22650: Regression from f51c1f59 with select_related + prefetch_related
-+-
 Reporter:  aaugustin|Owner:  loic84
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |  1.7-beta-2
 Severity:  Release blocker  |   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 timo):

 * needs_better_patch:  1 => 0
 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #22653: Need to add database features flag in some of the test cases

2014-05-19 Thread Django

#22653: Need to add database features  flag in some of the test cases
-+-
 Reporter:  rahul.priyadarshi@…  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Testing framework|  Version:
 Severity:  Normal   |  1.7-beta-2
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by manfre):

 Why does the patch use `skipUnlessDBFeature` in some places and
 `skipUnless` in others? Why not always use `skipUnlessDBFeature`?

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

Re: [Django] #22654: DecimalField and DECIMAL_SEPARATOR (in admin)

2014-05-19 Thread Django

#22654: DecimalField and DECIMAL_SEPARATOR (in admin)
---+-
 Reporter:  matija@…   |Owner:  sabinemaennel
 Type:  Uncategorized  |   Status:  assigned
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by sabinemaennel):

 I think this is clearly an error. I tested it with a decimal field. The
 settings `DECIMAL_SEPARATOR = ','` is taken into account when the field is
 shown in the admin, but when validating the field only input with a `.` as
 delimiter is accepted. The field validation needs to be adapted to the
 delimiter given in the settings as well. I tested this with the new 1.7
 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/077.1658c416cc5a2da8e5318afcd4bd37af%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #9373: "This field is required" error even on empty inlines formsets in the admin model page, when hiding a choice field of a custom form.

2014-05-19 Thread Django

#9373: "This field is required" error even on empty inlines formsets in the 
admin
model page, when hiding a choice field of a custom form.
+---
 Reporter:  tyrion.mx@… |Owner:  schacki
 Type:  Bug |   Status:  assigned
Component:  contrib.admin   |  Version:  1.7-alpha-1
 Severity:  Normal  |   Resolution:
 Keywords:  admin, inlines  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+---

Comment (by schacki):

 I have just reviewed the new check framework
 https://docs.djangoproject.com/en/1.7/topics/checks/. I think we should
 add a check in the admin  for this situation. The advantage is that this
 check is only done with DEBUG=False. I.e. log files are not populated in
 production systems.

 I am happy to implement this, if the approach is approved.

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

Re: [Django] #9373: "This field is required" error even on empty inlines formsets in the admin model page, when hiding a choice field of a custom form.

2014-05-19 Thread Django

#9373: "This field is required" error even on empty inlines formsets in the 
admin
model page, when hiding a choice field of a custom form.
+---
 Reporter:  tyrion.mx@… |Owner:  schacki
 Type:  Bug |   Status:  assigned
Component:  contrib.admin   |  Version:  1.7-alpha-1
 Severity:  Normal  |   Resolution:
 Keywords:  admin, inlines  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+---
Changes (by schacki):

 * component:  Forms => contrib.admin


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

Re: [Django] #22656: Adding check for FK that blank=False when null=False

2014-05-19 Thread Django

#22656: Adding check for FK that blank=False when null=False
-+-
 Reporter:  anubhav9042  |Owner:
 Type:  Bug  |  anubhav9042
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  1|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by anubhav9042):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * owner:  nobody => anubhav9042
 * needs_docs:   => 0
 * has_patch:  0 => 1


Comment:

 https://github.com/django/django/pull/2686

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

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

[Django] #22656: Adding check for FK that blank=False when null=False

2014-05-19 Thread Django

#22656: Adding check for FK that blank=False when null=False
--+
 Reporter:  anubhav9042   |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 When ForeignKey is not given null=True with blank=True, there are problems
 at the time of saving.

 Adding a validation check enforcing that blank=False when null=False to
 catch such errors/warnings and displaying appropriate message so that the
 user is fully aware of the situation.

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

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

Re: [Django] #22510: Form fields cannot have names that are present as attributes on the form

2014-05-19 Thread Django

#22510: Form fields cannot have names that are present as attributes on the form
-+--
 Reporter:  gc@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by mjtamlyn):

 Ugh, so much for getting things done at sprints, sorry. I discussed with
 Russ and although part of his argument was "just use del" he decided he
 was happy enough with `None` as a sentinel, and preferred it to
 `ignore_fields`. This is still on my list, but if anyone else gets time
 then feel free.

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

[django/django]

2014-05-19 Thread GitHub

  Branch: refs/heads/stable/1.7.X
  Home:   https://github.com/django/django

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

Re: [Django] #22648: Overridden get_lookup/get_transform not chainable

2014-05-19 Thread Django

#22648: Overridden get_lookup/get_transform not chainable
-+-
 Reporter:  mjtamlyn |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Marc Tamlyn ):

 In [changeset:"c38925a6018a7943936d1fd2b9038ab5de406545"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c38925a6018a7943936d1fd2b9038ab5de406545"
 [1.7.x] Fixed #22648 -- Transform.output_type should respect overridden
 custom_lookup and custom_transform.

 Previously, class lookups from the output_type would be used, but any
 changes to custom_lookup or custom_transform would be ignored.

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

[django/django] c38925: [1.7.x] Fixed #22648 -- Transform.output_type shou...

2014-05-19 Thread GitHub

  Branch: refs/heads/stable/1.7.X
  Home:   https://github.com/django/django
  Commit: c38925a6018a7943936d1fd2b9038ab5de406545
  
https://github.com/django/django/commit/c38925a6018a7943936d1fd2b9038ab5de406545
  Author: Marc Tamlyn 
  Date:   2014-05-19 (Mon, 19 May 2014)

  Changed paths:
M django/db/models/lookups.py
M tests/custom_lookups/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #22648 -- Transform.output_type should respect overridden 
custom_lookup and custom_transform.

Previously, class lookups from the output_type would be used, but any
changes to custom_lookup or custom_transform would be ignored.

Backport of a2dd618 from master


  Commit: 157575c7c8ad4e55b68077c2d10b41d596038e2e
  
https://github.com/django/django/commit/157575c7c8ad4e55b68077c2d10b41d596038e2e
  Author: Marc Tamlyn 
  Date:   2014-05-19 (Mon, 19 May 2014)

  Changed paths:
M tests/custom_lookups/tests.py

  Log Message:
  ---
  [1.7.x] Fix a2dd618 for mysql.

Backport of 3b76502 from master


Compare: https://github.com/django/django/compare/c38925a6018a^...157575c7c8ad

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

[django/django] c38925: [1.7.x] Fixed #22648 -- Transform.output_type shou...

2014-05-19 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: c38925a6018a7943936d1fd2b9038ab5de406545
  
https://github.com/django/django/commit/c38925a6018a7943936d1fd2b9038ab5de406545
  Author: Marc Tamlyn 
  Date:   2014-05-19 (Mon, 19 May 2014)

  Changed paths:
M django/db/models/lookups.py
M tests/custom_lookups/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #22648 -- Transform.output_type should respect overridden 
custom_lookup and custom_transform.

Previously, class lookups from the output_type would be used, but any
changes to custom_lookup or custom_transform would be ignored.

Backport of a2dd618 from master


  Commit: 157575c7c8ad4e55b68077c2d10b41d596038e2e
  
https://github.com/django/django/commit/157575c7c8ad4e55b68077c2d10b41d596038e2e
  Author: Marc Tamlyn 
  Date:   2014-05-19 (Mon, 19 May 2014)

  Changed paths:
M tests/custom_lookups/tests.py

  Log Message:
  ---
  [1.7.x] Fix a2dd618 for mysql.

Backport of 3b76502 from master


Compare: https://github.com/django/django/compare/269291019ec2...157575c7c8ad

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

Re: [Django] #22648: Overridden get_lookup/get_transform not chainable

2014-05-19 Thread Django

#22648: Overridden get_lookup/get_transform not chainable
-+-
 Reporter:  mjtamlyn |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Marc Tamlyn ):

 In [changeset:"c38925a6018a7943936d1fd2b9038ab5de406545"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c38925a6018a7943936d1fd2b9038ab5de406545"
 [1.7.x] Fixed #22648 -- Transform.output_type should respect overridden
 custom_lookup and custom_transform.

 Previously, class lookups from the output_type would be used, but any
 changes to custom_lookup or custom_transform would be ignored.

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

[django/django] ecbabc: Revert "Fixed regression from a2dd618e3b4a7472fab8...

2014-05-19 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ecbabc216dd2fd30ee67ee75dd2a1d8a88e4f574
  
https://github.com/django/django/commit/ecbabc216dd2fd30ee67ee75dd2a1d8a88e4f574
  Author: Marc Tamlyn 
  Date:   2014-05-19 (Mon, 19 May 2014)

  Changed paths:
M django/db/backends/mysql/validation.py

  Log Message:
  ---
  Revert "Fixed regression from a2dd618e3b4a7472fab852da450ca5eef92a922f."

This reverts commit 5a2556afb9b1b3ef6e0622552970c67ac84ecd28.


  Commit: 3b765029f04a43a2ba432936553e33d7c4a4ce29
  
https://github.com/django/django/commit/3b765029f04a43a2ba432936553e33d7c4a4ce29
  Author: Marc Tamlyn 
  Date:   2014-05-19 (Mon, 19 May 2014)

  Changed paths:
M tests/custom_lookups/tests.py

  Log Message:
  ---
  Fix a2dd618 for mysql.


Compare: https://github.com/django/django/compare/2f43229c2f04...3b765029f04a

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

Re: [Django] #22424: Default value for TextField

2014-05-19 Thread Django

#22424: Default value for TextField
-+--
 Reporter:  Nevsky   |Owner:
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by CollinAnderson):

 #22649 SchemaEditor.quote_value is very fragile.

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

Re: [Django] #22655: strictly_above vs strictly_below

2014-05-19 Thread Django

#22655: strictly_above vs strictly_below
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.7-beta-2
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by Tim Graham ):

 In [changeset:"6a2f8985c13e5524d397b48951d6de982544a71a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6a2f8985c13e5524d397b48951d6de982544a71a"
 [1.6.x] Fixed #22655 -- Fixed GeoQuerySet doc about strictly_below

 The paragraph was a copy of strictly_above.

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

[django/django] 269291: [1.7.x] Fixed #22655 -- Fixed GeoQuerySet doc abou...

2014-05-19 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 269291019ec2dd6dd3b9833a37e7b94944ab
  
https://github.com/django/django/commit/269291019ec2dd6dd3b9833a37e7b94944ab
  Author: Moayad Mardini 
  Date:   2014-05-19 (Mon, 19 May 2014)

  Changed paths:
M docs/ref/contrib/gis/geoquerysets.txt

  Log Message:
  ---
  [1.7.x] Fixed #22655 -- Fixed GeoQuerySet doc about strictly_below

The paragraph was a copy of strictly_above.

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

Re: [Django] #22655: strictly_above vs strictly_below

2014-05-19 Thread Django

#22655: strictly_above vs strictly_below
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.7-beta-2
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by Tim Graham ):

 In [changeset:"269291019ec2dd6dd3b9833a37e7b94944ab"]:
 {{{
 #!CommitTicketReference repository=""
 revision="269291019ec2dd6dd3b9833a37e7b94944ab"
 [1.7.x] Fixed #22655 -- Fixed GeoQuerySet doc about strictly_below

 The paragraph was a copy of strictly_above.

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

[django/django] 2f4322: Fixed #22655 -- Fixed GeoQuerySet doc about strict...

2014-05-19 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2f43229c2f044207f193e753baf1bd3fb6164da4
  
https://github.com/django/django/commit/2f43229c2f044207f193e753baf1bd3fb6164da4
  Author: Moayad Mardini 
  Date:   2014-05-19 (Mon, 19 May 2014)

  Changed paths:
M docs/ref/contrib/gis/geoquerysets.txt

  Log Message:
  ---
  Fixed #22655 -- Fixed GeoQuerySet doc about strictly_below

The paragraph was a copy of strictly_above.


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

Re: [Django] #22655: strictly_above vs strictly_below

2014-05-19 Thread Django

#22655: strictly_above vs strictly_below
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.7-beta-2
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"2f43229c2f044207f193e753baf1bd3fb6164da4"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2f43229c2f044207f193e753baf1bd3fb6164da4"
 Fixed #22655 -- Fixed GeoQuerySet doc about strictly_below

 The paragraph was a copy of strictly_above.
 }}}

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

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

[django/django] 6a2f89: [1.6.x] Fixed #22655 -- Fixed GeoQuerySet doc abou...

2014-05-19 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 6a2f8985c13e5524d397b48951d6de982544a71a
  
https://github.com/django/django/commit/6a2f8985c13e5524d397b48951d6de982544a71a
  Author: Moayad Mardini 
  Date:   2014-05-19 (Mon, 19 May 2014)

  Changed paths:
M docs/ref/contrib/gis/geoquerysets.txt

  Log Message:
  ---
  [1.6.x] Fixed #22655 -- Fixed GeoQuerySet doc about strictly_below

The paragraph was a copy of strictly_above.

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

Re: [Django] #22646: MySQL dbshell command should respect the encryption flag

2014-05-19 Thread Django

#22646: MySQL dbshell command should respect the encryption flag
-+-
 Reporter:  zsoldosp |Owner:  zsoldosp
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  1
 Keywords:   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by anonymous):

 So there's a bug (dbshell doesn't work when using MySQL+SSL), there's a
 patch that solves the issue without breaking anything else. What's the
 holdup?

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

[django/django] 1a69d2: Updated translation catalogs

2014-05-19 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1a69d276bdc3009e42812071d06ba8c9dccc2104
  
https://github.com/django/django/commit/1a69d276bdc3009e42812071d06ba8c9dccc2104
  Author: Claude Paroz 
  Date:   2014-05-19 (Mon, 19 May 2014)

  Changed paths:
M django/conf/locale/en/LC_MESSAGES/django.po
M django/contrib/admin/locale/en/LC_MESSAGES/django.po
M django/contrib/admin/locale/en/LC_MESSAGES/djangojs.po
M django/contrib/admindocs/locale/en/LC_MESSAGES/django.po
M django/contrib/auth/locale/en/LC_MESSAGES/django.po
M django/contrib/contenttypes/locale/en/LC_MESSAGES/django.po
M django/contrib/flatpages/locale/en/LC_MESSAGES/django.po
M django/contrib/formtools/locale/en/LC_MESSAGES/django.po
M django/contrib/gis/locale/en/LC_MESSAGES/django.po
M django/contrib/humanize/locale/en/LC_MESSAGES/django.po
M django/contrib/messages/locale/en/LC_MESSAGES/django.po
M django/contrib/redirects/locale/en/LC_MESSAGES/django.po
M django/contrib/sessions/locale/en/LC_MESSAGES/django.po
M django/contrib/sites/locale/en/LC_MESSAGES/django.po

  Log Message:
  ---
  Updated translation catalogs


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

[django/django] 0f8403: [1.7.x] Updated translation catalogs

2014-05-19 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 0f84037e104d63ef341dcfa6a465bef4782fb8fb
  
https://github.com/django/django/commit/0f84037e104d63ef341dcfa6a465bef4782fb8fb
  Author: Claude Paroz 
  Date:   2014-05-19 (Mon, 19 May 2014)

  Changed paths:
M django/conf/locale/en/LC_MESSAGES/django.po
M django/contrib/admin/locale/en/LC_MESSAGES/django.po
M django/contrib/admin/locale/en/LC_MESSAGES/djangojs.po
M django/contrib/admindocs/locale/en/LC_MESSAGES/django.po
M django/contrib/auth/locale/en/LC_MESSAGES/django.po
M django/contrib/comments/locale/en/LC_MESSAGES/django.po
M django/contrib/contenttypes/locale/en/LC_MESSAGES/django.po
M django/contrib/flatpages/locale/en/LC_MESSAGES/django.po
M django/contrib/formtools/locale/en/LC_MESSAGES/django.po
M django/contrib/gis/locale/en/LC_MESSAGES/django.po
M django/contrib/humanize/locale/en/LC_MESSAGES/django.po
M django/contrib/messages/locale/en/LC_MESSAGES/django.po
M django/contrib/redirects/locale/en/LC_MESSAGES/django.po
M django/contrib/sessions/locale/en/LC_MESSAGES/django.po
M django/contrib/sites/locale/en/LC_MESSAGES/django.po

  Log Message:
  ---
  [1.7.x] Updated translation catalogs


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

[django/django] 16c433: [1.7.x] Re-added JS catalog in manage_translations...

2014-05-19 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 16c433967a93cf75e82569d6624ef0d5090bc92b
  
https://github.com/django/django/commit/16c433967a93cf75e82569d6624ef0d5090bc92b
  Author: Claude Paroz 
  Date:   2014-05-19 (Mon, 19 May 2014)

  Changed paths:
M scripts/manage_translations.py

  Log Message:
  ---
  [1.7.x] Re-added JS catalog in manage_translations script

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

[django/django] d20aa7: Re-added JS catalog in manage_translations script

2014-05-19 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d20aa78cbfbefb255ee7f60038c4f090d2deeedc
  
https://github.com/django/django/commit/d20aa78cbfbefb255ee7f60038c4f090d2deeedc
  Author: Claude Paroz 
  Date:   2014-05-19 (Mon, 19 May 2014)

  Changed paths:
M scripts/manage_translations.py

  Log Message:
  ---
  Re-added JS catalog in manage_translations script


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

Re: [Django] #22655: strictly_above vs strictly_below

2014-05-19 Thread Django

#22655: strictly_above vs strictly_below
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.7-beta-2
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by mardini):

 PR: https://github.com/django/django/pull/2684
 Thanks.

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

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

Re: [Django] #22384: Deprecate Django string magic in URLs and the ability to reverse by dotted path

2014-05-19 Thread Django

#22384: Deprecate Django string magic in URLs and the ability to reverse by 
dotted
path
--+
 Reporter:  timo  |Owner:  timo
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (URLs)   |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by FunkyBob):

 Gwildor, the feature pre-dates named url patterns [yes, there wasn't
 always that feature].

 Also, as I'm sure Alex will point out, it can make debugging harder, as
 the error of a wrong import won't always show up, and will appear to come
 from the wrong place when it does fire off.

 This will have no impact on needing to call as_view on CBV.  The as_view
 method is a view function factory -- it is what makes the actual view
 function used to invoke the CBV... you can't do without 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/062.aece6a666ecb3e67feed683617591848%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22654: DecimalField and DECIMAL_SEPARATOR (in admin)

2014-05-19 Thread Django

#22654: DecimalField and DECIMAL_SEPARATOR (in admin)
---+-
 Reporter:  matija@…   |Owner:  sabinemaennel
 Type:  Uncategorized  |   Status:  assigned
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by sabinemaennel):

 * owner:  nobody => sabinemaennel
 * needs_docs:   => 0
 * status:  new => assigned
 * needs_tests:   => 0
 * needs_better_patch:   => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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/077.5c98a5717331250770a7ea0b3a765abd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22652: create_superuser in contrib.auth.management expects "objects" manager in 1.7b4

2014-05-19 Thread Django

#22652: create_superuser in contrib.auth.management expects "objects" manager in
1.7b4
-+--
 Reporter:  alexdlaird   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+--

Comment (by Tim Graham ):

 In [changeset:"1e78d132dad66cae93b94e3c854bcb4fd4b49b6e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1e78d132dad66cae93b94e3c854bcb4fd4b49b6e"
 [1.7.x] Fixed #22652 -- Replaced UserModel.objects with
 UserModel._default_manager.

 Thanks alexdlaird for the report.

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

[django/django] 1e78d1: [1.7.x] Fixed #22652 -- Replaced UserModel.objects...

2014-05-19 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 1e78d132dad66cae93b94e3c854bcb4fd4b49b6e
  
https://github.com/django/django/commit/1e78d132dad66cae93b94e3c854bcb4fd4b49b6e
  Author: Tim Graham 
  Date:   2014-05-19 (Mon, 19 May 2014)

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

  Log Message:
  ---
  [1.7.x] Fixed #22652 -- Replaced UserModel.objects with 
UserModel._default_manager.

Thanks alexdlaird for the report.

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

Re: [Django] #22652: create_superuser in contrib.auth.management expects "objects" manager in 1.7b4

2014-05-19 Thread Django

#22652: create_superuser in contrib.auth.management expects "objects" manager in
1.7b4
-+--
 Reporter:  alexdlaird   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+--
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"b68fac7e88c08cd0bb3dde86388292ddc863eba5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b68fac7e88c08cd0bb3dde86388292ddc863eba5"
 Fixed #22652 -- Replaced UserModel.objects with
 UserModel._default_manager.

 Thanks alexdlaird 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.9b4b5204a7168a9c6ab0534852b67ae6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] b68fac: Fixed #22652 -- Replaced UserModel.objects with Us...

2014-05-19 Thread GitHub

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

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

  Log Message:
  ---
  Fixed #22652 -- Replaced UserModel.objects with UserModel._default_manager.

Thanks alexdlaird for the report.


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

Re: [Django] #5437: Make GDAL optional for GIS test runner

2014-05-19 Thread Django

#5437: Make GDAL optional for GIS test runner
-+
 Reporter:  rcoup|Owner:  vlal
 Type:  Bug  |   Status:  assigned
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  testing  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by vlal):

 Posted on django-dev mailing list [https://groups.google.com/forum/#!topic
 /django-developers/jr6WQ94JRoQ here]

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

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

Re: [Django] #22655: strictly_above vs strictly_below

2014-05-19 Thread Django

#22655: strictly_above vs strictly_below
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.7-beta-2
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by timo):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * easy:  0 => 1
 * needs_docs:   => 0
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


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

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

[Django] #22655: strictly_above vs strictly_below

2014-05-19 Thread Django

#22655: strictly_above vs strictly_below
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.7-beta-2
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Strictly below has the same description as strictly above
 https://docs.djangoproject.com/en/1.7/ref/contrib/gis/geoquerysets
 /#strictly-above

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

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

[django/django] 5abc81: Revert "Fixed #20477: Allowed settings.FORMAT_MODU...

2014-05-19 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5abc811a40dbeee092b9f50055d229e9c24274fa
  
https://github.com/django/django/commit/5abc811a40dbeee092b9f50055d229e9c24274fa
  Author: Tim Graham 
  Date:   2014-05-19 (Mon, 19 May 2014)

  Changed paths:
M django/utils/formats.py
M docs/ref/settings.txt
M docs/releases/1.8.txt
M docs/topics/i18n/formatting.txt
R tests/utils_tests/test_formats.py
R tests/utils_tests/test_module/formats/__init__.py
R tests/utils_tests/test_module/formats/en/__init__.py
R tests/utils_tests/test_module/formats/en/formats.py
R tests/utils_tests/test_module/formats2/__init__.py
R tests/utils_tests/test_module/formats2/en/__init__.py
R tests/utils_tests/test_module/formats2/en/formats.py

  Log Message:
  ---
  Revert "Fixed #20477: Allowed settings.FORMAT_MODULE_PATH to be a list of 
modules."

This reverts commit 950b6de16ac2f8135612f2ed5984c090dd8e4dcf.


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

Re: [Django] #20477: Allow list of modules for FORMAT_MODULE_PATH

2014-05-19 Thread Django

#20477: Allow list of modules for FORMAT_MODULE_PATH
-+-
 Reporter:  mbrochh  |Owner:  mbrochh
 Type:  New feature  |   Status:  closed
Component:   |  Version:  master
  Internationalization   |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  localization,|  Needs documentation:  0
  format files   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"5abc811a40dbeee092b9f50055d229e9c24274fa"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5abc811a40dbeee092b9f50055d229e9c24274fa"
 Revert "Fixed #20477: Allowed settings.FORMAT_MODULE_PATH to be a list of
 modules."

 This reverts commit 950b6de16ac2f8135612f2ed5984c090dd8e4dcf.
 }}}

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

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

[django/django] a69534: [1.7.x] Removed locale dirs for single-message app...

2014-05-19 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: a69534ddd4308d19a06f323037e74205e5192ac9
  
https://github.com/django/django/commit/a69534ddd4308d19a06f323037e74205e5192ac9
  Author: Claude Paroz 
  Date:   2014-05-19 (Mon, 19 May 2014)

  Changed paths:
R django/contrib/sitemaps/locale/en/LC_MESSAGES/django.po
R django/contrib/staticfiles/locale/en/LC_MESSAGES/django.po
R django/contrib/syndication/locale/en/LC_MESSAGES/django.po
R django/contrib/webdesign/locale/en/LC_MESSAGES/django.po

  Log Message:
  ---
  [1.7.x] Removed locale dirs for single-message apps

Considering that these apps only translate their app name, it's not
worth having a whole bunch of po files just for that. The translatable
app name for those apps will be integrated in Django core catalog.
Backport of a1f0c4c697 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/5379f74d48c3c_791ce3fd3c1872d%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] a1f0c4: Removed locale dirs for single-message apps

2014-05-19 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a1f0c4c697e8d848ce43ad8ce346a058f288db19
  
https://github.com/django/django/commit/a1f0c4c697e8d848ce43ad8ce346a058f288db19
  Author: Claude Paroz 
  Date:   2014-05-19 (Mon, 19 May 2014)

  Changed paths:
R django/contrib/sitemaps/locale/en/LC_MESSAGES/django.po
R django/contrib/staticfiles/locale/en/LC_MESSAGES/django.po
R django/contrib/syndication/locale/en/LC_MESSAGES/django.po
R django/contrib/webdesign/locale/en/LC_MESSAGES/django.po

  Log Message:
  ---
  Removed locale dirs for single-message apps

Considering that these apps only translate their app name, it's not
worth having a whole bunch of po files just for that. The translatable
app name for those apps will be integrated in Django core catalog.


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

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

2014-05-19 Thread Django

#22563: Migration of admin.LogEntry.user fails.
-+
 Reporter:  efrinut@…|Owner:  andrewgodwin
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by andrewgodwin):

 This bug is much more limited now to dependency management and so will
 probably be fixed along with #22470 in the next few weeks. We don't treat
 bugs in pre-release versions as "show stoppers", as you're not supposed to
 be doing production code on them yet!

 That said, you can probably fix the bug by manually re-ordering your
 migration operations as described above.

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

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

[django/django] 950b6d: Fixed #20477: Allowed settings.FORMAT_MODULE_PATH ...

2014-05-19 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 950b6de16ac2f8135612f2ed5984c090dd8e4dcf
  
https://github.com/django/django/commit/950b6de16ac2f8135612f2ed5984c090dd8e4dcf
  Author: Martin Brochhaus 
  Date:   2014-05-19 (Mon, 19 May 2014)

  Changed paths:
M django/utils/formats.py
M docs/ref/settings.txt
M docs/releases/1.8.txt
M docs/topics/i18n/formatting.txt
A tests/utils_tests/test_formats.py
A tests/utils_tests/test_module/formats/__init__.py
A tests/utils_tests/test_module/formats/en/__init__.py
A tests/utils_tests/test_module/formats/en/formats.py
A tests/utils_tests/test_module/formats2/__init__.py
A tests/utils_tests/test_module/formats2/en/__init__.py
A tests/utils_tests/test_module/formats2/en/formats.py

  Log Message:
  ---
  Fixed #20477: Allowed settings.FORMAT_MODULE_PATH to be a list of modules.

Previously the FORMAT_MODULE_PATH setting only accepted one string (dotted
module path).

This is useful when using several reusable third party apps that define new
formats. We can now use them all and we can even override some of the formats
by providing a project-wide format module.


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

Re: [Django] #20477: Allow list of modules for FORMAT_MODULE_PATH

2014-05-19 Thread Django

#20477: Allow list of modules for FORMAT_MODULE_PATH
-+-
 Reporter:  mbrochh  |Owner:  mbrochh
 Type:  New feature  |   Status:  closed
Component:   |  Version:  master
  Internationalization   |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  localization,|  Needs documentation:  0
  format files   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"950b6de16ac2f8135612f2ed5984c090dd8e4dcf"]:
 {{{
 #!CommitTicketReference repository=""
 revision="950b6de16ac2f8135612f2ed5984c090dd8e4dcf"
 Fixed #20477: Allowed settings.FORMAT_MODULE_PATH to be a list of modules.

 Previously the FORMAT_MODULE_PATH setting only accepted one string (dotted
 module path).

 This is useful when using several reusable third party apps that define
 new
 formats. We can now use them all and we can even override some of the
 formats
 by providing a project-wide format module.
 }}}

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

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

Re: [Django] #22653: Need to add database features flag in some of the test cases

2014-05-19 Thread Django

#22653: Need to add database features  flag in some of the test cases
-+-
 Reporter:  rahul.priyadarshi@…  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Testing framework|  Version:
 Severity:  Normal   |  1.7-beta-2
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #22368: Document how to use SERVICE_NAME with Oracle

2014-05-19 Thread Django

#22368: Document how to use SERVICE_NAME with Oracle
-+-
 Reporter:  michael.cherkasov@…  |Owner:  mardini
 Type:  New feature  |   Status:  closed
Component:  Documentation|  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  oracle, database,| Triage Stage:  Accepted
  db config  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"4dd37a3a6eb744a9901eb53454a86bf304a71426"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4dd37a3a6eb744a9901eb53454a86bf304a71426"
 [1.7.x] Fixed #22368 -- clarified connecting to Oracle DB using service
 name

 Used the official terminology listed in
 http://docs.oracle.com/cd/B19306_01/network.102/b14212/glossary.htm#i997309

 Thanks michael.cherkasov for the report.

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

[django/django] 4dd37a: [1.7.x] Fixed #22368 -- clarified connecting to Or...

2014-05-19 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 4dd37a3a6eb744a9901eb53454a86bf304a71426
  
https://github.com/django/django/commit/4dd37a3a6eb744a9901eb53454a86bf304a71426
  Author: Moayad Mardini 
  Date:   2014-05-19 (Mon, 19 May 2014)

  Changed paths:
M docs/ref/databases.txt

  Log Message:
  ---
  [1.7.x] Fixed #22368 -- clarified connecting to Oracle DB using service name

Used the official terminology listed in
http://docs.oracle.com/cd/B19306_01/network.102/b14212/glossary.htm#i997309

Thanks michael.cherkasov for the report.

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

Re: [Django] #22368: Document how to use SERVICE_NAME with Oracle

2014-05-19 Thread Django

#22368: Document how to use SERVICE_NAME with Oracle
-+-
 Reporter:  michael.cherkasov@…  |Owner:  mardini
 Type:  New feature  |   Status:  closed
Component:  Documentation|  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  oracle, database,| Triage Stage:  Accepted
  db config  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"26221445df5855d189b2dc4dd76ff0a9f0bd77d0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="26221445df5855d189b2dc4dd76ff0a9f0bd77d0"
 [1.6.x] Fixed #22368 -- clarified connecting to Oracle DB using service
 name

 Used the official terminology listed in
 http://docs.oracle.com/cd/B19306_01/network.102/b14212/glossary.htm#i997309

 Thanks michael.cherkasov for the report.

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

Re: [Django] #22368: Document how to use SERVICE_NAME with Oracle

2014-05-19 Thread Django

#22368: Document how to use SERVICE_NAME with Oracle
-+-
 Reporter:  michael.cherkasov@…  |Owner:  mardini
 Type:  New feature  |   Status:  closed
Component:  Documentation|  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  oracle, database,| Triage Stage:  Accepted
  db config  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"bfac6bef833d2520853c88188560b81bc7e3988d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="bfac6bef833d2520853c88188560b81bc7e3988d"
 Fixed #22368 -- clarified connecting to Oracle DB using service name

 Used the official terminology listed in
 http://docs.oracle.com/cd/B19306_01/network.102/b14212/glossary.htm#i997309

 Thanks michael.cherkasov 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/085.8a7ef74ccf34a690070b906fdf23f5ea%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 262214: [1.6.x] Fixed #22368 -- clarified connecting to Or...

2014-05-19 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 26221445df5855d189b2dc4dd76ff0a9f0bd77d0
  
https://github.com/django/django/commit/26221445df5855d189b2dc4dd76ff0a9f0bd77d0
  Author: Moayad Mardini 
  Date:   2014-05-19 (Mon, 19 May 2014)

  Changed paths:
M docs/ref/databases.txt

  Log Message:
  ---
  [1.6.x] Fixed #22368 -- clarified connecting to Oracle DB using service name

Used the official terminology listed in
http://docs.oracle.com/cd/B19306_01/network.102/b14212/glossary.htm#i997309

Thanks michael.cherkasov for the report.

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

[django/django] bfac6b: Fixed #22368 -- clarified connecting to Oracle DB ...

2014-05-19 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: bfac6bef833d2520853c88188560b81bc7e3988d
  
https://github.com/django/django/commit/bfac6bef833d2520853c88188560b81bc7e3988d
  Author: Moayad Mardini 
  Date:   2014-05-19 (Mon, 19 May 2014)

  Changed paths:
M docs/ref/databases.txt

  Log Message:
  ---
  Fixed #22368 -- clarified connecting to Oracle DB using service name

Used the official terminology listed in
http://docs.oracle.com/cd/B19306_01/network.102/b14212/glossary.htm#i997309

Thanks michael.cherkasov for the report.


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

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

2014-05-19 Thread Django

#22563: Migration of admin.LogEntry.user fails.
-+
 Reporter:  efrinut@…|Owner:  andrewgodwin
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by npolet):

 I can't run tests as I get the "ValueError: Lookup failed for model
 referenced by field admin.LogEntry.user" error when the test system is
 trying to create the test database. Has there been any progress on this
 bug? It's pretty much a show stopper at the moment.

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

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

[Django] #22654: DecimalField and DECIMAL_SEPARATOR (in admin)

2014-05-19 Thread Django

#22654: DecimalField and DECIMAL_SEPARATOR (in admin)
---+
Reporter: matija@… | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized |Version: 1.6
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
---+
DecimalField with following settings:

LANGUAGE_CODE = 'hr-hr'
TIME_ZONE = 'CET'
USE_I18N = True
USE_L10N = False
USE_TZ = False
DATE_FORMAT = 'd.m.Y.'
DATE_INPUT_FORMATS = ('%d.%m.%Y.', '%d.%m.%Y', '%Y-%m-%d')
DECIMAL_SEPARATOR = ','

Correctly shows Decimal field in admin, but raises validation error.

As most of our customers do not set their preferences to Croatian, and we
need to show Croatian locale for all users. So with settings above, things
sdhould work.

Tried in 1.6 and 1.7.

In order to reproduce, all you need is a single model with a DecimalField,
registered in Admin. And the above settings. Input any non-integer value
and press save_and_continue_editing. If you encounter no errors, press it
again. Now it will show an error.

I added a new ticked because related ones were closed years ago.

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

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

Re: [Django] #10811: Assigning unsaved model to a ForeignKey leads to silent failures

2014-05-19 Thread Django

#10811: Assigning unsaved model to a ForeignKey leads to silent failures
-+-
 Reporter:  Glenn|Owner:
 Type:  Bug  |  anubhav9042
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timo):

 Looks like #8892 is another duplicate.

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

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

Re: [Django] #8892: ForeignKey relation not saved as expected

2014-05-19 Thread Django

#8892: ForeignKey relation not saved as expected
-+-
 Reporter:  julien   |Owner:
 Type:  Bug  |  blacklwhite
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  Version:  1.0
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 Looks like a duplicate of #10811.

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

Re: [Django] #14807: django.utils.formats localize_input inserts thousands_separator into boolean values

2014-05-19 Thread Django

#14807: django.utils.formats localize_input inserts thousands_separator into
boolean values
-+-
 Reporter:  vanschelven  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:   |  Version:  1.2
  Internationalization   |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 I'll be better to open a new ticket rather than reopening one that's three
 years old where the original fix has already been released, thanks.

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

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

[Django] #22653: Need to add database features flag in some of the test cases

2014-05-19 Thread Django

#22653: Need to add database features  flag in some of the test cases
-+
 Reporter:  rahul.priyadarshi@…  |  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  Testing framework|Version:  1.7-beta-2
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  1
Easy pickings:  0|  UI/UX:  0
-+
 Some of the Database backend doesn't allow to defer constraints check like
 DB2 which doesn't allow to defer constraint check within a transaction
 also

 Following test cases requires to check can_defer_constraint_checks
 i) test cases under admin_views.tests.AdminViewDeletedObjectsTest test
 class
 ii) test cases under serializers_regress.tests.SerializerTests test class

 Following test cases requires supports_forward_references flag check
 i) serializers.SerializersTransactionTestBase.test_forward_refs
 ii)
 fixtures_regress.TestFixtures.test_loaddata_works_when_fixture_has_forward_refs
 iii)
 fixtures_regress.TestFixtures.test_loaddata_forward_refs_split_fixtures

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

Re: [Django] #10811: Assigning unsaved model to a ForeignKey leads to silent failures

2014-05-19 Thread Django

Comment (by anubhav9042):

Well I went through the entire problem today thoroughly.

The problem is that when in the `inline` test(which causes errors), we are
trying to create an object on the fly and then since it has no `id` so it
cannot be used. Following Aymeric's comments above line by line its true
that form gets fields: `['et', 'place']` out of which `et` which is FK
creates problem in form validation step in `_post_clean` when
`construct_instance` is called.
We need a saved object of `ExtraTerrestrial` class for its `id` to be
saved in `Sighting`.

As far as I think, there are other tests in same test file with models
using the FK, why not try to implement the error causing test case in a
similar way/ or create an object before and send it(dunno if the second
part is possible)
Or
Is it possible to write a check in `_post_clean` and prevent calling of
`construct_instance`?

Need some guidance here.

A similarity between failing tests: Both are dealing with inherited
models. Although I don't think that might be a problem here but still I
thought it better to post.

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

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

Re: [Django] #21231: Limiting the number of variables and files that a POST request can contain

2014-05-19 Thread Django

#21231: Limiting the number of variables and files that a POST request can 
contain
---+
 Reporter:  epandurski@…   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by anonymous):

 This is a serious problem, and there seems to be a patch available. Can
 someone from the dev team look at it please?

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

Re: [Django] #8892: ForeignKey relation not saved as expected

2014-05-19 Thread Django

Comment (by akaariai):

What we could possibly do is check that b.a.id == b.a_id. If not, then
throw an error. This would break some code for sure, but on the other hand
it would be a nice protection. Instead of saving corrupted data the ORM
layer forces you to write code where both b.a.id and b.a_id agree on the
value.

There are a couple of other options, too, like when a.save() is called,
then b.a_id is set (requires that a knows it is assigned to b), or on
b.save() use the value of b.a.id instead of b.a_id (this will break code
that relies on saving b.a_id).

Raising an exception whenever b.a_id doesn't agree on b.a.id's value is
worth considering. I believe exception is a lot better than the
possibility for bugs that lead to silent data corruption.

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

Re: [Django] #8892: ForeignKey relation not saved as expected

2014-05-19 Thread Django

#8892: ForeignKey relation not saved as expected
-+-
 Reporter:  julien   |Owner:
 Type:  Bug  |  blacklwhite
Component:  Database layer   |   Status:  new
  (models, ORM)  |  Version:  1.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 The original example isn't supported because, deep inside the ORM, `b.a =
 a` is implemented as `b.a_id = a.id`.

 Changing this design would require rewriting most of the related fields
 code, which isn't for the faint of heart ;-)

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

Re: [Django] #14807: django.utils.formats localize_input inserts thousands_separator into boolean values

2014-05-19 Thread Django

#14807: django.utils.formats localize_input inserts thousands_separator into
boolean values
-+-
 Reporter:  vanschelven  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:   |  Version:  1.2
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by klaas@…):

 * status:  closed => new
 * severity:   => Normal
 * type:   => Uncategorized
 * easy:   => 0
 * ui_ux:   => 0
 * resolution:  fixed =>


Comment:

 When fixing this, input_localize was missed. My proposed solution (which
 is unfortunately not formatted as a pull request, nor does it have tests)
 is here:

 
https://github.com/vanschelven/django/commit/f0e39c83ec9174b8e5241caa6ba59b8e2e6deb66

 Also copying my notes from that solution to justify reopening the issue:

 6c53a81 only fixed localize(), but not localize_input()
 It appears to me that this was simply an oversight at the time.

 It seems that a new call-order for fields somewhere between Django 1.4
 and Django 1.6 triggers triggers this bug again, but this time on the
 inputs
 and only when rendering fields as_hidden.

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

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

Re: [Django] #8892: ForeignKey relation not saved as expected

2014-05-19 Thread Django

#8892: ForeignKey relation not saved as expected
-+-
 Reporter:  julien   |Owner:
 Type:  Bug  |  blacklwhite
Component:  Database layer   |   Status:  new
  (models, ORM)  |  Version:  1.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by altlist):

 I am a little confused why the original example isn't supported.

 {{{
 >>> a = ModelA(name='foo')
 >>> b = ModelB(name='bar')
 >>> b.a = a # Set relation *before* saving related object
 >>> a.save() # Save related object
 >>> a.pk
 123
 >>> b.a.pk
 123
 >>> b.save()
 >>> b = ModelB.objects.get(name='bar')
 >>> b.a
 
 }}}

 While I agree the docs suggests auto-increment keys can be determined
 upfront, the django model above shows a.pk is already known BEFORE I save
 b.  Hence I don't see why Django can't save object b correctly.

 Instead, I have to use the below suggested hack in the StackOverlow
 question.  Yet this seems cumbersome and unnecessary.

 {{{
 >>> b.a = b.a
 >>> b.save()
 }}}

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

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

Re: [Django] #22646: MySQL dbshell command should respect the encryption flag

2014-05-19 Thread Django

#22646: MySQL dbshell command should respect the encryption flag
-+-
 Reporter:  zsoldosp |Owner:  zsoldosp
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  1
 Keywords:   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by syphar):

 Perhaps I'm missing the point.

 But the OP stated his options are (formatted):
 {{{
 {
 'OPTIONS': {
 'ssl': {
 'ca': ''
 }
 }
  }
 }}}

 which is exactly the same as he uses for the {{{--ssl-ca}}} command line
 argument:
 {{{
 cert = settings_dict['OPTIONS'].get('ssl', {}).get('ca')
 }}}

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

Re: [Django] #22368: Document how to use SERVICE_NAME with Oracle

2014-05-19 Thread Django

#22368: Document how to use SERVICE_NAME with Oracle
-+-
 Reporter:  michael.cherkasov@…  |Owner:  mardini
 Type:  New feature  |   Status:  assigned
Component:  Documentation|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  oracle, database,| Triage Stage:  Accepted
  db config  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by mardini):

 PR: https://github.com/django/django/pull/2683
 Thanks.

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

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

[django/django] db2aac: [1.7.x] Updated Django makemessages process

2014-05-19 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: db2aacff9906c0f9c7c004173787ef8c292451f1
  
https://github.com/django/django/commit/db2aacff9906c0f9c7c004173787ef8c292451f1
  Author: Claude Paroz 
  Date:   2014-05-19 (Mon, 19 May 2014)

  Changed paths:
M django/core/management/commands/makemessages.py
M scripts/manage_translations.py

  Log Message:
  ---
  [1.7.x] Updated Django makemessages process

makemessages should now automatically distribute translatable
strings in the proper locale files, for Django too
(see 50a8ab7cd1e6).
Backport of 7999ed9b69 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/5379b34f24b90_198d7d9d44635b8%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

1 2 >

1 - 100 of 106 matches

Mail list logo