Re: [Django] #23901: Unable to load the SpatiaLite library extension "/usr/local/lib/libspatialite.dylib"

[Django]

#23901: Unable to load the SpatiaLite library extension
"/usr/local/lib/libspatialite.dylib"
-+-
 Reporter:  kenial   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  spatialite   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by kenial:

Old description:

> Installing libspatialite package with Homebrew on OS X and using
> django.contrib.gis.db.backends.spatialite as a database backend, I met
> this exception:
>
> {{{
> Traceback (most recent call last):
>   File "manage.py", line 14, in 
> execute_from_command_line(sys.argv)
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/core/management/__init__.py", line 385, in
> execute_from_command_line
> utility.execute()
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/core/management/__init__.py", line 377, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/core/management/base.py", line 288, in run_from_argv
> self.execute(*args, **options.__dict__)
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/core/management/base.py", line 338, in execute
> output = self.handle(*args, **options)
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/core/management/commands/migrate.py", line 63, in handle
> executor = MigrationExecutor(connection,
> self.migration_progress_callback)
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/migrations/executor.py", line 17, in __init__
> self.loader = MigrationLoader(self.connection)
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/migrations/loader.py", line 48, in __init__
> self.build_graph()
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/migrations/loader.py", line 179, in build_graph
> self.applied_migrations = recorder.applied_migrations()
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/migrations/recorder.py", line 59, in
> applied_migrations
> self.ensure_schema()
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/migrations/recorder.py", line 49, in ensure_schema
> if self.Migration._meta.db_table in
> self.connection.introspection.get_table_list(self.connection.cursor()):
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/backends/__init__.py", line 165, in cursor
> cursor = self.make_debug_cursor(self._cursor())
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/backends/__init__.py", line 138, in _cursor
> self.ensure_connection()
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/backends/__init__.py", line 133, in ensure_connection
> self.connect()
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/backends/__init__.py", line 122, in connect
> self.connection = self.get_new_connection(conn_params)
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/contrib/gis/db/backends/spatialite/base.py", line 65, in
> get_new_connection
> six.reraise(ImproperlyConfigured, ImproperlyConfigured(new_msg),
> sys.exc_info()[2])
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/contrib/gis/db/backends/spatialite/base.py", line 60, in
> get_new_connection
> cur.execute("SELECT load_extension(%s)", (self.spatialite_lib,))
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/backends/sqlite3/base.py", line 485, in execute
> return Database.Cursor.execute(self, query, params)
> django.core.exceptions.ImproperlyConfigured: Unable to load the
> SpatiaLite library extension "/usr/local/lib/libspatialite.dylib"
> because: dlsym(0x7f8bf32f8000, sqlite3_spatialite_init): symbol not found
> }}}
>
> On Homebrew's SpatiaLite 4.2.0 package what I've got, it provides both
> libspatialite.7.dylib and mod_spatialite.7.dylib. For its proper working,
> sqlite3 should load mod_spatialite instead of libspatialite, but it seems
> not detecting right package with ctypes.util.find_library('spatialite').
> In case using find_library('mod_spatialite'), it does work.
>
> I think it might be a problem of entry 

Re: [Django] #23899: A new field/doc note in the settings.py to denote django version

[Django]

#23899: A new field/doc note in the settings.py to denote django version
-+-
 Reporter:  atmb4u   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  settings.py, django  | Triage Stage:  Accepted
  version|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by carljm):

 Hi Russ - I'm not convinced that we should try to use a settings file
 marker of any kind for that upgrade-checks purpose, because you still end
 up with too many false positives ("yes, my project settings were initially
 generated on 1.5, and yes I'm running 1.6, and yes I don't have
 TEST_RUNNER set, and yes, my tests are still just fine, thanks for
 asking"). My proposal here was really geared towards "possibly
 informational for readers, but not intended for machine parsing at all" --
 if we're going to bother with machine parsing a comment, why not just make
 it a setting?

 With the sort of "generated by" comment I'm suggesting here, I'd expect at
 least advanced users - myself included - to just remove it once they go
 through their settings file and edit it sufficiently that it's now more
 "written by me" than "generated by Django". So I wouldn't consider it
 something whose presence Django should rely on.

 (It's somewhat off-topic for this ticket, but my current feeling about
 upgrade checks is that we just simply shouldn't add them at all. People
 who upgrade without bothering to even read the backwards-incompatible-
 changes section of the release notes make their own bed, they can lie in
 it. Checks should only be loud about things that we can confidently say
 are a configuration problem given what we know about the current state,
 not what we try to infer about whether they might have recently upgraded.)

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

Re: [Django] #23901: Unable to load the SpatiaLite library extension "/usr/local/lib/libspatialite.dylib"

[Django]

#23901: Unable to load the SpatiaLite library extension
"/usr/local/lib/libspatialite.dylib"
-+-
 Reporter:  kenial   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  spatialite   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by kenial:

Old description:

> Installing libspatialite package with Homebrew on OS X and using
> django.contrib.gis.db.backends.spatialite as a database backend, I met
> this exception:
>
> {{{
> Traceback (most recent call last):
>   File "manage.py", line 14, in 
> execute_from_command_line(sys.argv)
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/core/management/__init__.py", line 385, in
> execute_from_command_line
> utility.execute()
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/core/management/__init__.py", line 377, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/core/management/base.py", line 288, in run_from_argv
> self.execute(*args, **options.__dict__)
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/core/management/base.py", line 338, in execute
> output = self.handle(*args, **options)
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/core/management/commands/migrate.py", line 63, in handle
> executor = MigrationExecutor(connection,
> self.migration_progress_callback)
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/migrations/executor.py", line 17, in __init__
> self.loader = MigrationLoader(self.connection)
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/migrations/loader.py", line 48, in __init__
> self.build_graph()
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/migrations/loader.py", line 179, in build_graph
> self.applied_migrations = recorder.applied_migrations()
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/migrations/recorder.py", line 59, in
> applied_migrations
> self.ensure_schema()
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/migrations/recorder.py", line 49, in ensure_schema
> if self.Migration._meta.db_table in
> self.connection.introspection.get_table_list(self.connection.cursor()):
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/backends/__init__.py", line 165, in cursor
> cursor = self.make_debug_cursor(self._cursor())
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/backends/__init__.py", line 138, in _cursor
> self.ensure_connection()
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/backends/__init__.py", line 133, in ensure_connection
> self.connect()
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/backends/__init__.py", line 122, in connect
> self.connection = self.get_new_connection(conn_params)
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/contrib/gis/db/backends/spatialite/base.py", line 65, in
> get_new_connection
> six.reraise(ImproperlyConfigured, ImproperlyConfigured(new_msg),
> sys.exc_info()[2])
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/contrib/gis/db/backends/spatialite/base.py", line 60, in
> get_new_connection
> cur.execute("SELECT load_extension(%s)", (self.spatialite_lib,))
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/backends/sqlite3/base.py", line 485, in execute
> return Database.Cursor.execute(self, query, params)
> django.core.exceptions.ImproperlyConfigured: Unable to load the
> SpatiaLite library extension "/usr/local/lib/libspatialite.dylib"
> because: dlsym(0x7f8bf32f8000, sqlite3_spatialite_init): symbol not found
> }}}
>
> On Homebrew's SpatiaLite 4.2.0 package what I've got, it provides both
> libspatialite.7.dylib and mod_spatialite.7.dylib. For its proper working,
> sqlite3 should load mod_spatialite instead of libspatialite, but it seems
> not detecting right package with ctypes.util.find_library('spatialite').
> In case using find_library('mod_spatialite'), it does work.
>
> I think it might be a problem of entry 

Re: [Django] #23901: Unable to load the SpatiaLite library extension "/usr/local/lib/libspatialite.dylib"

[Django]

#23901: Unable to load the SpatiaLite library extension
"/usr/local/lib/libspatialite.dylib"
-+-
 Reporter:  kenial   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  spatialite   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by kenial):

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


Old description:

> Installing libspatialite package with Homebrew on OS X and using
> django.contrib.gis.db.backends.spatialite as a database backend, I met
> this exception:
>
> {{{
> Traceback (most recent call last):
>   File "manage.py", line 14, in 
> execute_from_command_line(sys.argv)
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/core/management/__init__.py", line 385, in
> execute_from_command_line
> utility.execute()
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/core/management/__init__.py", line 377, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/core/management/base.py", line 288, in run_from_argv
> self.execute(*args, **options.__dict__)
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/core/management/base.py", line 338, in execute
> output = self.handle(*args, **options)
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/core/management/commands/migrate.py", line 63, in handle
> executor = MigrationExecutor(connection,
> self.migration_progress_callback)
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/migrations/executor.py", line 17, in __init__
> self.loader = MigrationLoader(self.connection)
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/migrations/loader.py", line 48, in __init__
> self.build_graph()
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/migrations/loader.py", line 179, in build_graph
> self.applied_migrations = recorder.applied_migrations()
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/migrations/recorder.py", line 59, in
> applied_migrations
> self.ensure_schema()
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/migrations/recorder.py", line 49, in ensure_schema
> if self.Migration._meta.db_table in
> self.connection.introspection.get_table_list(self.connection.cursor()):
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/backends/__init__.py", line 165, in cursor
> cursor = self.make_debug_cursor(self._cursor())
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/backends/__init__.py", line 138, in _cursor
> self.ensure_connection()
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/backends/__init__.py", line 133, in ensure_connection
> self.connect()
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/backends/__init__.py", line 122, in connect
> self.connection = self.get_new_connection(conn_params)
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/contrib/gis/db/backends/spatialite/base.py", line 65, in
> get_new_connection
> six.reraise(ImproperlyConfigured, ImproperlyConfigured(new_msg),
> sys.exc_info()[2])
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/contrib/gis/db/backends/spatialite/base.py", line 60, in
> get_new_connection
> cur.execute("SELECT load_extension(%s)", (self.spatialite_lib,))
>   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
> packages/django/db/backends/sqlite3/base.py", line 485, in execute
> return Database.Cursor.execute(self, query, params)
> django.core.exceptions.ImproperlyConfigured: Unable to load the
> SpatiaLite library extension "/usr/local/lib/libspatialite.dylib"
> because: dlsym(0x7f8bf32f8000, sqlite3_spatialite_init): symbol not found
> }}}
>
> On Homebrew's SpatiaLite 4.2.0 package what I've got, it provides both
> libspatialite.7.dylib and mod_spatialite.7.dylib. For its proper working,
> sqlite3 should load mod_spatialite instead of libspatialite, but it seems
> not detecting right package with ctypes.util.find_library('spatialite').
> In case using 

[Django] #23901: Unable to load the SpatiaLite library extension "/usr/local/lib/libspatialite.dylib"

[Django]

#23901: Unable to load the SpatiaLite library extension
"/usr/local/lib/libspatialite.dylib"
--+
 Reporter:  kenial|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.7
 Severity:  Normal|   Keywords:  spatialite
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+
 Installing libspatialite package with Homebrew on OS X and using
 django.contrib.gis.db.backends.spatialite as a database backend, I met
 this exception:

 {{{
 Traceback (most recent call last):
   File "manage.py", line 14, in 
 execute_from_command_line(sys.argv)
   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 385, in
 execute_from_command_line
 utility.execute()
   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 377, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
 packages/django/core/management/base.py", line 288, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
 packages/django/core/management/base.py", line 338, in execute
 output = self.handle(*args, **options)
   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
 packages/django/core/management/commands/migrate.py", line 63, in handle
 executor = MigrationExecutor(connection,
 self.migration_progress_callback)
   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
 packages/django/db/migrations/executor.py", line 17, in __init__
 self.loader = MigrationLoader(self.connection)
   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
 packages/django/db/migrations/loader.py", line 48, in __init__
 self.build_graph()
   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
 packages/django/db/migrations/loader.py", line 179, in build_graph
 self.applied_migrations = recorder.applied_migrations()
   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
 packages/django/db/migrations/recorder.py", line 59, in applied_migrations
 self.ensure_schema()
   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
 packages/django/db/migrations/recorder.py", line 49, in ensure_schema
 if self.Migration._meta.db_table in
 self.connection.introspection.get_table_list(self.connection.cursor()):
   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
 packages/django/db/backends/__init__.py", line 165, in cursor
 cursor = self.make_debug_cursor(self._cursor())
   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
 packages/django/db/backends/__init__.py", line 138, in _cursor
 self.ensure_connection()
   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
 packages/django/db/backends/__init__.py", line 133, in ensure_connection
 self.connect()
   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
 packages/django/db/backends/__init__.py", line 122, in connect
 self.connection = self.get_new_connection(conn_params)
   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
 packages/django/contrib/gis/db/backends/spatialite/base.py", line 65, in
 get_new_connection
 six.reraise(ImproperlyConfigured, ImproperlyConfigured(new_msg),
 sys.exc_info()[2])
   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
 packages/django/contrib/gis/db/backends/spatialite/base.py", line 60, in
 get_new_connection
 cur.execute("SELECT load_extension(%s)", (self.spatialite_lib,))
   File "/Users/kenial/.virtualenvs/fp/lib/python2.7/site-
 packages/django/db/backends/sqlite3/base.py", line 485, in execute
 return Database.Cursor.execute(self, query, params)
 django.core.exceptions.ImproperlyConfigured: Unable to load the SpatiaLite
 library extension "/usr/local/lib/libspatialite.dylib" because:
 dlsym(0x7f8bf32f8000, sqlite3_spatialite_init): symbol not found
 }}}

 On Homebrew's SpatiaLite 4.2.0 package what I've got, it provides both
 libspatialite.7.dylib and mod_spatialite.7.dylib. For its proper working,
 sqlite3 should load mod_spatialite instead of libspatialite, but it seems
 not detecting right package with ctypes.util.find_library('spatialite').
 In case using find_library('mod_spatialite'), it does work.

--
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 

Re: [Django] #23251: Use a temporary folder to store uploaded files during tests

[Django]

#23251: Use a temporary folder to store uploaded files during tests
-+
 Reporter:  shai |Owner:
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  file storage upload  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by pavel_shpilev):

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


Comment:

 Oops, sorry. I was sure I deassigned myself.
 Please, feel free to take it over.

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

Re: [Django] #23899: A new field/doc note in the settings.py to denote django version

[Django]

#23899: A new field/doc note in the settings.py to denote django version
-+-
 Reporter:  atmb4u   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  settings.py, django  | Triage Stage:  Accepted
  version|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by freakboy3742):

 This would also be useful for upgrade checks. At present, when we do
 version change checks (e.g., checks related to TEST_RUNNER) we have to
 guess whether the project is "1.5 and has been upgraded" or "1.6 with a
 specific collection of settings". There are tickets reporting false
 positives related to these checks, which is to be expected, because things
 like "User has TEMPLATE_DIRS set" aren't a reliable way to check that
 you're running a particular Django version.

 Having a setting (or, as Carl suggests, a "meta" setting that is actually
 a comment) that represents "This project configuration is known to be
 correct for version X" would be very helpful for this purpose. The key
 thing here is that it isn't just a "Generated on v1.N" setting, because
 you can update the settings over time and know that the settings file is
 "good" for v1.(N+1). Being easily machine parseable is also important.

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

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

Re: [Django] #12708: Django raises DoesNotExist when consulting an empty ForeignKey field

[Django]

#12708: Django raises DoesNotExist when consulting an empty ForeignKey field
-+-
 Reporter:  lsaffre  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:  invalid
  (models, ORM)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:  ForeignKey   |  Needs documentation:  0
  DoesNotExist   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by simon29):

 * cc: simon@… (added)
 * type:  Uncategorized => Cleanup/optimization


Comment:

 @lukeplant, perhaps this is something that should be cleaned up and
 flagged as backward incompatible in the next major release? We ought to be
 able to check the value of a field without raising an artificial error, or
 resorting to workarounds.

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

Re: [Django] #23900: Section on Preventing header injection does not include some imports

[Django]

#23900: Section on Preventing header injection does not include some imports
-+-
 Reporter:  kevgathuku   |Owner:
 Type:   |  kevgathuku
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  BadHeaderError,  | Triage Stage:  Ready for
  docs   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Baptiste Mispelon ):

 In [changeset:"db227d9d20d848c56f94ce0ca175fde7e1180c21"]:
 {{{
 #!CommitTicketReference repository=""
 revision="db227d9d20d848c56f94ce0ca175fde7e1180c21"
 [1.6.x] Fixed #23900 -- Added missing imports in code example.

 The Preventing header injection example included
 classes that are not imported.

 Thanks to Collin Anderson and Berker Peksağ for the
 reviews.

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

Re: [Django] #23900: Section on Preventing header injection does not include some imports

[Django]

#23900: Section on Preventing header injection does not include some imports
-+-
 Reporter:  kevgathuku   |Owner:
 Type:   |  kevgathuku
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  BadHeaderError,  | Triage Stage:  Ready for
  docs   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Baptiste Mispelon ):

 In [changeset:"22d292e23b1b60fd5c304b3d867ecf70860e7048"]:
 {{{
 #!CommitTicketReference repository=""
 revision="22d292e23b1b60fd5c304b3d867ecf70860e7048"
 [1.7.x] Fixed #23900 -- Added missing imports in code example.

 The Preventing header injection example included
 classes that are not imported.

 Thanks to Collin Anderson and Berker Peksağ for the
 reviews.

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

Re: [Django] #23900: Section on Preventing header injection does not include some imports

[Django]

#23900: Section on Preventing header injection does not include some imports
-+-
 Reporter:  kevgathuku   |Owner:
 Type:   |  kevgathuku
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  BadHeaderError,  | Triage Stage:  Ready for
  docs   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Baptiste Mispelon ):

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


Comment:

 In [changeset:"0d74209ef66111f29f122d5f5fdf8e2964890cc5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0d74209ef66111f29f122d5f5fdf8e2964890cc5"
 Fixed #23900 -- Added missing imports in code example.

 The Preventing header injection example included
 classes that are not imported.

 Thanks to Collin Anderson and Berker Peksağ for the
 reviews.
 }}}

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

Re: [Django] #22569: lookup_allowed fails to consider dynamic list_filter

[Django]

#22569: lookup_allowed fails to consider dynamic list_filter
-+-
 Reporter:  Keryn Knight |Owner:
   |  parasgithub
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  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 parasgithub):

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


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

Re: [Django] #23900: Section on Preventing header injection does not include some imports

[Django]

#23900: Section on Preventing header injection does not include some imports
-+-
 Reporter:  kevgathuku   |Owner:
 Type:   |  kevgathuku
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  BadHeaderError,  | Triage Stage:  Ready for
  docs   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by berkerpeksag):

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

Re: [Django] #4278: get_template should accept a dirs argument

[Django]

#4278: get_template should accept a dirs argument
-+
 Reporter:  amcnabb  |Owner:  berkerpeksag
 Type:  New feature  |   Status:  closed
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  tplrf-patched| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by Aymeric Augustin ):

 In [changeset:"17012b6936128fb771b98e4fa6d78caddd07a9a8"]:
 {{{
 #!CommitTicketReference repository=""
 revision="17012b6936128fb771b98e4fa6d78caddd07a9a8"
 Deprecated dirs argument to override TEMPLATE_DIRS.

 Cancels 2f0566fa. Refs #4278.
 }}}

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

Re: [Django] #23900: Section on Preventing header injection does not include some imports

[Django]

#23900: Section on Preventing header injection does not include some imports
-+-
 Reporter:  kevgathuku   |Owner:
 Type:   |  kevgathuku
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  BadHeaderError,  | Triage Stage:  Accepted
  docs   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by berkerpeksag):

 * version:  1.7 => master
 * component:  Uncategorized => Documentation
 * stage:  Unreviewed => Accepted


Comment:

 PR is at https://github.com/django/django/pull/3608 and LGTM.

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

Re: [Django] #18105: Investigate possible misuse of Context

[Django]

#18105: Investigate possible misuse of Context
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Template system   |  Version:  1.4
 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):

 [73317883] changed `render_to_response` so it wouldn't rewrap a `Context`
 inadvertently passed in the `dictionary` argument in another `Context`.
 That's the opposite of the route taken by first patch above and I'm
 convinced it's a better approach given how widespread `render_to_response`
 is and how easy forgetting `context_instance=` is.

 The second patch still warrants consideration. I had a look and I don't
 think the code inside `if isinstance(_dict, BaseContext)` is correct: it
 adds values such as `autoescape` and `current_app` to the context when
 they're intended to be attributes of the context object.

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

Re: [Django] #23251: Use a temporary folder to store uploaded files during tests

[Django]

#23251: Use a temporary folder to store uploaded files during tests
-+-
 Reporter:  shai |Owner:
 Type:  Bug  |  pavel_shpilev
Component:  Testing framework|   Status:  assigned
 Severity:  Normal   |  Version:  master
 Keywords:  file storage upload  |   Resolution:
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by berkerpeksag):

 * needs_docs:  1 => 0
 * needs_tests:  1 => 0


Comment:

 Pavel, do you working on this? If not, I can take a look at this.

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

Re: [Django] #23897: makemessages does not work if STATIC_ROOT isn't defined

[Django]

#23897: makemessages does not work if STATIC_ROOT isn't defined
-+-
 Reporter:  igorcc   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:  master
  Internationalization   |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by claudep:

Old description:

> After new project is created, I have put into settings.py:
>
> {{{
> LOCALE_PATHS = (
> os.path.join(BASE_DIR, 'locale'),
> )
> LANGUAGES = (
> ('ru', 'Russian'),
> ('en', 'English'),
> )
> }}}
>
> I have created directory 'locale' under BASE_PATH as well.
> And after I ran ./manage.py makemessages -l ru I got:
>
> ''Traceback (most recent call last):
>   File
> "/Applications/PyCharm.app/Contents/helpers/pycharm/django_manage.py",
> line 41, in 
> run_module(manage_file, None, '__main__', True)
>   File
> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py",
> line 176, in run_module
> fname, loader, pkg_name)
>   File
> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py",
> line 82, in _run_module_code
> mod_name, mod_fname, mod_loader, pkg_name)
>   File
> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py",
> line 72, in _run_code
> exec code in run_globals
>   File "/Users/igo/PycharmProjects/TestTest/manage.py", line 10, in
> 
> execute_from_command_line(sys.argv)
>   File "/Users/igo/Django/lib/python2.7/site-
> packages/django/core/management/__init__.py", line 385, in
> execute_from_command_line
> utility.execute()
>   File "/Users/igo/Django/lib/python2.7/site-
> packages/django/core/management/__init__.py", line 377, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/Users/igo/Django/lib/python2.7/site-
> packages/django/core/management/base.py", line 288, in run_from_argv
> self.execute(*args, **options.__dict__)
>   File "/Users/igo/Django/lib/python2.7/site-
> packages/django/core/management/base.py", line 338, in execute
> output = self.handle(*args, **options)
>   File "/Users/igo/Django/lib/python2.7/site-
> packages/django/core/management/base.py", line 533, in handle
> return self.handle_noargs(**options)
>   File "/Users/igo/Django/lib/python2.7/site-
> packages/django/core/management/commands/makemessages.py", line 283, in
> handle_noargs
> potfiles = self.build_potfiles()
>   File "/Users/igo/Django/lib/python2.7/site-
> packages/django/core/management/commands/makemessages.py", line 299, in
> build_potfiles
> file_list = self.find_files(".")
>   File "/Users/igo/Django/lib/python2.7/site-
> packages/django/core/management/commands/makemessages.py", line 358, in
> find_files
> ignored_roots = [os.path.normpath(p) for p in (settings.MEDIA_ROOT,
> settings.STATIC_ROOT)]
>   File "/Users/igo/Django/lib/python2.7/posixpath.py", line 327, in
> normpath
> initial_slashes = path.startswith('/')
> AttributeError: 'NoneType' object has no attribute 'startswith'''

New description:

 After new project is created, I have put into settings.py:

 {{{
 LOCALE_PATHS = (
 os.path.join(BASE_DIR, 'locale'),
 )
 LANGUAGES = (
 ('ru', 'Russian'),
 ('en', 'English'),
 )
 }}}

 I have created directory 'locale' under BASE_PATH as well.
 And after I ran ./manage.py makemessages -l ru I got:

 {{{
 Traceback (most recent call last):
   File
 "/Applications/PyCharm.app/Contents/helpers/pycharm/django_manage.py",
 line 41, in 
 run_module(manage_file, None, '__main__', True)
   File
 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py",
 line 176, in run_module
 fname, loader, pkg_name)
   File
 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py",
 line 82, in _run_module_code
 mod_name, mod_fname, mod_loader, pkg_name)
   File
 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py",
 line 72, in _run_code
 exec code in run_globals
   File "/Users/igo/PycharmProjects/TestTest/manage.py", line 10, in
 
 execute_from_command_line(sys.argv)
   File "/Users/igo/Django/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 385, in
 execute_from_command_line
 utility.execute()
   File "/Users/igo/Django/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 377, in execute
 

Re: [Django] #23897: makemessages does not work if STATIC_ROOT isn't defined

[Django]

#23897: makemessages does not work if STATIC_ROOT isn't defined
-+-
 Reporter:  igorcc   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:  master
  Internationalization   |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

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


Comment:

 Yes, it is.

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

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

Re: [Django] #12982: Add get_or_set method to cache API

[Django]

#12982: Add get_or_set method to cache API
-+-
 Reporter:  Alex |Owner:
 Type:  New feature  |  berkerpeksag
Component:  Core (Cache system)  |   Status:  assigned
 Severity:  Normal   |  Version:  master
 Keywords:  cache|   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 berkerpeksag):

 * owner:  snow0x2d0 => berkerpeksag
 * needs_better_patch:  1 => 0
 * status:  new => assigned


Comment:

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

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

Re: [Django] #23742: Option to run Django tests in reverse

[Django]

#23742: Option to run Django tests in reverse
-+-
 Reporter:  wrwrwr   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by prestontimmons):

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

Re: [Django] #23742: Option to run Django tests in reverse

[Django]

#23742: Option to run Django tests in reverse
---+
 Reporter:  wrwrwr |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by prestontimmons):

 This patch looks good to me.

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

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

Re: [Django] #23899: A new field/doc note in the settings.py to denote django version

[Django]

#23899: A new field/doc note in the settings.py to denote django version
-+-
 Reporter:  atmb4u   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  settings.py, django  | Triage Stage:  Accepted
  version|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by carljm):

 * stage:  Unreviewed => Accepted


Comment:

 Generating an actual setting for this is a bad idea, IMO -- too unclear
 what effect it would have, too likely to become out of date or be edited
 wrongly, and too likely to be used in ways that would cause breakage if
 so.

 But I could see value in adding a simple comment like `# Generated by
 'django-admin.py startproject', Django 1.7.1`, on the general principle
 that it's good practice for automatic code generators to insert a
 "generated by" comment. That's clearly a "this file generated by", not a
 "this project runs with", so it's less likely to be incorrectly edited
 (and doesn't really matter that much if it is). There are definitely times
 I would have found this useful, just to get a rough idea of which settings
 I ought to check for possible updates needed.

 Accepting on that basis.

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

Re: [Django] #23900: Section on Preventing header injection does not include some imports

[Django]

#23900: Section on Preventing header injection does not include some imports
-+-
 Reporter:  kevgathuku   |Owner:
 Type:   |  kevgathuku
  Cleanup/optimization   |   Status:  assigned
Component:  Uncategorized|  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  BadHeaderError,  | Triage Stage:
  docs   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by kevgathuku):

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

Re: [Django] #23900: Section on Preventing header injection does not include some imports

[Django]

#23900: Section on Preventing header injection does not include some imports
-+-
 Reporter:  kevgathuku   |Owner:
 Type:   |  kevgathuku
  Cleanup/optimization   |   Status:  assigned
Component:  Uncategorized|  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  BadHeaderError,  | Triage Stage:
  docs   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by kevgathuku):

 * status:  new => assigned
 * needs_docs:   => 0
 * owner:  nobody => kevgathuku
 * 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/068.178e2f33386ff200c8b85917acb2ac2f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20392: Rearrange transactional behavior in django.test.TestCase: savepoints around tests

[Django]

#20392: Rearrange transactional behavior in django.test.TestCase: savepoints 
around
tests
-+-
 Reporter:  xelnor   |Owner:
 Type:  New feature  |   Status:  new
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  test atomic  | Triage Stage:  Accepted
  savepoint  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by tchaumeny):

 * needs_better_patch:  1 => 0


Comment:

 Thanks for the review. I updated the PR to address your comments.

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

[Django] #23900: Section on Preventing header injection does not include some imports

[Django]

#23900: Section on Preventing header injection does not include some imports
--+--
 Reporter:  kevgathuku|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Uncategorized |Version:  1.7
 Severity:  Normal|   Keywords:  BadHeaderError, docs
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+--
 The documentation section on Preventing header injection
 https://docs.djangoproject.com/en/1.7/topics/email/#preventing-header-
 injection, and specifically, the example provided uses HttpResponse and
 HttpResponseRedirect yet they are not imported.

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

Re: [Django] #23899: A new field/doc note in the settings.py to denote django version

[Django]

#23899: A new field/doc note in the settings.py to denote django version
-+-
 Reporter:  atmb4u   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  settings.py, django  | Triage Stage:
  version|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by erikr):

 * needs_better_patch:   => 0
 * component:  Core (System checks) => Core (Other)
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 My concern with this idea is that there is nothing enforcing this to be up
 to date, whereas that is more the case with requirements.txt. That would
 make it very unreliable in practice to indicate which version this project
 is supposed to run with. It may be used indicate which Django version's
 project template was used to initially create the project, but I'm not
 sure what the added value would be. Also, that would be unreliable because
 people may assume that should match the running version, and simply update
 it with each upgrade.

 In other words: as far as I can see there is little added value due to the
 low reliability. The recommended way to ensure you are running a
 particular version is and has been requirements.txt. But perhaps there's
 something I'm overlooking :)

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

[Django] #23899: A new field/doc note in the settings.py to denote django version

[Django]

#23899: A new field/doc note in the settings.py to denote django version
-+-
 Reporter:  atmb4u   |  Owner:  nobody
 Type:  New feature  | Status:  new
Component:  Core (System |Version:  master
  checks)|   Keywords:  settings.py, django
 Severity:  Normal   |  version
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  1|  UI/UX:  0
-+-
 A field to know which django version was used to create the project. This
 will be helpful while setting up the code in a new environment. Solutions
 like requirements.txt do exist, but a quickly accessible variable/ note in
 the auto-generated help in the settings.py without a requirements.txt
 would make project for self contained.

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

Re: [Django] #23898: django.contrib.admin.actions.delete_selected missing admin_site.each_context

[Django]

#23898: django.contrib.admin.actions.delete_selected missing
admin_site.each_context
-+-
 Reporter:  redouane |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  delete_selected  | Triage Stage:  Accepted
  action, each_context, site_title,  |  Needs documentation:  0
  site_header, site_url  |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  1|
-+-

Comment (by aaugustin):

 Can you use the same style as other views in
 django/contrib/admin/options.py?

 While you're there it would be nice to support `extra_context` too
 (#12044).

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

Re: [Django] #23898: django.contrib.admin.actions.delete_selected missing admin_site.each_context

[Django]

#23898: django.contrib.admin.actions.delete_selected missing
admin_site.each_context
-+-
 Reporter:  redouane |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  delete_selected  | Triage Stage:  Accepted
  action, each_context, site_title,  |  Needs documentation:  0
  site_header, site_url  |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  1|
-+-
Changes (by bmispelon):

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


Comment:

 Hi,

 The pull request looks good but it's missing some tests.

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

Re: [Django] #23898: django.contrib.admin.actions.delete_selected missing admin_site.each_context

[Django]

#23898: django.contrib.admin.actions.delete_selected missing
admin_site.each_context
-+-
 Reporter:  redouane |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  delete_selected  | Triage Stage:
  action, each_context, site_title,  |  Unreviewed
  site_header, site_url  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by redouane):

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

Re: [Django] #23898: django.contrib.admin.actions.delete_selected missing admin_site.each_context

[Django]

#23898: django.contrib.admin.actions.delete_selected missing
admin_site.each_context
-+-
 Reporter:  redouane |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  delete_selected  | Triage Stage:
  action, each_context, site_title,  |  Unreviewed
  site_header, site_url  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by redouane):

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


Comment:

 pull request sent.
 https://github.com/django/django/pull/3607

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

[Django] #23898: django.contrib.admin.actions.delete_selected missing admin_site.each_context

[Django]

#23898: django.contrib.admin.actions.delete_selected missing
admin_site.each_context
-+-
 Reporter:   |  Owner:  nobody
  redouane   | Status:  new
 Type:  Bug  |Version:  1.7
Component:   |   Keywords:  delete_selected action,
  contrib.admin  |  each_context, site_title, site_header, site_url
 Severity:  Normal   |  Has patch:  0
 Triage Stage:   |  UI/UX:  0
  Unreviewed |
Easy pickings:  1|
-+-
 Hello,
 in django's delete_selected action
 (django.contrib.admin.actions.delete_selected)
 the templates are rendered without admin_site's each_context, and thus
 it always renders the default values for admin_site.each_context() key
 attributes (site_title, site_header, site_url)
 So if you override/use custom values for site_title, site_header, site_url
 they will not be used on the delete_selected action view.

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