Re: [Django] #11696: validate command in 1.1 hides errors in models that used to be shown

[Django]

#11696: validate command in 1.1 hides errors in models that used to be shown
+---
  Reporter:  martin maney   | Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  1 
Needs_better_patch:  0  |  
+---
Comment (by martin maney):

 Previous patch considered harmful.  It explodes if you have admindocs
 installed, as that app has no models.py.  My guess is that this would
 happen any time the import fails because there's no models.py to be found.

 Based on my current understanding of what's going on in import_module,
 this may be unfixable without extending the code brought back by time
 machine, as it fails to produce distinguishable results for the two cases
 (benign "just ain't no module here" and evil "the module failed to
 compile").  The old code could return the package containing "models"
 whether there was a "models" module or not; import_module raises
 ImportError for this (as well as when there's an actual compile error).

 ...okay, one last, bleary-eyed notion to try.

 Yeah, you can, just barely, distinguish the benign and evil failures, but
 it seems to require parsing the text of the exception __import__ throws -
 "No module named models" vs anything else.  Yuck.

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11358: Flatpage sitemap shows all pages, even private pages

[Django]

#11358: Flatpage sitemap shows all pages, even private pages
---+
  Reporter:  dburke| Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by dburke):

 Yeah, this solution is fine.  Should be made a little more explicit in the
 Documentation?  Or should we hope that google helps direct people seeking
 this solution here?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11659: Minor typo in 1.1 release notes

[Django]

#11659: Minor typo in 1.1 release notes
+---
  Reporter:  agabel | Owner:  agabel
Status:  assigned   | Milestone:
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:  typo  
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * keywords:  => typo
  * version:  1.1 => SVN
  * 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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11728: Documentation typo

[Django]

#11728: Documentation typo
+---
  Reporter:  Tommstein  | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:  typo  
 Stage:  Ready for checkin  | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * version:  1.1 => SVN
  * keywords:  => typo
  * needs_docs:  => 0
  * stage:  Unreviewed => 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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11741: PostgreSQL/PostGIS backend table quoting bug in nested queries

[Django]

#11741: PostgreSQL/PostGIS backend table quoting bug in nested queries
+---
  Reporter:  n...@urbanmapping.com  | Owner:  nobody
Status:  new| Milestone:
 Component:  GIS|   Version:  1.1   
Resolution: |  Keywords:  PostGIS Postgresql
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Alex):

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

Comment:

 The issue looks to be that the global quote_name shouldn't be use there,
 but instead Query.quote_name_unless_alias.

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  Alex   
  
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:|  Keywords:  multiple 
database feature
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Comment (by Alex):

 If you want to see the current state of work please use my branch in
 soc2009/multidb in the Django repository, right now my GitHub repo is
 undergoing severe code alterations that make it high unstable.

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  Alex   
  
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:|  Keywords:  multiple 
database feature
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Comment (by russellm):

 Replying to [comment:72 nicktank]:
 > Replying to [comment:66 alexkoshelev]:
 >  I've implemented this on a development version of django 1.1.
 ...
 > I apologize if this isn't the place to report this issue.  I am new
 around here and to django in general.

 Nick - as noted in comment 64, Multiple database connections was the
 subject of a 2009 Google Summer of Code project. Alex Gaynor has been
 developing the code to implement this. It's not a minor change - it
 requires lots of changes throughout Django.
 [http://github.com/alex/django/tree/multiple-db Check out Alex's GitHub
 repository] if you want to see the progress he has made. It isn't quite
 ready for trunk yet, but it's getting close, and it's sufficiently
 functional that you can try it out.

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11737: many2many recursive relationship do not work in DJ 1.1

[Django]

#11737: many2many recursive relationship do not work in DJ 1.1
+---
  Reporter:  simon_gray99   | Owner:  nobody 
Status:  closed | Milestone: 
 Component:  Uncategorized  |   Version:  1.1
Resolution:  worksforme |  Keywords:  many2many recursive
 Stage:  Unreviewed | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 I just tried this, and it works fine for me. There is also an extensive
 test suite of m2m relationships that covers this feature.

 I don't doubt you have found a problem, but it's not as simple as "the
 sample code doesn't work". Feel free to reopen if you can provide more
 context or debugging assistance.

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #11741: PostgreSQL/PostGIS backend table quoting bug in nested queries

[Django]

#11741: PostgreSQL/PostGIS backend table quoting bug in nested queries
---+
 Reporter:  n...@urbanmapping.com  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  GIS| Version:  1.1   
 Keywords:  PostGIS Postgresql |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 This issue occurs when using a spatial query as a subselect. The spatial
 predicate's table alias is quoted when it should not be.

 E.g.:
 {{{
 >>>
 MyGeoTable.objects.filter(geometry__intersects=geom).values_list('fid',
 flat=True).distinct().query.as_nested_sql()
 ('SELECT DISTINCT U0."ogc_fid" FROM "my_geo_table" U0 WHERE
 ST_Intersects("U0"."split", %s)',
 (,))

 }}}

 In the above ST_Intersects clause, the alias '''U0''' is quoted.  This
 happens here,I believe:
 
http://code.djangoproject.com/browser/django/trunk/django/contrib/gis/db/backend/postgis/query.py#L256

 I have not patched it yet, as I'm not clear yet how.

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #11740: ModelForm documentation not clear on default attributes of custom Fields

[Django]

#11740: ModelForm documentation not clear on default attributes of custom Fields
---+
 Reporter:  severian   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 The current documentation for ModelForm doesn't make clear that when you
 specify a custom field, default values for
 {{{required}}}, {{{initial}}}, etc. will not be drawn from the underlying
 model, as they are when you let the ModelForm create default fields. A
 patch is attached that explains this.

 As of this writing, the most straightforward example would involve a
 custom widget, but since a new paradigm for doing that is apparently about
 to be introduced ([http://code.djangoproject.com/ticket/9223]), I used an
 example with a custom field.

 A related discussion is here: [http://groups.google.com/group/django-
 developers/browse_thread/thread/904f0ec46525f922].

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9022: Allow US armed forces state codes for USStateField

[Django]

#9022: Allow US armed forces state codes for USStateField
+---
  Reporter:  Daniel Pope   | Owner:  
dougvanhorn
Status:  reopened   | Milestone:
 
 Component:  django.contrib.localflavor |   Version:  
1.0
Resolution: |  Keywords:
 
 Stage:  Design decision needed | Has_patch:  1 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Changes (by dougvanhorn):

 * cc: dougvanh...@gmail.com (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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9022: Allow US armed forces state codes for USStateField

[Django]

#9022: Allow US armed forces state codes for USStateField
+---
  Reporter:  Daniel Pope   | Owner:  
dougvanhorn
Status:  reopened   | Milestone:
 
 Component:  django.contrib.localflavor |   Version:  
1.0
Resolution: |  Keywords:
 
 Stage:  Design decision needed | Has_patch:  1 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Comment (by dougvanhorn):

 I'm adding a patch to this ticket that will add a USPSStateField to the US
 localflavor package.

 The USPostalCodeField will provide a model field and form fields which
 will validate USPS Postal Codes per
 [http://www.usps.com/ncsc/lookups/abbreviations.html].

 The patch includes regression test updated for forms and
 serializers_regress (though I'm unsure of what the serializers_regress
 tests are testing).

 ./runtests.py passes with 914 tests.

 I'm not sure this is the right design choice, but since there seems to be
 disagreement as to what constitutes a US State, I figured I'd add a field
 specifically for US Postal Codes.

 I'm not sure what this would mean to the USStateField, which, right now,
 is neither US States nor Postal Codes.

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11738: many2many recursive relationship do not work in DJ 1.1 - second problem

[Django]

#11738: many2many recursive relationship do not work in DJ 1.1 - second problem
---+
  Reporter:  simon_gray99  | Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  1.1
   
Resolution:|  Keywords:  many2many 
recursive missing tables
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Comment (by ubernostrum):

 `syncdb`, as documented, only does the initial table creation at the time
 you first define the model class. It does not make changes to your
 database later based on changes to models. Please consult the Django
 documentation for further details.

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11738: many2many recursive relationship do not work in DJ 1.1 - second problem

[Django]

#11738: many2many recursive relationship do not work in DJ 1.1 - second problem
---+
  Reporter:  simon_gray99  | Owner:  nobody 
   
Status:  closed| Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  1.1
   
Resolution:  invalid   |  Keywords:  many2many 
recursive missing tables
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

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

Comment:

 (closing as invalid now that it's clear this isn't a Django bug)

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11738: many2many recursive relationship do not work in DJ 1.1 - second problem

[Django]

#11738: many2many recursive relationship do not work in DJ 1.1 - second problem
---+
  Reporter:  simon_gray99  | Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  1.1
   
Resolution:|  Keywords:  many2many 
recursive missing tables
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Comment (by simon_gray99):

 I think I may have found the problem... despite me changing my model,
 running 'manage.py syncdb' is refusing to notice the model has changed and
 is therefore not creating the tables.

 Currently my application is laid out as follows:

 {{{
 /idj/models.py
 /djsite/...
 }}}

 It appears to be missing the 'models.py'. file completely and failing
 silently despite the fact that 'manage.py runserver' works perfectly

 There is some inconsistency here... perhaps someone can explain?

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11738: many2many recursive relationship do not work in DJ 1.1 - second problem

[Django]

#11738: many2many recursive relationship do not work in DJ 1.1 - second problem
---+
  Reporter:  simon_gray99  | Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  1.1
   
Resolution:|  Keywords:  many2many 
recursive missing tables
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Comment (by simon_gray99):

 I think I may have found the problem... despite me changing my model,
 running 'manage.py syncdb' is refusing to notice the model has changed
 and is therefore not creating the tables.

 Currently my application is laid out as follows
 /idj/models.py
 /djsite/...

 It appears to be missing the 'models.p'. file completely and failing
 silently
 despite the fact that 'manage.py runserver' works perfectly

 There is some inconsistency here... perhaps someone can explain?

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #2713: Sitemap Index with Cache gives a NoReverseMatch exception

[Django]

#2713: Sitemap Index with Cache gives a NoReverseMatch exception
-+--
  Reporter:  JayKlehr| Owner:  adrian
Status:  reopened| Milestone:
 Component:  Contrib apps|   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by stavros):

  * has_patch:  0 => 1

Comment:

 I have submitted a patch that checks for the normal view and falls back on
 a "contrib.sitemaps.sitemap" named view if there's an error. This fixes
 the problem and allows caching.

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11738: many2many recursive relationship do not work in DJ 1.1 - second problem

[Django]

#11738: many2many recursive relationship do not work in DJ 1.1 - second problem
---+
  Reporter:  simon_gray99  | Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  1.1
   
Resolution:|  Keywords:  many2many 
recursive missing tables
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by simon_gray99):

  * component:  Uncategorized => Database layer (models, ORM)

Comment:

 here is the full traceback from my machine at home:

 {{{
 In [1]: from isuite.models import Person

 In [2]: a = Person(name='Anne')

 In [3]: a.save()
 ---
 ProgrammingError  Traceback (most recent call
 last)

 /Volumes/home/Users/simon/isuite/ in ()

 /Library/Python/2.5/site-packages/django/db/models/base.pyc in save(self,
 force_insert, force_update)
 408 raise ValueError("Cannot force both insert and
 updating in "
 409 "model saving.")
 --> 410 self.save_base(force_insert=force_insert,
 force_update=force_update)
 411
 412 save.alters_data = True

 /Library/Python/2.5/site-packages/django/db/models/base.pyc in
 save_base(self, raw, cls, origin, force_insert, force_update)
 493 if values:
 494 # Create a new record.
 --> 495 result = manager._insert(values,
 return_id=update_pk)
 496 else:
 497 # Create a new record with defaults for
 everything.

 /Library/Python/2.5/site-packages/django/db/models/manager.pyc in
 _insert(self, values, **kwargs)
 175
 176 def _insert(self, values, **kwargs):
 --> 177 return insert_query(self.model, values, **kwargs)
 178
 179 def _update(self, values, **kwargs):

 /Library/Python/2.5/site-packages/django/db/models/query.pyc in
 insert_query(model, values, return_id, raw_values)
1083 part of the public API.
1084 """
1085 query = sql.InsertQuery(model, connection)
1086 query.insert_values(values, raw_values)
 -> 1087 return query.execute_sql(return_id)

 /Library/Python/2.5/site-packages/django/db/models/sql/subqueries.pyc in
 execute_sql(self, return_id)
 318 def execute_sql(self, return_id=False):
 319 self.return_id = return_id
 --> 320 cursor = super(InsertQuery, self).execute_sql(None)
 321 if not (return_id and cursor):
 322 return

 /Library/Python/2.5/site-packages/django/db/models/sql/query.pyc in
 execute_sql(self, result_type)
2367 return
2368 cursor = self.connection.cursor()
 -> 2369 cursor.execute(sql, params)
2370
2371 if not result_type:

 /Library/Python/2.5/site-packages/django/db/backends/util.pyc in
 execute(self, sql, params)
  17 start = time()
  18 try:
 ---> 19 return self.cursor.execute(sql, params)
  20 finally:
  21 stop = time()

 ProgrammingError: relation "isuite_person" does not exist

 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11739: ContentFile() does not support unicode data

[Django]

#11739: ContentFile() does not support unicode data
---+
  Reporter:  adamnelson| Owner:  nobody
Status:  new   | Milestone:
 Component:  File uploads/storage  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by adamnelson):

  * needs_better_patch:  => 0
  * version:  1.0 => 1.1
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Tried on 1.1 as well and also a 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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #11739: ContentFile() does not support unicode data

[Django]

#11739: ContentFile() does not support unicode data
--+-
 Reporter:  adamnelson|   Owner:  nobody
   Status:  new   |   Milestone:
Component:  File uploads/storage  | Version:  1.0   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 It's not clear to me where exactly this is a bug but it's certainly a
 problem.  This example is for a model PageDisplay with a FileField named
 'content':

 {{{
 >>> pager = PageDisplay.objects.get(id=4)
 >>> pager
 http://debtshed.com:/>
 >>> pager.content
 
 >>> from django.core.files.base import ContentFile
 >>> pager.content.save('tester.html',ContentFile('test1'))
 >>> pager.content.read()
 'test1'
 >>> pager.content.save('tester.html',ContentFile(u'test1'))
 >>> pager.content.read()
 't\x00e\x00s\x00t\x001\x00'

 }}}

 I'm not sure if this is working on the save and not the read or vice versa
 but I presume that the unicode translation should be symmetrical.

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11738: many2many recursive relationship do not work in DJ 1.1 - second problem

[Django]

#11738: many2many recursive relationship do not work in DJ 1.1 - second problem
+---
  Reporter:  simon_gray99   | Owner:  nobody

Status:  new| Milestone:

 Component:  Uncategorized  |   Version:  1.1   

Resolution: |  Keywords:  many2many recursive 
missing tables
 Stage:  Unreviewed | Has_patch:  0 

Needs_docs:  0  |   Needs_tests:  0 

Needs_better_patch:  0  |  
+---
Old description:

> According to the page at:
> http://www.djangoproject.com/documentation/models/m2m_recursive/
>
> All that is required to produce a recursive many2many is the following
> code:
> from django.db import models
>
> class Person(models.Model):
> name = models.CharField(max_length=20)
> friends = models.ManyToManyField('self')
> idols = models.ManyToManyField('self', symmetrical=False,
> related_name='stalkers')
>
> def __unicode__(self):
> return self.name
>
> When I try this exact same code in my application,
>
> I get an immediate complaint that the table 'persons_idols' does not
> exist.
>
> If I CREATE this table manually then things are OK but the documentation
> state that DJ is supposed to handle creating this
> table when the 'through' flag is NOT used... it doesn't!
>
> Please advise

New description:

 According to the page at:
 http://www.djangoproject.com/documentation/models/m2m_recursive/

 All that is required to produce a recursive many2many is the following
 code:
 {{{
 from django.db import models

 class Person(models.Model):
 name = models.CharField(max_length=20)
 friends = models.ManyToManyField('self')
 idols = models.ManyToManyField('self', symmetrical=False,
 related_name='stalkers')

 def __unicode__(self):
 return self.name
 }}}
 When I try this exact same code in my application,

 I get an immediate complaint that the table 'persons_idols' does not
 exist.

 If I CREATE this table manually then things are OK but the documentation
 state that DJ is supposed to handle creating this
 table when the 'through' flag is NOT used... it doesn't!

 Please advise

Comment (by Alex):

 Please use the preview button.

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11737: many2many recursive relationship do not work in DJ 1.1

[Django]

#11737: many2many recursive relationship do not work in DJ 1.1
+---
  Reporter:  simon_gray99   | Owner:  nobody 
Status:  new| Milestone: 
 Component:  Uncategorized  |   Version:  1.1
Resolution: |  Keywords:  many2many recursive
 Stage:  Unreviewed | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by Alex):

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

Old description:

> from the page at:
>
> http://docs.djangoproject.com/en/dev/ref/models/fields/#recursive-
> relationships
>
> the sample code does not work:
>
> >>> from django.db import models
> >>> class Person(models.Model):
> ... name = models.CharField(max_length=20)
> ... friends = models.ManyToManyField('self')
> ... idols = models.ManyToManyField('self', symmetrical=False,
> related_name=
> 'stalkers')
> ... def __unicode__(self):
> ... return self.name
> ...
> Traceback (most recent call last):
>   File "", line 1, in 
>   File "/usr/lib/python2.5/site-packages/django/db/models/base.py", line
> 51, in __new__
> kwargs = {"app_label": model_module.__name__.split('.')[-2]}
> IndexError: list index out of range
> >>>

New description:

 from the page at:

 http://docs.djangoproject.com/en/dev/ref/models/fields/#recursive-
 relationships

 the sample code does not work:
 {{{
 >>> from django.db import models
 >>> class Person(models.Model):
 ... name = models.CharField(max_length=20)
 ... friends = models.ManyToManyField('self')
 ... idols = models.ManyToManyField('self', symmetrical=False,
 related_name='stalkers')
 ... def __unicode__(self):
 ... return self.name
 ...
 Traceback (most recent call last):
   File "", line 1, in 
   File "/usr/lib/python2.5/site-packages/django/db/models/base.py", line
 51, in __new__
 kwargs = {"app_label": model_module.__name__.split('.')[-2]}
 IndexError: list index out of range
 >>>
 }}}

Comment:

 Please use the preview button.

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11696: validate command in 1.1 hides errors in models that used to be shown

[Django]

#11696: validate command in 1.1 hides errors in models that used to be shown
+---
  Reporter:  martin maney   | Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  1 
Needs_better_patch:  0  |  
+---
Changes (by martin maney):

  * has_patch:  0 => 1
  * needs_tests:  0 => 1

Comment:

 Looks simple enough.  At a guess the try/except wrapper was thrown
 together to satisfy the case where it could be postponed and error
 reporting was simply not considered.  This works for me in a small test
 case (validates OK with a small existing app, get the traceback when I
 inject a misspelt field type name).  Unless there's some subtle problem
 with the postponing business, I think this will do.
 {{{
 try:
 models = import_module('.models', app_name)
 except ImportError, e:
 self.nesting_level -= 1
 if can_postpone:
 # Either the app has no models, or the package is still
 being
 # imported by Python and the model module isn't available
 yet.
 # We will check again once all the recursion has finished
 (in
 # populate).
 self.postponed.append(app_name)
 return None
 raise e
 self.nesting_level -= 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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #2713: Sitemap Index with Cache gives a NoReverseMatch exception

[Django]

#2713: Sitemap Index with Cache gives a NoReverseMatch exception
-+--
  Reporter:  JayKlehr| Owner:  adrian
Status:  reopened| Milestone:
 Component:  Contrib apps|   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by stavros):

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

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #2713: Sitemap Index with Cache gives a NoReverseMatch exception

[Django]

#2713: Sitemap Index with Cache gives a NoReverseMatch exception
-+--
  Reporter:  JayKlehr| Owner:  adrian
Status:  closed  | Milestone:
 Component:  Contrib apps|   Version:  SVN   
Resolution:  fixed   |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by stavros):

 I can confirm that this doesn't work. How about making a named view
 mandatory for the sitemap, such as "contrib.sitemap.index" and
 "contrib.sitemap.sitemap"?

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11738: many2many recursive relationship do not work in DJ 1.1 - second problem

[Django]

#11738: many2many recursive relationship do not work in DJ 1.1 - second problem
+---
  Reporter:  simon_gray99   | Owner:  nobody

Status:  new| Milestone:

 Component:  Uncategorized  |   Version:  1.1   

Resolution: |  Keywords:  many2many recursive 
missing tables
 Stage:  Unreviewed | Has_patch:  0 

Needs_docs:  0  |   Needs_tests:  0 

Needs_better_patch:  0  |  
+---
Changes (by simon_gray99):

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

Comment:

 In addition, if I CREATE the table needed in my model (in this case
 'persons_idols')
 then I am unable to create a test database with the following error:

 {{{
 Error: Error: idj couldn't be reset. Possible reasons:
   * The database isn't running or isn't configured correctly.
   * At least one of the database tables doesn't exist.
   * The SQL was invalid.
 Hint: Look at the output of 'django-admin.py sqlreset idj'. That's the SQL
 this command wasn't able to run.
 The full error: relation "persons_idols" does not exist

 }}}

 even although I had created the table. Examining the SQL in more detail, I
 find that it is trying to DROP the table before it has created it... and
 therefore failing, of course. WTF?

 So it seems like either I have to create the tables by hand in order to
 get the model to work, and give up automated testing,
 or I have to skip recursive many2many links completely and somehow find
 another way through... :(

 Please can someone point me in an effective direction for a solution?

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #11738: many2many recursive relationship do not work in DJ 1.1 - second problem

[Django]

#11738: many2many recursive relationship do not work in DJ 1.1 - second problem
+---
 Reporter:  simon_gray99|   Owner:  nobody
   Status:  new |   Milestone:
Component:  Uncategorized   | Version:  1.1   
 Keywords:  many2many recursive missing tables  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 According to the page at:
 http://www.djangoproject.com/documentation/models/m2m_recursive/

 All that is required to produce a recursive many2many is the following
 code:
 from django.db import models

 class Person(models.Model):
 name = models.CharField(max_length=20)
 friends = models.ManyToManyField('self')
 idols = models.ManyToManyField('self', symmetrical=False,
 related_name='stalkers')

 def __unicode__(self):
 return self.name

 When I try this exact same code in my application,

 I get an immediate complaint that the table 'persons_idols' does not
 exist.

 If I CREATE this table manually then things are OK but the documentation
 state that DJ is supposed to handle creating this
 table when the 'through' flag is NOT used... it doesn't!

 Please advise

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #11737: many2many recursive relationship do not work in DJ 1.1

[Django]

#11737: many2many recursive relationship do not work in DJ 1.1
-+--
 Reporter:  simon_gray99 |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Uncategorized| Version:  1.1   
 Keywords:  many2many recursive  |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 from the page at:

 http://docs.djangoproject.com/en/dev/ref/models/fields/#recursive-
 relationships

 the sample code does not work:

 >>> from django.db import models
 >>> class Person(models.Model):
 ... name = models.CharField(max_length=20)
 ... friends = models.ManyToManyField('self')
 ... idols = models.ManyToManyField('self', symmetrical=False,
 related_name=
 'stalkers')
 ... def __unicode__(self):
 ... return self.name
 ...
 Traceback (most recent call last):
   File "", line 1, in 
   File "/usr/lib/python2.5/site-packages/django/db/models/base.py", line
 51, in __new__
 kwargs = {"app_label": model_module.__name__.split('.')[-2]}
 IndexError: list index out of range
 >>>

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #10907: Adding google news sitemap support to django.contrib.sitemaps

[Django]

#10907: Adding google news sitemap support to django.contrib.sitemaps
-+--
  Reporter:  lakinwecker | Owner:  lakinwecker
Status:  assigned| Milestone: 
 Component:  Contrib apps|   Version:  1.0
Resolution:  |  Keywords: 
 Stage:  Design decision needed  | Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Comment (by ChrisL):

 Ticket patch not updated.

 I'm implementing this patch and can see the  content is
 still in place. Should read:

 {% if url.keywords %}
 {% for keyword in keywords %}{{ url.keyword }}{% if not
 forloop.last %}, {% endif %}{% endfor %}
 news:keywords>{% endif %}

 can't get the news sitemap content to pass through to the template
 correctly, likely this was part of the bugs that were cleaned up?

 Please post the up to date 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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  Alex   
  
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:|  Keywords:  multiple 
database feature
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Comment (by nicktank):

 Replying to [comment:66 alexkoshelev]:
  I've implemented this on a development version of django 1.1.  It appears
 as though it appends the table name of the app in the database established
 in the project settings instead of adding the model's tables to the
 declared database
 {{{

 from django.db import models
 from django.blocks.apps.core.managers import MultiDBManager

 class FireMap(models.Model):
 address = models.CharField(max_length=100)
 city = models.CharField(max_length=50)
 zip = models.IntegerField()
 latitude = models.DecimalField(max_digits=17, decimal_places=14)
 longitude = models.DecimalField(max_digits=17, decimal_places=14)
 neighborhood = models.CharField(max_length=30)
 assesorID = models.IntegerField()
 assessorURL = models.URLField()
 homeValue = models.CommaSeparatedIntegerField(max_length=8)
 homeOwner = models.CharField (max_length=30)
 mainIMGURL = models.URLField()
 photos = models.CommaSeparatedIntegerField(max_length=40)
 articleID1 = models.IntegerField()
 articleID2 = models.IntegerField()
 articleID3 = models.IntegerField()
 extrainfo = models.TextField()

 objects = MultiDBManager()

 def __str__(self):
 return self.name

 class Meta:
 db_name = 'firemap'
 }}}

 the setting for the Db in my project settings file is set to:

 {{{

 DATABASE_ENGINE = 'postgresql_psycopg2'   # 'postgresql_psycopg2',
 'postgresql', 'mysql', 'sqlite3' or 'oracle'.
 DATABASE_NAME = 'newsok' # Or path to database file if using
 sqlite3.

 }}}

 When the tables are created I see in the newsok Db a firemap_firemap table
 (firemap is the name of the app as well) but there is nothing in the
 actual firemap Db.

 I apologize if this isn't the place to report this issue.  I am new around
 here and to django in general.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11736: title tag - put 'Django |' to the end

[Django]

#11736: title tag - put 'Django |' to the end
---+
  Reporter:  ris...@gmail.com  | Owner:  nobody
Status:  closed| Milestone:
 Component:  Django Web site   |   Version:  1.1   
Resolution:  duplicate |  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by ubernostrum):

 Seeing as this is something that's been brought up again and again, and
 the decision and rationale are easily spotted, I'll once again throw out a
 reminder: please search existing tickets before filing new ones.

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11736: title tag - put 'Django |' to the end

[Django]

#11736: title tag - put 'Django |' to the end
---+
  Reporter:  ris...@gmail.com  | Owner:  nobody
Status:  closed| Milestone:
 Component:  Django Web site   |   Version:  1.1   
Resolution:  duplicate |  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 Duplicate of #10209 and #1380.

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11736: title tag - put 'Django |' to the end

[Django]

#11736: title tag - put 'Django |' to the end
---+
  Reporter:  ris...@gmail.com  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Django Web site   |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

  * needs_better_patch:  => 0
  * component:  Uncategorized => Django Web site
  * needs_tests:  => 0
  * needs_docs:  => 0

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #11736: title tag - put 'Django |' to the end

[Django]

#11736: title tag - put 'Django |' to the end
--+-
 Reporter:  ris...@gmail.com  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Uncategorized | Version:  1.1   
 Keywords:|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 Change

 {{{ Django | {% block title %}The Web framework for perfectionists
 with deadlines{% endblock %}  }}}

 to

 {{{ {% block title %}The Web framework for perfectionists with
 deadlines{% endblock %} | Django }}}

 Main reason for this that in current state it's pretty hard to find the
 tab you are looking for. If you have multiple tabs open all you can see is
 'Django | D...' or 'Django | T...' and it's impossible to distinguish
 between them.

 Second reason is SEO, as it's far better to have brand or so at the end of
 title.

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #11735: Wrong documentation for changing Model formsets queryset

[Django]

#11735: Wrong documentation for changing Model formsets queryset
---+
 Reporter:  claudep|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 In the documentation, we can read that a Model Formset queryset can be
 changed with the following code:
 {{{
 class BaseAuthorFormSet(BaseModelFormSet):
 def __init__(self, *args, **kwargs):
 self.queryset = Author.objects.filter(name__startswith='O')
 super(BaseAuthorFormSet, self).__init__(*args, **kwargs)
 }}}
 See http://docs.djangoproject.com/en/dev/topics/forms/modelforms
 /#changing-the-queryset

 This doesn't work. The problem is that in the {{{__init__}}} function of
 BaseModelFormSet, the queryset is redefined from the queryset parameter
 which default to None.
 See
 http://code.djangoproject.com/browser/django/trunk/django/forms/models.py#L448

 To make it work, the queryset should be added to the {{{__init__}}} call
 as a keyword parameter. Or it might also be a bug in the {{{__init__}}}
 function where it should test if self.queryset is not None before
 assigning to it. Either in docs, either in code, I think there is
 something to solve.

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11068: Wrong language code for Norwegian (Bokmål)

[Django]

#11068: Wrong language code for Norwegian (Bokmål)
---+
  Reporter:  nfg   | Owner:  garcia_marc

Status:  reopened  | Milestone: 

 Component:  Internationalization  |   Version:  SVN

Resolution:|  Keywords:  language_code 
norwegian
 Stage:  Fixed on a branch | Has_patch:  0  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  0 |  
---+
Changes (by garcia_marc):

  * status:  closed => reopened
  * resolution:  fixed =>
  * stage:  Unreviewed => Fixed on a branch

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11715: If change mutable list "inlines" in one admin options then it will change "inlines" for all admin options.

[Django]

#11715: If change mutable list "inlines" in one admin options then it will 
change
"inlines" for all admin options.
---+
  Reporter:  aiv   | Owner:  nobody 
  
Status:  new   | Milestone: 
  
 Component:  django.contrib.admin  |   Version:  1.1
  
Resolution:|  Keywords:  inlines admin 
options
 Stage:  Unreviewed| Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by summerisgone):

 * cc: summer.is.g...@gmail.com (added)
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #5390: Add signals to ManyRelatedManager

[Django]

#5390: Add signals to ManyRelatedManager
--+-
  Reporter:  Ludovico Magnocavallo   | Owner:  
rvdrijst   
Status:  assigned | Milestone:  
   
 Component:  Database layer (models, ORM) |   Version:  SVN 
   
Resolution:   |  Keywords:  
manytomanyfield feature signals
 Stage:  Design decision needed   | Has_patch:  1   
   
Needs_docs:  0|   Needs_tests:  0   
   
Needs_better_patch:  0|  
--+-
Changes (by aom):

 * cc: aom (added)

Comment:

 Replying to [comment:24 ubernostrum]:
 > If you're really interested in getting a feature into Django, it's in
 your best interest to get involved on the developers' list and pay
 attention to the release schedule.

 +1 it's not a feature, it's a bug fix.

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #342: Add a way for fields to be displayed in the admin without being editable

[Django]

#342: Add a way for fields to be displayed in the admin without being editable
---+
  Reporter:  Bless | Owner:  nobody
Status:  reopened  | Milestone:  1.2   
 Component:  django.contrib.admin  |   Version:  newforms-admin
Resolution:|  Keywords:  djangocon 
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

 * cc: rlaa...@wiktel.com (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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11358: Flatpage sitemap shows all pages, even private pages

[Django]

#11358: Flatpage sitemap shows all pages, even private pages
---+
  Reporter:  dburke| Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by kmpm):

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

Comment:

 You almost answered it yourself.
 I don't know if its worth doing a modification to sitemaps just for this.
 Save your class but with another name like "FlatPagePublicSitemap" in a
 file called "sitemaps.py" for example.
 Include ( from sitemaps include FlatPagePublicSitemap ) and use that class
 in your urls.py instead of the ordinary FlagPageSitemap.

 Is that a good enough solution for you?

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---