[Django] #23413: django.contrib.contenttypes.fields has been remove

#23413: django.contrib.contenttypes.fields has been remove ---+-- Reporter: neoblackcap| Owner: nobody Type: Bug| Status: new Component: Documentation |Version: 1.7 Severity: Normal

Re: [Django] #23403: Sitemap bug

#23403: Sitemap bug ---+-- Reporter: igorcc |Owner: igorcc Type: Bug| Status: assigned Component: contrib.sitemaps |

Re: [Django] #23412: Unable to import django.forms.util.ValidationError

#23412: Unable to import django.forms.util.ValidationError ---+-- Reporter: george_edison |Owner: nobody Type: Bug| Status: new Component: Forms |

[Django] #23412: Unable to import django.forms.util.ValidationError

#23412: Unable to import django.forms.util.ValidationError ---+ Reporter: george_edison | Owner: nobody Type: Bug| Status: new Component: Forms |Version: 1.7 Severity: Normal |

Re: [Django] #23395: Clarification on PEP 8 E501: line too long (> 79 characters)

#23395: Clarification on PEP 8 E501: line too long (> 79 characters) --+ Reporter: nrogers64 |Owner: nobody Type: Cleanup/optimization | Status: new

Re: [Django] #23411: Typo on download page, says 1.7 requires at minimum 2.6.5

#23411: Typo on download page, says 1.7 requires at minimum 2.6.5 -+ Reporter: gaqzi|Owner: nobody Type: Bug | Status: new Component:

[Django] #23411: Typo on download page, says 1.7 requires at minimum 2.6.5

#23411: Typo on download page, says 1.7 requires at minimum 2.6.5 -+ Reporter: gaqzi| Owner: nobody Type: Bug | Status: new Component: *.djangoproject.com |Version: 1.7

Re: [Django] #23408: Automaticly created migration calls callable for default only once

#23408: Automaticly created migration calls callable for default only once + Reporter: Harper04|Owner: nobody Type: Bug | Status: new Component: Migrations |

Re: [Django] #23410: Backward migrations change overall state rather than reverting single migration

#23410: Backward migrations change overall state rather than reverting single migration -+-- Reporter: Markush2010 |Owner: nobody Type: Bug | Status: new

[Django] #23410: Backward migrations change overall state rather than reverting single migration

#23410: Backward migrations change overall state rather than reverting single migration -+ Reporter: Markush2010 | Owner: nobody Type: Bug | Status: new Component: Migrations |Version: 1.7

Re: [Django] #23395: Clarification on PEP 8 E501: line too long (> 79 characters)

#23395: Clarification on PEP 8 E501: line too long (> 79 characters) --+ Reporter: nrogers64 |Owner: nobody Type: Cleanup/optimization | Status: new

Re: [Django] #23124: Add touch support for version chooser in documentation

#23124: Add touch support for version chooser in documentation -+- Reporter: jarus|Owner: Type: | adambrenecki Cleanup/optimization |

Re: [Django] #23281: Add explicit link into OneToOneField.parent_link

#23281: Add explicit link into OneToOneField.parent_link --+ Reporter: knowledgepoint-devs |Owner: nobody Type: Cleanup/optimization | Status: new Component:

Re: [Django] #23305: Models that are imported on app's import time are invisible to makemigrations when the application is relabeld

#23305: Models that are imported on app's import time are invisible to makemigrations when the application is relabeld --+ Reporter: rafalp|Owner: nobody Type:

Re: [Django] #23307: max_num limits total number of forms, not empty forms

#23307: max_num limits total number of forms, not empty forms --+ Reporter: velle |Owner: nobody Type: Cleanup/optimization | Status: new Component:

Re: [Django] #23338: Warn when unique=True is set on ForeignKey

#23338: Warn when unique=True is set on ForeignKey --+ Reporter: funkybob |Owner: JLinden Type: New feature | Status: assigned Component: Core

Re: [Django] #23406: Migrations not found when only .pyc files are available (e.g. in a frozen environment)

#23406: Migrations not found when only .pyc files are available (e.g. in a frozen environment) -+- Reporter: danielmenzel |Owner: nobody Type: Bug |

Re: [Django] #21565: values() and values_list() don't work when datetime fields are specified and a GeoManager is used

#21565: values() and values_list() don't work when datetime fields are specified and a GeoManager is used -+- Reporter: brett_energysavvy|Owner: Marc Type: Bug |

[django/django] e91034: Fixed #18757, #14462, #21565 -- Reworked database-...

Branch: refs/heads/master Home: https://github.com/django/django Commit: e9103402c0fa873aea58a6a11dba510cd308cb84 https://github.com/django/django/commit/e9103402c0fa873aea58a6a11dba510cd308cb84 Author: Marc Tamlyn Date: 2014-09-03 (Wed, 03 Sep 2014)

Re: [Django] #18757: Examine ways to get rid of DB backend convert_values()

#18757: Examine ways to get rid of DB backend convert_values() -+- Reporter: akaariai |Owner: mjtamlyn Type: | Status: closed

Re: [Django] #14462: Aggregates default to the database type instead of the field type

#14462: Aggregates default to the database type instead of the field type -+- Reporter: WoLpH|Owner: wogan Type: Bug | Status: closed

Re: [Django] #23340: naturaltime documentation doesn't match behavior

#23340: naturaltime documentation doesn't match behavior --+ Reporter: zachborboa|Owner: nobody Type: Bug | Status: new Component: contrib.humanize

Re: [Django] #23350: mod_wsgi authentication/authorization docs result in extra memory usage

#23350: mod_wsgi authentication/authorization docs result in extra memory usage --+ Reporter: GrahamDumpleton |Owner: nobody Type: Cleanup/optimization | Status:

Re: [Django] #19139: OpenLayersWidget's 'Delete all Features' control doesn't respect GeoModelAdmin's modifiable attribute

#19139: OpenLayersWidget's 'Delete all Features' control doesn't respect GeoModelAdmin's modifiable attribute -+- Reporter: fcurella |Owner: claudep Type: Bug |

Re: [Django] #23376: Inconsistent documentation about required Storage methods

#23376: Inconsistent documentation about required Storage methods -+- Reporter: jaap3|Owner: nobody Type: | Status: new

Re: [Django] #22377: SQL Logging throws an exception when fields have utf-8 characters

#22377: SQL Logging throws an exception when fields have utf-8 characters -+- Reporter: rolanvc@…|Owner: nobody Type: Bug | Status: new

Re: [Django] #23395: Clarification on PEP 8 E501: line too long (> 79 characters)

#23395: Clarification on PEP 8 E501: line too long (> 79 characters) --+ Reporter: nrogers64 |Owner: nobody Type: Cleanup/optimization | Status: new

[django/django] 89559b: Fixed #23409 -- Extract PasswordResetForm.get_user...

Branch: refs/heads/master Home: https://github.com/django/django Commit: 89559bcfb096ccc625e0e9ab41e2136fcb32a514 https://github.com/django/django/commit/89559bcfb096ccc625e0e9ab41e2136fcb32a514 Author: Carl Meyer Date: 2014-09-03 (Wed, 03 Sep 2014)

Re: [Django] #23409: PasswordResetForm should not exclude users with unusable passwords

#23409: PasswordResetForm should not exclude users with unusable passwords --+-- Reporter: carljm|Owner: nobody Type: New feature | Status: closed Component:

Re: [Django] #23409: PasswordResetForm should not exclude users with unusable passwords

#23409: PasswordResetForm should not exclude users with unusable passwords --+-- Reporter: carljm|Owner: nobody Type: New feature | Status: new Component:

Re: [Django] #23409: PasswordResetForm should not exclude users with unusable passwords

#23409: PasswordResetForm should not exclude users with unusable passwords --+-- Reporter: carljm|Owner: nobody Type: New feature | Status: new Component:

[Django] #23409: PasswordResetForm should not exclude users with unusable passwords

#23409: PasswordResetForm should not exclude users with unusable passwords + Reporter: carljm| Owner: nobody Type: New feature | Status: new Component:

Re: [Django] #17101: Add --deploy option to check management command (was: Add "checkdeploy" management command)

#17101: Add --deploy option to check management command -+- Reporter: carljm |Owner: timgraham Type: New feature | Status: assigned Component:

Re: [Django] #23397: Multipart base64 file decoding of fails with large files when the encoded string contains newlines.

#23397: Multipart base64 file decoding of fails with large files when the encoded string contains newlines. ---+ Reporter: jhobbs |Owner: nobody Type: Bug|

Re: [Django] #23397: Multipart base64 file decoding of fails with large files when the encoded string contains newlines.

#23397: Multipart base64 file decoding of fails with large files when the encoded string contains newlines. ---+ Reporter: jhobbs |Owner: nobody Type: Bug|

Re: [Django] #23408: Automaticly created migration calls callable for default only once

#23408: Automaticly created migration calls callable for default only once + Reporter: Harper04|Owner: nobody Type: Bug | Status: new Component: Migrations |

Re: [Django] #19139: OpenLayersWidget's 'Delete all Features' control doesn't respect GeoModelAdmin's modifiable attribute

#19139: OpenLayersWidget's 'Delete all Features' control doesn't respect GeoModelAdmin's modifiable attribute -+- Reporter: fcurella |Owner: nobody Type: Bug |

[django/django] 289d38: [1.6.x] Fixed typo in docs/topics/db/transactions....

Branch: refs/heads/stable/1.6.x Home: https://github.com/django/django Commit: 289d38b731798ed362a5ca343210921e0d5127ab https://github.com/django/django/commit/289d38b731798ed362a5ca343210921e0d5127ab Author: Corey Farwell Date: 2014-09-03 (Wed, 03 Sep 2014)

[django/django] de18a6: [1.7.x] Fixed typo in docs/topics/db/transactions....

Branch: refs/heads/stable/1.7.x Home: https://github.com/django/django Commit: de18a687ada58c5296f3f41b432aa2d26de8e3d9 https://github.com/django/django/commit/de18a687ada58c5296f3f41b432aa2d26de8e3d9 Author: Corey Farwell Date: 2014-09-03 (Wed, 03 Sep 2014)

[django/django] 4db759: Fixed typo in docs/topics/db/transactions.txt.

Branch: refs/heads/master Home: https://github.com/django/django Commit: 4db75925be90affaf49ffe5361b47a56762f93d0 https://github.com/django/django/commit/4db75925be90affaf49ffe5361b47a56762f93d0 Author: Corey Farwell Date: 2014-09-03 (Wed, 03 Sep 2014)

Re: [Django] #23408: Automaticly created migration calls callable for default only once

#23408: Automaticly created migration calls callable for default only once + Reporter: Harper04|Owner: nobody Type: Bug | Status: new Component: Migrations |

[Django] #23408: Automaticly created migration calls callable for default only once

#23408: Automaticly created migration calls callable for default only once + Reporter: Harper04| Owner: nobody Type: Bug | Status: new Component: Migrations |Version: 1.7 Severity: Normal |

Re: [Django] #23406: Migrations not found when only .pyc files are available (e.g. in a frozen environment)

#23406: Migrations not found when only .pyc files are available (e.g. in a frozen environment) -+- Reporter: danielmenzel |Owner: nobody Type: Bug |

Re: [Django] #23406: Migrations not found when only .pyc files are available (e.g. in a frozen environment)

#23406: Migrations not found when only .pyc files are available (e.g. in a frozen environment) -+- Reporter: danielmenzel |Owner: nobody Type: Bug |

Re: [Django] #23406: Migrations not found when only .pyc files are available (e.g. in a frozen environment)

#23406: Migrations not found when only .pyc files are available (e.g. in a frozen environment) -+- Reporter: danielmenzel |Owner: nobody Type: Bug |

Re: [Django] #23406: Migrations not found when only .pyc files are available (e.g. in a frozen environment)

#23406: Migrations not found when only .pyc files are available (e.g. in a frozen environment) -+- Reporter: danielmenzel |Owner: nobody Type: Bug |

Re: [Django] #23405: Blank-able CharFields require default=''

#23405: Blank-able CharFields require default='' +-- Reporter: yuvadm |Owner: nobody Type: Bug | Status: new Component: Migrations | Version:

Re: [Django] #23405: Blank-able CharFields require default=''

#23405: Blank-able CharFields require default='' +-- Reporter: yuvadm |Owner: nobody Type: Bug | Status: new Component: Migrations | Version:

Re: [Django] #23407: makemigrations doesn't use --noinput

#23407: makemigrations doesn't use --noinput -+- Reporter: bmispelon|Owner: nobody Type: | Status: new Cleanup/optimization

Re: [Django] #23406: Migrations not found when only .pyc files are available (e.g. in a frozen environment)

#23406: Migrations not found when only .pyc files are available (e.g. in a frozen environment) -+- Reporter: danielmenzel |Owner: nobody Type: Bug |

Re: [Django] #23406: Migrations not found when only .pyc files are available (e.g. in a frozen environment)

#23406: Migrations not found when only .pyc files are available (e.g. in a frozen environment) -+- Reporter: danielmenzel |Owner: nobody Type: Bug |

[Django] #23407: makemigrations doesn't use --noinput

#23407: makemigrations doesn't use --noinput + Reporter: bmispelon | Owner: nobody Type: Cleanup/optimization | Status: new Component:

[Django] #23406: Migrations not found when only .pyc files are available (e.g. in a frozen environment)

#23406: Migrations not found when only .pyc files are available (e.g. in a frozen environment) -+- Reporter: | Owner: nobody danielmenzel | Status: new Type: Bug |

Re: [Django] #23270: select_related on fields pointing to subclasses does not work when using defer

#23270: select_related on fields pointing to subclasses does not work when using defer -+- Reporter: islavov |Owner: nobody Type: Bug |

Re: [Django] #23405: Blank-able CharFields require default=''

#23405: Blank-able CharFields require default='' +-- Reporter: yuvadm |Owner: nobody Type: Bug | Status: new Component: Migrations | Version:

Re: [Django] #23405: Blank-able CharFields require default=''

#23405: Blank-able CharFields require default='' +-- Reporter: yuvadm |Owner: nobody Type: Bug | Status: new Component: Migrations | Version:

Re: [Django] #22377: SQL Logging throws an exception when fields have utf-8 characters

#22377: SQL Logging throws an exception when fields have utf-8 characters -+- Reporter: rolanvc@…|Owner: nobody Type: Bug | Status: new

[Django] #23405: Blank-able CharFields require default=''

#23405: Blank-able CharFields require default='' + Reporter: yuvadm | Owner: nobody Type: Bug | Status: new Component: Migrations |Version: 1.7 Severity: Normal | Keywords: Triage

Re: [Django] #23399: Update int_to_base36

#23399: Update int_to_base36 -+- Reporter: liminspace |Owner: Type: | liminspace Cleanup/optimization | Status: new

Re: [Django] #23404: Django modelformset returns the same data inserted in the previous insert when opening the same page for inserting new data

#23404: Django modelformset returns the same data inserted in the previous insert when opening the same page for inserting new data -+- Reporter: guruprasad |Owner: nobody Type:

Re: [Django] #23404: Django modelformset returns the same data inserted in the previous insert when opening the same page for inserting new data

#23404: Django modelformset returns the same data inserted in the previous insert when opening the same page for inserting new data -+- Reporter: guruprasad |Owner: nobody Type:

Re: [Django] #23404: Django modelformset returns the same data inserted in the previous insert when opening the same page for inserting new data

#23404: Django modelformset returns the same data inserted in the previous insert when opening the same page for inserting new data -+- Reporter: guruprasad |Owner: nobody Type:

Re: [Django] #23403: Sitemap bug

#23403: Sitemap bug ---+-- Reporter: igorcc |Owner: igorcc Type: Bug| Status: assigned Component: contrib.sitemaps |

Re: [Django] #21001: Non working SQL generated for Oracle when doing .exclude('')

#21001: Non working SQL generated for Oracle when doing .exclude('') -+- Reporter: greenRocker |Owner: nobody Type: Bug | Status: closed

Re: [Django] #23404: Django modelformset returns the same data inserted in the previous insert when opening the same page for inserting new data

#23404: Django modelformset returns the same data inserted in the previous insert when opening the same page for inserting new data -+- Reporter: guruprasad |Owner: nobody Type:

[Django] #23404: Django modelformset returns the same data inserted in the previous insert when opening the same page for inserting new data

#23404: Django modelformset returns the same data inserted in the previous insert when opening the same page for inserting new data +-- Reporter: guruprasad | Owner: nobody Type: Bug | Status: new

Re: [Django] #23396: Regression in #14334 causes ValueError to be thrown on ValuesQuerySets

#23396: Regression in #14334 causes ValueError to be thrown on ValuesQuerySets -+- Reporter: gabejackson |Owner: Type: Bug | gabejackson Component: Database

Re: [Django] #23359: Add ability to show the migration plan

#23359: Add ability to show the migration plan -+--- Reporter: Markush2010 |Owner: Markush2010 Type: New feature | Status: assigned Component: Migrations |

Re: [Django] #23403: Sitemap bug

#23403: Sitemap bug ---+-- Reporter: igorcc |Owner: igorcc Type: Bug| Status: assigned Component: contrib.sitemaps |

[Django] #23403: Sitemap bug

#23403: Sitemap bug --+--- Reporter: igorcc| Owner: nobody Type: Bug | Status: new Component: contrib.sitemaps |Version: 1.7 Severity: Normal| Keywords:

Re: [Django] #23402: Minor incorrect links.

#23402: Minor incorrect links. -+- Reporter: michaelcoconnor |Owner: nobody Type: | Status: closed Cleanup/optimization |