Re: [Django] #20261: Changing a Site fails if the user has a string ID.

[Django]

#20261: Changing a Site fails if the user has a string ID.
---+--
 Reporter:  stavros|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.5
 Severity:  Normal |   Resolution:  duplicate
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by russellm):

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


Comment:

 This is a
 [https://docs.djangoproject.com/en/1.5/topics/auth/customizing/#specifying-a
 -custom-user-model known and documented limitation of Django's User
 system]

 #14881 tracks the underlying problem.

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

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

Re: [Django] #14402: help_text is not displayed for ManyToMany raw_id fields

[Django]

#14402: help_text is not displayed for ManyToMany raw_id fields
---+
 Reporter:  tyrion |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  master
 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:  1
---+
Description changed by ramiro:

Old description:

> {{{
> #!python
> if db_field.name in self.raw_id_fields:
> kwargs['widget'] = widgets.ManyToManyRawIdWidget(db_field.rel,
> using=db)
> kwargs['help_text'] = ''
> }}}
> In `contrib.admin.options.BaseModelAdmin.formfield_for_manytomany` the
> help_text is reset to `""` because otherwise `ManyToManyField.__init__`
> would prependo to it 'Hold down "Control", or "Command"...':
> {{{
> #!python
> msg = _('Hold down "Control", or "Command" on a Mac, to select more than
> one.')
> self.help_text = string_concat(self.help_text, ' ', msg)
> }}}

New description:

 {{{
 #!python
 if db_field.name in self.raw_id_fields:
 kwargs['widget'] = widgets.ManyToManyRawIdWidget(db_field.rel,
 using=db)
 kwargs['help_text'] = ''
 }}}
 In `contrib.admin.options.BaseModelAdmin.formfield_for_manytomany` the
 help_text is reset to `""` because otherwise `ManyToManyField.__init__`
 would append 'Hold down "Control", or "Command"...' to it:
 {{{
 #!python
 msg = _('Hold down "Control", or "Command" on a Mac, to select more than
 one.')
 self.help_text = string_concat(self.help_text, ' ', msg)
 }}}

--

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

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

Re: [Django] #20258: "managed" attr of Model meta class losted during inheritance from abstract model

[Django]

#20258: "managed" attr of Model meta class losted during inheritance from 
abstract
model
-+-
 Reporter:  vsafronovich |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  invalid
 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 ramiro):

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


Comment:

 To achieve that, make C's inner Meta class inherit from A's one::
 {{{
 class C(A):
 class Meta(A.Meta):
 db_table = 'ccc'
 }}}
 See https://docs.djangoproject.com/en/dev/topics/db/models/#meta-
 inheritance

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

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

Re: [Django] #18231: i18n javascript_catalog View Pollutes Global Namespace

[Django]

#18231: i18n javascript_catalog View Pollutes Global Namespace
-+-
 Reporter:  Matthew Tretter  |Owner:  nobody
  |   Status:  closed
 Type:  Bug  |  Version:  master
Component:   |   Resolution:  fixed
  Internationalization   | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  javascript i18n  |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by Ramiro Morales ):

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


Comment:

 In [changeset:"a506b6981bc48caec30bca3de94d2ac3e6fc1660"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a506b6981bc48caec30bca3de94d2ac3e6fc1660"
 Fixed #18231 -- Made JavaScript i18n not pollute global JS namespace.

 Also, use Django templating for the dynamic generated JS code and use
 more idiomatic coding techniques.

 Thanks Matthew Tretter for the report and the patch.
 }}}

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

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

[django/django] a506b6: Fixed #18231 -- Made JavaScript i18n not pollute g...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a506b6981bc48caec30bca3de94d2ac3e6fc1660
  
https://github.com/django/django/commit/a506b6981bc48caec30bca3de94d2ac3e6fc1660
  Author: Matthew Tretter 
  Date:   2013-04-14 (Sun, 14 Apr 2013)

  Changed paths:
M AUTHORS
M django/contrib/admin/static/admin/js/jquery.init.js
M django/views/i18n.py
M tests/view_tests/tests/test_i18n.py

  Log Message:
  ---
  Fixed #18231 -- Made JavaScript i18n not pollute global JS namespace.

Also, use Django templating for the dynamic generated JS code and use
more idiomatic coding techniques.

Thanks Matthew Tretter for the report and the patch.



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

Re: [Django] #20186: Overriding registration/logged_out.html template doesn't work

[Django]

#20186: Overriding registration/logged_out.html template doesn't work
-+-
 Reporter:  honyczek |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  1.5
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  templates, auth, | Triage Stage:
  login, logout  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by herve):

 Just got hit by that bug in Django 1.5.1.

 I have overridden "registration/login.html" without even thinking about
 it, but then I wanted to override all of the other "registration/*.html"
 templates.

 But only "login.html" will come from my app (the last one in
 INSTALLED_APPS). All of the other ones are still the admin templates.

 I'll try and set up a minimal projet to reproduce the issue.

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

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

[Django] #20261: Changing a Site fails if the user has a string ID.

[Django]

#20261: Changing a Site fails if the user has a string ID.
---+
 Reporter:  stavros|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I'm running Django 1.5 and have a custom User model that has a string ID
 field. When I try to change a site, I get the following error:


 {{{
 Environment:


 Request Method: POST
 Request URL: http://staging.getinstabot.com/narnia/sites/site/1/

 Django Version: 1.5
 Python Version: 2.7.3
 Installed Applications:
 ['django.contrib.auth',
  'django.contrib.contenttypes',
  'django.contrib.sessions',
  'django.contrib.sites',
  'django.contrib.messages',
  'django.contrib.admin',
  'django_browserid',
  'django_extensions',
  'django_forms_bootstrap',
  'backend',
  'loginas',
  'south',
  'gunicorn',
  'mediagenerator',
  'main']
 Installed Middleware:
 ('django.middleware.common.CommonMiddleware',
  'django.contrib.sessions.middleware.SessionMiddleware',
  'django.middleware.csrf.CsrfViewMiddleware',
  'django.contrib.auth.middleware.AuthenticationMiddleware',
  'django.contrib.messages.middleware.MessageMiddleware',
  'middleware.InterstitialMiddleware')


 Traceback:
 File "/var/projects/instabot/env/local/lib/python2.7/site-
 packages/django/core/handlers/base.py" in get_response
   115. response = callback(request,
 *callback_args, **callback_kwargs)
 File "/var/projects/instabot/env/local/lib/python2.7/site-
 packages/django/contrib/admin/options.py" in wrapper
   372. return self.admin_site.admin_view(view)(*args,
 **kwargs)
 File "/var/projects/instabot/env/local/lib/python2.7/site-
 packages/django/utils/decorators.py" in _wrapped_view
   91. response = view_func(request, *args, **kwargs)
 File "/var/projects/instabot/env/local/lib/python2.7/site-
 packages/django/views/decorators/cache.py" in _wrapped_view_func
   89. response = view_func(request, *args, **kwargs)
 File "/var/projects/instabot/env/local/lib/python2.7/site-
 packages/django/contrib/admin/sites.py" in inner
   202. return view(request, *args, **kwargs)
 File "/var/projects/instabot/env/local/lib/python2.7/site-
 packages/django/utils/decorators.py" in _wrapper
   25. return bound_func(*args, **kwargs)
 File "/var/projects/instabot/env/local/lib/python2.7/site-
 packages/django/utils/decorators.py" in _wrapped_view
   91. response = view_func(request, *args, **kwargs)
 File "/var/projects/instabot/env/local/lib/python2.7/site-
 packages/django/utils/decorators.py" in bound_func
   21. return func(self, *args2, **kwargs2)
 File "/var/projects/instabot/env/local/lib/python2.7/site-
 packages/django/db/transaction.py" in inner
   223. return func(*args, **kwargs)
 File "/var/projects/instabot/env/local/lib/python2.7/site-
 packages/django/contrib/admin/options.py" in change_view
   1108. self.log_change(request, new_object,
 change_message)
 File "/var/projects/instabot/env/local/lib/python2.7/site-
 packages/django/contrib/admin/options.py" in log_change
   546. change_message  = message
 File "/var/projects/instabot/env/local/lib/python2.7/site-
 packages/django/contrib/admin/models.py" in log_action
   19. e.save()
 File "/var/projects/instabot/env/local/lib/python2.7/site-
 packages/django/db/models/base.py" in save
   546.force_update=force_update,
 update_fields=update_fields)
 File "/var/projects/instabot/env/local/lib/python2.7/site-
 packages/django/db/models/base.py" in save_base
   650. result = manager._insert([self], fields=fields,
 return_id=update_pk, using=using, raw=raw)
 File "/var/projects/instabot/env/local/lib/python2.7/site-
 packages/django/db/models/manager.py" in _insert
   215. return insert_query(self.model, objs, fields, **kwargs)
 File "/var/projects/instabot/env/local/lib/python2.7/site-
 packages/django/db/models/query.py" in insert_query
   1673. return query.get_compiler(using=using).execute_sql(return_id)
 File "/var/projects/instabot/env/local/lib/python2.7/site-
 packages/django/db/models/sql/compiler.py" in execute_sql
   937. cursor.execute(sql, params)
 File "/var/projects/instabot/env/local/lib/python2.7/site-
 packages/django/db/backends/util.py" in execute
   41. return self.cursor.execute(sql, params)
 File "/var/projects/instabot/env/local/lib/python2.7/site-
 packages/django/db/backends/postgresql_psycopg2/base.py" in execute
   58. six.reraise(utils.DatabaseError,
 utils.DatabaseError(*tuple(e.args)), sys.exc_info()[2])
 File "/var/projects/instabot/env/local/lib/python2.7/s

[Django] #20260: Geodjango - ogrinspect on spatialite deprecation warning and unknown field type

[Django]

#20260: Geodjango - ogrinspect on spatialite deprecation warning and unknown 
field
type
---+---
 Reporter: |  Owner:  nobody
  burton449geo@…   | Status:  new
 Type: |Version:  1.5
  Uncategorized|   Keywords:  geodjango, spatialite, ogrinspect
Component:  GIS|  Has patch:  0
 Severity:  Normal |  UI/UX:  0
 Triage Stage: |
  Unreviewed   |
Easy pickings:  0  |
---+---
 I run ogrinspect on spatialite 4.0 where TM_WORLD_BORDERS-0.3.shp was
 loaded. I got two errors.

 This is the traceback:

 c:\mygeosite\geodjango>python manage.py ogrinspect
 c:/mygeosite/sqlite3/ezmappin
 g.sqlite test --srid=4326 --mapping --multi
 C:\python27\lib\site-packages\django\contrib\localflavor\__init__.py:2:
 Deprecat
 ionWarning: django.contrib.localflavor is deprecated. Use the separate
 django-lo
 calflavor-* packages instead.
   warnings.warn("django.contrib.localflavor is deprecated. Use the
 separate djan
 go-localflavor-* packages instead.", DeprecationWarning)

 TypeError: Unknown field type 
 in search_frame

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

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

Re: [Django] #20259: Syntax Error in the Document

[Django]

#20259: Syntax Error in the Document
-+-
 Reporter:  1458409827@… |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-
Changes (by me@…):

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


Comment:

 This was fixed in
 
https://github.com/django/django/commit/c3779d42142eb83eb8694177a12066261b3243aa

 Not sure why the PDF is outdated.

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

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

Re: [Django] #19028: Support GeoJSON output with SpatiaLite backend

[Django]

#19028: Support GeoJSON output with SpatiaLite backend
-+-
 Reporter:  bkg  |Owner:  bkg
 Type:  New feature  |   Status:  closed
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"9176fa70c1541d29d4d1865770d48b174e5dd968"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9176fa70c1541d29d4d1865770d48b174e5dd968"
 [1.5.x] Fixed geojson detection with Spatialite

 This is a partial backport of commit eb9430fc4be1. Without this,
 geojson support is never detected with Spatialite.
 Refs #20252 and #19028.
 }}}

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

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

Re: [Django] #20252: GeoDjango - GeoQuerySet.geojson NotImplementedError with Spatialite

[Django]

#20252: GeoDjango - GeoQuerySet.geojson NotImplementedError with Spatialite
-+-
 Reporter:  burton449geo@…   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5-rc-1
Component:  GIS  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  GeoDjango,   |  Needs documentation:  0
  Spatialite |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Claude Paroz ):

 In [changeset:"9176fa70c1541d29d4d1865770d48b174e5dd968"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9176fa70c1541d29d4d1865770d48b174e5dd968"
 [1.5.x] Fixed geojson detection with Spatialite

 This is a partial backport of commit eb9430fc4be1. Without this,
 geojson support is never detected with Spatialite.
 Refs #20252 and #19028.
 }}}

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

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

[django/django] 9176fa: [1.5.x] Fixed geojson detection with Spatialite

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 9176fa70c1541d29d4d1865770d48b174e5dd968
  
https://github.com/django/django/commit/9176fa70c1541d29d4d1865770d48b174e5dd968
  Author: Claude Paroz 
  Date:   2013-04-14 (Sun, 14 Apr 2013)

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

  Log Message:
  ---
  [1.5.x] Fixed geojson detection with Spatialite

This is a partial backport of commit eb9430fc4be1. Without this,
geojson support is never detected with Spatialite.
Refs #20252 and #19028.



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

Re: [Django] #18864: Django models __eq__ and __hash__ treat all unsaved model instances as identical

[Django]

#18864: Django models __eq__ and __hash__ treat all unsaved model instances as
identical
-+-
 Reporter:  fengb|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by bendavis78):

 * cc: bendavis78 (added)


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

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

Re: [Django] #20189: Collectstatic ignore list expansion on a per project basis

[Django]

#20189: Collectstatic ignore list expansion on a per project basis
-+-
 Reporter:  mark0978 |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.staticfiles  |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by tomask):

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


Comment:

 Hi,

 This is the file that the code is in
 
https://github.com/django/django/blob/master/django/contrib/staticfiles/management/commands/collectstatic.py

 This seems like a cool feature 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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20259: Syntax Error in the Document

[Django]

#20259: Syntax Error in the Document
--+
 Reporter:  1458409827@…  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.5
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  1
--+
 I found a mistake in the
 document(http://media.readthedocs.org/pdf/django/1.5.x/django.pdf), on
 page 486:
 "but in views written by hand you’ll need to explicitly use RequestContext
 To see how that works, and to read more details, check out Subclassing
 Context: RequestContext.", I think there should be a dot after "use
 RequestContext".

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

Re: [Django] #20254: startproject command - need better error message

[Django]

#20254: startproject command - need better error message
-+-
 Reporter:  dhivya23 |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Core (Management |  Version:  1.4
  commands)  |   Resolution:  needsinfo
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by tomask):

 Hi,

 I think this has been fixed in commit
 a9a0f0b03f9a02deb03617bf7e9773a307d1328f (django 1.4). The 'startproject'
 and 'startapp' commands are not disabled any more when specifying a
 settings module.

 {{{
 $ git diff a9a0f0b03f9a02deb03617bf7e9773a307d1328f
 20c8aa2a2029be50449b25122f85bbef0f2b957f django/core/man
 agement/__init__.py
 diff --git a/django/core/management/__init__.py
 b/django/core/management/__init__.py
 index 3672639..7e8eebd 100644
 --- a/django/core/management/__init__.py
 +++ b/django/core/management/__init__.py
 @@ -77,7 +77,9 @@ def get_commands():
  in that package are registered.

  Core commands are always included. If a settings module has been
 -specified, user-defined commands will also be included.
 +specified, user-defined commands will also be included, the
 +startproject command will be disabled, and the startapp command
 +will be modified to use the directory in which the settings module
 appears.

  The dictionary is in the format {command_name: app_name}. Key-value
  pairs from this dictionary can then be used in calls to
 }}}

 I hope this helps.

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

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

Re: [Django] #20183: "Making Queries" documentation assumes an Entry instance has already been created.

[Django]

#20183: "Making Queries" documentation assumes an Entry instance has already 
been
created.
-+-
 Reporter:  Katya|Owner:  nobody
   |   Status:  new
 Type:   |  Version:  1.5
  Cleanup/optimization   |   Resolution:
Component:  Documentation| Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by anonymous):

 * type:  Uncategorized => Cleanup/optimization


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

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

Re: [Django] #20258: "managed" attr of Model meta class losted during inheritance from abstract model

[Django]

#20258: "managed" attr of Model meta class losted during inheritance from 
abstract
model
-+-
 Reporter:  vsafronovich |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by vsafronovich):

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


Comment:

 more correct example code

 {{{
 class A(models.Model):
 class Meta:
 abstract = True
 managed = False

 class B(A):
 pass

 class C(A):
 class Meta:
 db_table = 'ccc'
 >>> B._meta.managed
 False
 >>> C._meta.managed
 True
 }}}

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

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

[Django] #20258: "managed" attr of Model meta class losted during inheritance from abstract model

[Django]

#20258: "managed" attr of Model meta class losted during inheritance from 
abstract
model
--+
 Reporter:  vsafronovich  |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 {{{
 class A(models.Model):
 class Meta:
 abstract = True
 managed = False

 class B(A):
 pass
 >>> B._meta.managed
 True
 }}}
 must be False.

 This needed for example for creating base model class for Models from
 legacy database.

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

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