[Django] #24851: Reverse one-to-one relations break the admin.

[Django]

#24851: Reverse one-to-one relations break the admin.
---+
 Reporter:  jerivas|  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Including reverse one-to-one relations in `list_display` or `fields` in a
 `ModelAdmin` breaks the "change_list" and "change" admin views.

 The "change" view raises a `FieldError` saying the reverse one-to-one
 field is unknown. The "change_list" raises `AttributeError`: 'OneToOneRel'
 object has no attribute 'rel'.

 I've setup a small test app here: https://gitlab.com/jerivas/one-to-one-
 bug.

 To reproduce:
 - Clone the repo
 - Install deps from requirements.txt
 - Start the development server
 - Visit the admin. User/pass: proj/proj
 - Both the Car and Engine admins should work
 - Uncomment lines 7 & 8 from `cars/admin.py`
 - Both the "change_list" and "change" views  of the Car admin are now
 broken. The Engine admin continues to work as expected.

 This worked normally in 1.6, and I just found it while updating a project
 from 1.6 to 1.8. I don't know if the bug was introduced in 1.7 or 1.8.

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

[Django] #24850: Squashed migration not recognized as an initial migration

[Django]

#24850: Squashed migration not recognized as an initial migration
---+
 Reporter:  riklaunim  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Migrations |Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I have constant problems with squash migrations not being recognised as
 initial migrations.

 - when '''replaces''' and old migrations exist it's ok
 - when '''replaces''' exist and old migrations do not it's ok if there are
 not dependant migrations in other apps (or NodeNotFoundError will be
 thrown)
 - when both do not exist it tries to execute the migration which fails on
 an existing database as tables exist

 Running migrations with --fake is a local solution, but definitely not
 optimal for deployment where other migrations may show up and so on. In
 only one simple example I managed to get migration auto-faked, recognised
 as initial. In every other it tries to apply it.

 I would say that a squash should have an explicit flag that would affect
 data in django_migrations. Some sort of get_or_create with an entry for
 that squashed migration so that no matter where the code will go - the
 table will be updated without the need of any forced --fake operations.

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

[Django] #24849: Broken squashmigration when model related to another one gets deleted

[Django]

#24849: Broken squashmigration when model related to another one gets deleted
+
 Reporter:  riklaunim   |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  1.8
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 I've got a simple example of an broken squashmigration I had in two apps.
 The problem is that if a model gets deleted, that has relation to other
 model then the squash will crash as something will want to do some
 operation on the non-existing model (relation presence is essential,
 tested on postgres):

 Initial:
 {{{
 class Category(models.Model):
 title = models.CharField(max_length=100)


 class News(models.Model):
 title = models.CharField(max_length=100)
 category = models.ForeignKey(Category)
 }}}

 Second migration:

 {{{
 class Category(models.Model):
 title = models.CharField(max_length=100)

 class NewCategory(models.Model):
 title = models.CharField(max_length=100)


 class News(models.Model):
 title = models.CharField(max_length=100)
 category = models.ForeignKey(NewCategory, blank=True, null=True)
 new_category = models.ForeignKey(NewCategory, blank=True, null=True)
 }}}

 Third:

 {{{
 class NewCategory(models.Model):
 title = models.CharField(max_length=100)


 class News(models.Model):
 title = models.CharField(max_length=100)
 new_category = models.ForeignKey(NewCategory, blank=True, null=True)
 }}}

 Squash looks like so:
 {{{
 operations = [
 migrations.CreateModel(
 name='Category',
 fields=[
 ('id', models.AutoField(auto_created=True,
 primary_key=True, serialize=False, verbose_name='ID')),
 ('title', models.CharField(max_length=100)),
 ],
 ),
 migrations.CreateModel(
 name='News',
 fields=[
 ('id', models.AutoField(auto_created=True,
 primary_key=True, serialize=False, verbose_name='ID')),
 ('title', models.CharField(max_length=100)),
 ('category', models.ForeignKey(blank=True,
 to='relateddeleted.Category', null=True)),
 ],
 ),
 migrations.CreateModel(
 name='NewCategory',
 fields=[
 ('id', models.AutoField(auto_created=True,
 primary_key=True, serialize=False, verbose_name='ID')),
 ('title', models.CharField(max_length=100)),
 ],
 ),
 migrations.AddField(
 model_name='news',
 name='new_category',
 field=models.ForeignKey(blank=True,
 to='relateddeleted.NewCategory', null=True),
 ),
 migrations.RemoveField(
 model_name='news',
 name='category',
 ),
 migrations.DeleteModel(
 name='Category',
 ),
 ]
 }}}

 And on a clean database it throws:
 {{{
   Applying
 relateddeleted.0001_squashed_0003_auto_20150524_2020...Traceback (most
 recent call last):
   File "/home/piotr/devel/envs/migracje/lib/python3.4/site-
 packages/django/db/backends/utils.py", line 64, in execute
 return self.cursor.execute(sql, params)
 psycopg2.ProgrammingError: relation "relateddeleted_category" does not
 exist


 The above exception was the direct cause of the following exception:

 Traceback (most recent call last):
   File "manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/home/piotr/devel/envs/migracje/lib/python3.4/site-
 packages/django/core/management/__init__.py", line 338, in
 execute_from_command_line
 utility.execute()
   File "/home/piotr/devel/envs/migracje/lib/python3.4/site-
 packages/django/core/management/__init__.py", line 330, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/piotr/devel/envs/migracje/lib/python3.4/site-
 packages/django/core/management/commands/test.py", line 30, in
 run_from_argv
 super(Command, self).run_from_argv(argv)
   File "/home/piotr/devel/envs/migracje/lib/python3.4/site-
 packages/django/core/management/base.py", line 390, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/home/piotr/devel/envs/migracje/lib/python3.4/site-
 packages/django/core/management/commands/test.py", line 74, in execute
 super(Command, self).execute(*args, **options)
   File "/home/piotr/devel/envs/migracje/lib/python3.4/site-
 packages/django/core/management/base.py", line 441, in execute
 output = self.handle(*args, **options)
   File "/home/piotr/devel/envs/migracje/lib/python3.4/site-
 packages/django/core/management/commands/test.py", line 90, in handle
 failures = test_runner.run_tests(test_labels)
   File "/home/piotr/devel/envs/migracje/lib/python3.4/site-
 packages/django/test/runner.py", line 210, in 

Re: [Django] #24848: makemigrations fails with 'ValueError: Dependency on unknown app' when migrations module exists without __init__.py

[Django]

#24848: makemigrations fails with 'ValueError: Dependency on unknown app' when
migrations module exists without __init__.py
+
 Reporter:  Ernest0x|Owner:  knbk
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  1.8
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by knbk):

 * has_patch:  0 => 1


Comment:

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

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

Re: [Django] #24848: makemigrations fails with 'ValueError: Dependency on unknown app' when migrations module exists without __init__.py (was: makemigrations fails with 'ValueError: Dependency on unkn

[Django]

#24848: makemigrations fails with 'ValueError: Dependency on unknown app' when
migrations module exists without __init__.py
+
 Reporter:  Ernest0x|Owner:  knbk
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  1.8
 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 knbk):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * owner:  nobody => knbk
 * needs_docs:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 The problem is that, if you hit
 https://github.com/django/django/blob/master/django/db/migrations/loader.py#L81
 due to a missing `__init__.py` file, the app is neither in `migrated_apps`
 nor `unmigrated_apps`. The same will happen if the migrations module is a
 file, and not a folder.

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

Re: [Django] #24788: Allow Forms to set a default prefix attribute

[Django]

#24788: Allow Forms to set a default prefix attribute
-+
 Reporter:  kezabelle|Owner:  pwmarcz
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by pwmarcz):

 * has_patch:  0 => 1


Comment:

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

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

Re: [Django] #24788: Allow Forms to set a default prefix attribute

[Django]

#24788: Allow Forms to set a default prefix attribute
-+
 Reporter:  kezabelle|Owner:  pwmarcz
 Type:  New feature  |   Status:  assigned
Component:  Forms|  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 pwmarcz):

 * owner:  nobody => pwmarcz
 * 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/067.ffa9f8f90b839621886790e282eb3a35%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24835: exists() incorrect after annotation with Count()

[Django]

#24835: exists() incorrect after annotation with Count()
-+-
 Reporter:  pteromys |Owner:  pwmarcz
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 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
-+-
Changes (by pwmarcz):

 * has_patch:  0 => 1


Comment:

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

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

Re: [Django] #24835: exists() incorrect after annotation with Count()

[Django]

#24835: exists() incorrect after annotation with Count()
-+-
 Reporter:  pteromys |Owner:  pwmarcz
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 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
-+-
Changes (by pwmarcz):

 * owner:  nobody => pwmarcz
 * 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/066.7c71da41a59354f2b66d008603ee748e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24846: MySQL Migration SchemaEditor default code is ignorant of other blob/text data types

[Django]

#24846: MySQL Migration SchemaEditor default code is ignorant of other blob/text
data types
--+--
 Reporter:  adamchainz|Owner:  adamchainz
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:  mysql migrations  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by claudep):

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


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

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

Re: [Django] #24845: serve with apache in virualenv documentation

[Django]

#24845: serve with apache in virualenv documentation
---+--
 Reporter:  Alcolo47   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.7
 Severity:  Normal |   Resolution:  invalid
 Keywords:  apache virtualenv  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by claudep):

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


Comment:

 Sorry, but this ticket tracker is not meant to answer support questions:
 https://code.djangoproject.com/wiki/TicketClosingReasons/UseSupportChannels

 Your question is outside the scope of Django. You should better refer to
 the mod_wsgi documentation.
 https://code.google.com/p/modwsgi/wiki/InstallationInstructions

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

Re: [Django] #24848: makemigrations fails with 'ValueError: Dependency on unknown app' when using custom user model

[Django]

#24848: makemigrations fails with 'ValueError: Dependency on unknown app' when
using custom user model
+
 Reporter:  Ernest0x|  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  1.8
 Severity:  Normal  | Resolution:
 Keywords:  |   Triage Stage:  Unreviewed
Has patch:  0   |  Easy pickings:  0
UI/UX:  0   |
+
Changes (by Ernest0x):

 * Attachment "myproject.tar.gz" added.


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

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

[Django] #24848: makemigrations fails with 'ValueError: Dependency on unknown app' when using custom user model

[Django]

#24848: makemigrations fails with 'ValueError: Dependency on unknown app' when
using custom user model
+
 Reporter:  Ernest0x|  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  1.8
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 Django version 1.8.2

 traceback:
 {{{
 Traceback (most recent call last):
   File "manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/path/to/python/env/lib/python3.4/site-
 packages/django/core/management/__init__.py", line 338, in
 execute_from_command_line
 utility.execute()
   File "/path/to/python/env/lib/python3.4/site-
 packages/django/core/management/__init__.py", line 330, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/path/to/python/env/lib/python3.4/site-
 packages/django/core/management/base.py", line 390, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/path/to/python/env/lib/python3.4/site-
 packages/django/core/management/base.py", line 441, in execute
 output = self.handle(*args, **options)
   File "/path/to/python/env/lib/python3.4/site-
 packages/django/core/management/commands/makemigrations.py", line 63, in
 handle
 loader = MigrationLoader(None, ignore_no_migrations=True)
   File "/path/to/python/env/lib/python3.4/site-
 packages/django/db/migrations/loader.py", line 47, in __init__
 self.build_graph()
   File "/path/to/python/env/lib/python3.4/site-
 packages/django/db/migrations/loader.py", line 287, in build_graph
 parent = self.check_key(parent, key[0])
   File "/path/to/python/env/lib/python3.4/site-
 packages/django/db/migrations/loader.py", line 165, in check_key
 raise ValueError("Dependency on unknown app: %s" % key[0])
 ValueError: Dependency on unknown app: users
 }}}

 Example project is included as an attachment.

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

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

Re: [Django] #24844: HStore Form Field falsely report has_changed

[Django]

#24844: HStore Form Field falsely report has_changed
--+
 Reporter:  RamezIssac|Owner:  andreagrandi
 Type:  Bug   |   Status:  closed
Component:  contrib.postgres  |  Version:  1.8
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  1
--+
Changes (by Florian Apolloner ):

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


Comment:

 In [changeset:"43b2d88a5b9cfb151ccf7ac861f2750e70c0e2c4" 43b2d88]:
 {{{
 #!CommitTicketReference repository=""
 revision="43b2d88a5b9cfb151ccf7ac861f2750e70c0e2c4"
 Fixed #24844 -- Corrected has_changed implementation for HStoreField.
 }}}

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

Re: [Django] #24844: HStore Form Field falsely report has_changed

[Django]

#24844: HStore Form Field falsely report has_changed
--+
 Reporter:  RamezIssac|Owner:  andreagrandi
 Type:  Bug   |   Status:  assigned
Component:  contrib.postgres  |  Version:  1.8
 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:  1
--+
Changes (by andreagrandi):

 * has_patch:  0 => 1


Comment:

 I try to fix the bug with this PR
 https://github.com/django/django/pull/4705

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

Re: [Django] #24844: HStore Form Field falsely report has_changed

[Django]

#24844: HStore Form Field falsely report has_changed
--+
 Reporter:  RamezIssac|Owner:  andreagrandi
 Type:  Bug   |   Status:  assigned
Component:  contrib.postgres  |  Version:  1.8
 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:  1
--+
Changes (by andreagrandi):

 * status:  new => assigned
 * owner:   => andreagrandi


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

Re: [Django] #16774: Backtracking URL resolver

[Django]

#16774: Backtracking URL resolver
-+
 Reporter:  nbstrite |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by knbk):

 * component:  HTTP handling => Core (URLs)


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

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

Re: [Django] #24847: Items set on a RequestContext after creation get lost

[Django]

#24847: Items set on a RequestContext after creation get lost
-+
 Reporter:  pmdhazy  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.8
 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
-+
Changes (by bmispelon):

 * Attachment "repro-24847.patch" added.

 Reproduction testcase

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

Re: [Django] #24847: Items set on a RequestContext after creation get lost

[Django]

#24847: Items set on a RequestContext after creation get lost
-+
 Reporter:  pmdhazy  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.8
 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
-+
Changes (by bmispelon):

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


Comment:

 Hi,

 I can confirm that this issue exists and it wasn't present in 1.7 so I'm
 bumping the severity.
 With the help of the attached test case, I bisected the issue to commit
 37505b6397058bcc3460f23d48a7de9641cd6ef0.

 Thanks.

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

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

[Django] #24847: Items set on a RequestContext after creation get lost

[Django]

#24847: Items set on a RequestContext after creation get lost
-+
 Reporter:  pmdhazy  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Template system  |Version:  1.8
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 You cannot use `c['foo']  = newvalue` on a RequestContext after creation
 as it gets stomped on by the different context processors logic in 1.8
 {{{
 >>> from django.template import Template, RequestContext
 >>> from django.http import HttpRequest
 >>> r = HttpRequest()
 >>> c = RequestContext(r, {'a': 'AAA'})
 >>> t = Template('a is <{{a}}> and b is <{{b}}>')
 >>> c['b'] = 'BBB'
 >>> t.render(c)
 u'a is  and b is <>'
 }}}
 In the above note that 'b' is not rendered in the template.

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

Re: [Django] #24846: MySQL Migration SchemaEditor default code is ignorant of other blob/text data types

[Django]

#24846: MySQL Migration SchemaEditor default code is ignorant of other blob/text
data types
--+--
 Reporter:  adamchainz|Owner:  adamchainz
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:  mysql migrations  | Triage Stage:  Unreviewed
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by adamchainz):

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


Comment:

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

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

[Django] #24846: MySQL Migration SchemaEditor default code is ignorant of other blob/text data types

[Django]

#24846: MySQL Migration SchemaEditor default code is ignorant of other blob/text
data types
+--
 Reporter:  adamchainz  |  Owner:  adamchainz
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  1.8
 Severity:  Normal  |   Keywords:  mysql migrations
 Triage Stage:  Unreviewed  |  Has patch:  1
Easy pickings:  0   |  UI/UX:  0
+--
 #22424 added a default check for TextField and BinaryField, but it only
 checks for the `longtext` and `longblob` data types which Django uses for
 Text and Binary fields.

 Some projects may be using custom field classes whose db_type is
 `tinytext`, `mediumblob`, etc. which are also subject to the same no-
 default rule, so the SchemaEditor should be made aware of that, otherwise
 migrations may break.

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

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

Re: [Django] #11964: Using database-level CHECK CONSTRAINTS

[Django]

#11964: Using database-level CHECK CONSTRAINTS
-+-
 Reporter:  schinckel|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  check contsraint | Triage Stage:
 |  Someday/Maybe
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by esigra):

 * cc: esigra (added)


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

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