Re: [Django] #15149: Memcached backend: possible issue with cache keys

[Django]

#15149: Memcached backend: possible issue with cache keys
--+-
   Reporter:  jeff@…  | Owner:  nobody   
 Status:  new | Milestone:   
  Component:  Cache system|   Version:  SVN  
 Resolution:  |  Keywords:  memcached
   Triage Stage:  Unreviewed  | Has patch:  0
Needs documentation:  0   |   Needs tests:  0
Patch needs improvement:  0   |  
--+-

Comment (by russellm):

 The fact that the set debug isn't being printed is *very* suspect. When
 combined with the fact that the set() calls are evidently calling the
 caching functions without any prefixes, it suggests that some old caching
 code is being invoked for some reason.

 Could you try purging all the .pyc files from your django directory, and
 rerun the tests. I have no idea how you'd be getting half an updated class
 (updated gets, but not sets), but it's worth a try.

 Failing that - Do you get the same results if:

  * You use get_cache() directly, instead of the default cache object.
 i.e.:
 {{{
 from django.core.cache import get_cache
 mycache = get_cache('default')
 mycache.get('testing_yo')
 ...
 }}}

  * You use a manually instantiated cache object:
 {{{
 from django.core.cache.backends.memcached.MemcachedCache
 mycache = MemcachedCache('127.0.0.1:11211', KEY_PREFIX='lendle_')
 mycache.get('testing_yo')
 ...
 }}}

-- 
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] #15184: Error when subclassing models.ForeignKey field

[Django]

#15184: Error when subclassing models.ForeignKey field
+---
   Reporter:  rupa108   | Owner:  
nobody 
 Status:  reopened  | Milestone:
 
  Component:  Database layer (models, ORM)  |   Version:  SVN   
 
 Resolution:|  Keywords:  
ForeignKey, models, subclassing
   Triage Stage:  Accepted  | Has patch:  0 
 
Needs documentation:  0 |   Needs tests:  0 
 
Patch needs improvement:  0 |  
+---
Changes (by russellm):

  * stage:  Unreviewed => Accepted


Comment:

 Ok - I'm going to mark this accepted -- line 96 of subclassing.py looks
 like it should be field.attname, not field.name. There may be other
 problems involved with subclassing ForeignKey that follow on from that
 fix; that will require some additional investigation.

 However, I would make two comments:

  1. When reporting a bug, you need to give us *all* the information you
 have, not just the bits you want to give us. Nowhere in your mailing list
 posts or in this ticket did you mention that you were using to_python.
 That's a pretty important detail for anybody that wants to reproduce the
 problem. Remember, if we can't reproduce your problem, the problem
 effectively doesn't exist.

  2. The reason you've found this bug is that you are almost certainly
 Doing It Wrong (tm). Your model layer shouldn't care whether it's being
 used for AJAX or not. A foreign key is a pointer to another model. The
 "value" for that model is something that uniquely references another
 object. A primary key value (or, by proxy, a Django object that
 encapsulates that primary key value) is the most sensible representation
 of that value. The need to be "AJAXified" is a display level concern. AJAX
 rendering considerations should be in your forms/templating layer, not
 your data model.

-- 
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] #15179: django.test.client.Client.login fake HttpRequest is not run through middlewares

[Django]

#15179: django.test.client.Client.login fake HttpRequest is not run through
middlewares
-+--
   Reporter:  Ciantic| Owner:  nobody
 Status:  new| Milestone:  1.3   
  Component:  Testing framework  |   Version:  SVN   
 Resolution: |  Keywords:
   Triage Stage:  Accepted   | Has patch:  1 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  1  |  
-+--
Changes (by russellm):

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


Comment:

 Accepting the use case. However, the patch needs some work.

  * The patch should note that the reference to "/login" is arbitrary --
 it's not actually using /login, it's just using that URL as a dummy
 location.
  * The test case isn't particularly good - it's checking a test condition
 that is a composite of multiple features. You should be checking that
 request has an attribute called "middlewares", and that the value is
 "+middlewares'. Checking a comparison of concatenated strings is just
 confusing the issue.
  * The test case should be integrated with Django's test suite (the
 test_client_regress tests would be a good location).

-- 
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] #15168: feature request - New setting

[Django]

#15168: feature request - New setting
+---
   Reporter:  zay2  | Owner:  nobody
 Status:  closed| Milestone:  1.3   
  Component:  Internationalization  |   Version:  SVN   
 Resolution:  wontfix   |  Keywords:
   Triage Stage:  Unreviewed| Has patch:  0 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by russellm):

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


Comment:

 Its unclear why a new setting is required here.

 HTTP Header based language detection is performed by the Locale
 middleware; if you don't want the behavior that is implemented... don't
 use that middleware. Just remove it, or provide a different middleware.

 If you're referring to a different piece of code, you'll need to provide
 more specific details than "that part of the code". Regardless, this
 doesn't seem to me like something that should be handled as a setting.

-- 
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] #15187: CommonMiddleware should only send broken link emails if DEBUG is False

[Django]

#15187: CommonMiddleware should only send broken link emails if DEBUG is False
-+--
   Reporter:  dancarroll | Owner:  dancarroll   
 Status:  assigned   | Milestone:   
  Component:  Core framework |   Version:  1.2  
 Resolution: |  Keywords:  common middleware
   Triage Stage:  Ready for checkin  | Has patch:  1
Needs documentation:  0  |   Needs tests:  0
Patch needs improvement:  0  |  
-+--
Changes (by russellm):

  * stage:  Unreviewed => Ready for checkin


Comment:

 Low impact isn't really the measure here -- regardless of impact, every
 change *could* regress behavior, so it should be tested.

 However, in this case, the behavior is something that is difficult to
 accurately test for regression, because debug is turned off for testing
 purposes. *That* is a good reason to accept the patch without a test.

-- 
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] #15188: ellipsizing fields in list_display in admin

[Django]

#15188: ellipsizing fields in list_display in admin
+---
   Reporter:  bjourne   | Owner:  nobody
 Status:  new   | Milestone:
  Component:  django.contrib.admin  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  0 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by russellm):

  * needs_better_patch:  => 0
  * needs_docs:  => 0
  * needs_tests:  => 0
  * stage:  Unreviewed => Accepted


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #15189: django 1.2 docs claim auth login and logout signals

[Django]

#15189: django 1.2 docs claim auth login and logout signals
-+--
   Reporter:  roderyc@…  | Owner:  nobody
 Status:  closed | Milestone:
  Component:  Documentation  |   Version:  1.2   
 Resolution:  duplicate  |  Keywords:
   Triage Stage:  Unreviewed | Has patch:  0 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by russellm):

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


Comment:

 Closing as a duplicate -- Agreed that it looks like a server update issue;
 whatever will fix #15192 will fix this too.

-- 
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] #15191: Minor grammar fix in form validation docs

[Django]

#15191: Minor grammar fix in form validation docs
-+--
   Reporter:  berto  | Owner:  nobody
 Status:  new| Milestone:
  Component:  Documentation  |   Version:  1.2   
 Resolution: |  Keywords:
   Triage Stage:  Accepted   | Has patch:  1 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by russellm):

  * component:  Uncategorized => Documentation
  * stage:  Unreviewed => Accepted


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #15193: string indices must be integers, not str during YAML deserialization

[Django]

#15193: string indices must be integers, not str during YAML deserialization
--+-
   Reporter:  Jack| Owner:  nobody
 Status:  closed  | Milestone:
  Component:  Core framework  |   Version:  1.2   
 Resolution:  invalid |  Keywords:
   Triage Stage:  Unreviewed  | Has patch:  0 
Needs documentation:  0   |   Needs tests:  0 
Patch needs improvement:  0   |  
--+-
Changes (by russellm):

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


Old description:

> Traceback:
> Problem installing fixture 'data\init.yaml': Traceback (most recent call
> last):
>   File "C:\Python26\lib\site-
> packages\django\core\management\commands\loaddata.p
> y", line 169, in handle
> for obj in objects:
>   File "C:\Python26\lib\site-packages\django\core\serializers\pyyaml.py",
> line 5
> 9, in Deserializer
> for obj in PythonDeserializer(objs, **options):
>   File "C:\Python26\lib\site-packages\django\core\serializers\python.py",
> line 8
> 4, in Deserializer
> Model = _get_model(d["model"])
> TypeError: string indices must be integers, not str
>
> I made the following change to pyyaml.py and it fixed the problem:
> {{{
> def Deserializer(stream_or_string, **options):
> """
> Deserialize a stream or string of YAML data.
> """
> if isinstance(stream_or_string, basestring):
> stream = StringIO(stream_or_string)
> else:
> stream = stream_or_string
> for obj in PythonDeserializer('''[yaml.load(stream),]''', **options):
> yield obj
> }}}
> I'm running Windows XP SP3 with this version of pyyaml:
>
> http://pyyaml.org/download/pyyaml/PyYAML-3.09.win32-py2.6.exe

New description:

 {{{
 Traceback:
 Problem installing fixture 'data\init.yaml': Traceback (most recent call
 last):
   File "C:\Python26\lib\site-
 packages\django\core\management\commands\loaddata.p
 y", line 169, in handle
 for obj in objects:
   File "C:\Python26\lib\site-packages\django\core\serializers\pyyaml.py",
 line 5
 9, in Deserializer
 for obj in PythonDeserializer(objs, **options):
   File "C:\Python26\lib\site-packages\django\core\serializers\python.py",
 line 8
 4, in Deserializer
 Model = _get_model(d["model"])
 TypeError: string indices must be integers, not str
 }}}

 I made the following change to pyyaml.py and it fixed the problem:
 {{{
 def Deserializer(stream_or_string, **options):
 """
 Deserialize a stream or string of YAML data.
 """
 if isinstance(stream_or_string, basestring):
 stream = StringIO(stream_or_string)
 else:
 stream = stream_or_string
 for obj in PythonDeserializer(yaml.load(stream), **options):
 yield obj
 }}}
 I'm running Windows XP SP3 with this version of pyyaml:

 http://pyyaml.org/download/pyyaml/PyYAML-3.09.win32-py2.6.exe

--

Comment:

 Marking invalid -- report doesn't give any indication of *why* the
 proposed change is required, other than apparent abiility of the reporter
 to generate a stack trace.

 In order for a bug report to be useful, you need to give us the ability to
 reproduce a problem. That means a complete set of instructions that would
 allow someone else to reproduce the problem.

 If you care to provide such instructions, please repoen this ticket with
 those 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] #15180: reverse doesn't check default_args

[Django]

#15180: reverse doesn't check default_args
--+-
   Reporter:  olaf| Owner:  nobody  
 Status:  new | Milestone:  1.3 
  Component:  Core framework  |   Version:  1.3-beta
 Resolution:  |  Keywords:  resolve default_args
   Triage Stage:  Accepted| Has patch:  1   
Needs documentation:  0   |   Needs tests:  1   
Patch needs improvement:  0   |  
--+-

Comment (by russellm):

 I have a background suspicion that this will cause all sorts of havoc with
 existing URL lookups -- for example, existing views with default arguments
 that *aren't* using the default arguments to differentiate between views.

 However, since the patch doesn't have any tests, I can't verify this
 quickly.

 Marking this as a qualified accepted, the qualification being that the
 implementation *must* be backwards compatible with existing uses, and be
 tested as such. If that can't be achieved, then we'll need to close
 wontfix.

-- 
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] #15180: reverse doesn't check default_args

[Django]

#15180: reverse doesn't check default_args
--+-
   Reporter:  olaf| Owner:  nobody  
 Status:  new | Milestone:  1.3 
  Component:  Core framework  |   Version:  1.3-beta
 Resolution:  |  Keywords:  resolve default_args
   Triage Stage:  Accepted| Has patch:  1   
Needs documentation:  0   |   Needs tests:  1   
Patch needs improvement:  0   |  
--+-
Changes (by russellm):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #15158: Server-crashing error: local variable 'loader_name' referenced before assignment

[Django]

#15158: Server-crashing error: local variable 'loader_name' referenced before
assignment
-+--
   Reporter:  gsf| Owner:  ramiro
 Status:  closed | Milestone:  1.3   
  Component:  Core framework |   Version:  SVN   
 Resolution:  fixed  |  Keywords:  regression
   Triage Stage:  Ready for checkin  | Has patch:  1 
Needs documentation:  0  |   Needs tests:  1 
Patch needs improvement:  0  |  
-+--

Comment (by gsf):

 Replying to [comment:4 ramiro]:
 > @gsf:
 >
 > It seems one of the template loaders you have listed in your
 `TEMPLATE_LOADERS` setting has problems when it is going to be loaded. Can
 you verify this and post the value of such setting?

 Sorry I missed this earlier. It looks like the error was caused by a
 combination of a missing template and the old style for template loaders
 in my settings file, i.e.:

 {{{
 TEMPLATE_LOADERS = (
 'django.template.loaders.filesystem.load_template_source',
 'django.template.loaders.app_directories.load_template_source',
 )
 }}}

-- 
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] #15193: string indices must be integers, not str during YAML deserialization

[Django]

#15193: string indices must be integers, not str during YAML deserialization
--+-
   Reporter:  Jack| Owner:  nobody
 Status:  new | Milestone:
  Component:  Core framework  |   Version:  1.2   
 Resolution:  |  Keywords:
   Triage Stage:  Unreviewed  | Has patch:  0 
Needs documentation:  0   |   Needs tests:  0 
Patch needs improvement:  0   |  
--+-
Changes (by Jack):

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


Comment:

 Sorry, I realized that I can't use {{{'''}}} inside code snippet, please
 disregard it around:
 {{{'''[yaml.load(stream),]'''}}}

-- 
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] #15193: string indices must be integers, not str during YAML deserialization

[Django]

#15193: string indices must be integers, not str during YAML deserialization
+---
 Reporter:  Jack|  Owner:  nobody
   Status:  new |  Milestone:
Component:  Core framework  |Version:  1.2   
 Keywords:  |   Triage Stage:  Unreviewed
Has patch:  0   |  
+---
 Traceback:
 Problem installing fixture 'data\init.yaml': Traceback (most recent call
 last):
   File "C:\Python26\lib\site-
 packages\django\core\management\commands\loaddata.p
 y", line 169, in handle
 for obj in objects:
   File "C:\Python26\lib\site-packages\django\core\serializers\pyyaml.py",
 line 5
 9, in Deserializer
 for obj in PythonDeserializer(objs, **options):
   File "C:\Python26\lib\site-packages\django\core\serializers\python.py",
 line 8
 4, in Deserializer
 Model = _get_model(d["model"])
 TypeError: string indices must be integers, not str

 I made the following change to pyyaml.py and it fixed the problem:
 {{{
 def Deserializer(stream_or_string, **options):
 """
 Deserialize a stream or string of YAML data.
 """
 if isinstance(stream_or_string, basestring):
 stream = StringIO(stream_or_string)
 else:
 stream = stream_or_string
 for obj in PythonDeserializer('''[yaml.load(stream),]''', **options):
 yield obj
 }}}
 I'm running Windows XP SP3 with this version of pyyaml:

 http://pyyaml.org/download/pyyaml/PyYAML-3.09.win32-py2.6.exe

-- 
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] #14760: Admin inlines with file/image field fails to save_as

[Django]

#14760: Admin inlines with file/image field fails to save_as
--+-
   Reporter:  paulos  | Owner:  nobody
 Status:  reopened| Milestone:
  Component:  django.contrib.admin|   Version:  1.2   
 Resolution:  |  Keywords:
   Triage Stage:  Design decision needed  | Has patch:  0 
Needs documentation:  0   |   Needs tests:  0 
Patch needs improvement:  0   |  
--+-

Comment (by SmileyChris):

 There's nothing in the "nature" of a `FileField` stating that you can't
 have multiple fields attached to the same file.

 In fact, there's logic in the delete method to avoid the underlying file
 getting deleted if any other fields in the same model reference it
 (granted, the very fact the underlying file is deleted is now under
 consideration as a bug, but that's an aside...).

-- 
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] #15189: django 1.2 docs claim auth login and logout signals

[Django]

#15189: django 1.2 docs claim auth login and logout signals
-+--
   Reporter:  roderyc@…  | Owner:  nobody
 Status:  new| Milestone:
  Component:  Documentation  |   Version:  1.2   
 Resolution: |  Keywords:
   Triage Stage:  Unreviewed | Has patch:  0 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by lrekucki):

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


Comment:

 This looks like a bug in the new site, not the docs itself. Also see:
 Ticket #15192

-- 
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] #15192: 1.2/tutorial04 refers to class-based generic views

[Django]

#15192: 1.2/tutorial04 refers to class-based generic views
-+--
   Reporter:  MixedContent   | Owner:  nobody
 Status:  new| Milestone:
  Component:  Uncategorized  |   Version:  1.2   
 Resolution: |  Keywords:
   Triage Stage:  Accepted   | Has patch:  0 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by lrekucki):

  * needs_better_patch:  => 0
  * needs_docs:  => 0
  * needs_tests:  => 0
  * stage:  Unreviewed => Accepted


Comment:

 The source in repository:
 
http://code.djangoproject.com/browser/django/branches/releases/1.2.X/docs/intro/tutorial04.txt#L241
 looks correct. So does HTML generated from source. This is most likely an
 issue with the new site rendering the wrong version of docs. Ticket #15189
 looks similar.

-- 
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] #15192: 1.2/tutorial04 refers to class-based generic views

[Django]

#15192: 1.2/tutorial04 refers to class-based generic views
---+
 Reporter:  MixedContent   |  Owner:  nobody
   Status:  new|  Milestone:
Component:  Uncategorized  |Version:  1.2   
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  
---+
 I am the opposite of an expert, but I believe this is a doc problem.

 IIUC, class-based generic views were introduced in Django 1.3, and prior
 to that time, generic views were function-based.

 I am running Django 1.2.4.

 The 1.1 tutorial04 refers to function-based generic views.  The 1.2
 tutorial04 refers to class-based generic views.  The most obvious
 consequence of this, to the novice, is that attempting to run the example
 code that shows how to use generic views results in "ImportError at /polls
 ... cannot import name DetailView"

 I believe this error was introduced recently, because if I remember
 correctly, I first encountered this message due to an error on my part,
 which was that I had inadvertently navigated to the tutorial(04) for the
 dev version, and that when I loaded the 1.2 tutorial instead, the example
 code was different, and ran properly.

 Why I'm running through the same tutorial again is a reasonable question,
 but beyond the scope.

 URL of doc page: http://docs.djangoproject.com/en/1.2/intro/tutorial04/

-- 
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] #5423: "dumpdata" should stream output one row at a time

[Django]

#5423: "dumpdata" should stream output one row at a time
-+--
   Reporter:  adrian | Owner:  ramiro   
   
 Status:  assigned   | Milestone:   
   
  Component:  Serialization  |   Version:  SVN  
   
 Resolution: |  Keywords:  dumpdata fixtures 
memory
   Triage Stage:  Accepted   | Has patch:  1
   
Needs documentation:  0  |   Needs tests:  0
   
Patch needs improvement:  0  |  
-+--

Comment (by ramiro):

 Results obtained testing with the setup described at and downloadable from
 https://bitbucket.org/cramm/serializers_memory_usage/src (serialization of
 50,000 instances of
 
[https://bitbucket.org/cramm/serializers_memory_usage/src/dc88a9b44de7/serializers_memory_usage/ticket5423/models.py
 this model ] to JSON). Results with XML, YAMS and MySQL, SQLite3 are
 similar.

 == Unpatched trunk ==

 [[Image(json-postgresq-trunk.png)]]

 == Patched trunk ==

 [[Image(json-postgresq-trunk-patched.png)]]

-- 
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] #9962: Add a tutorial for the testing framework

[Django]

#9962: Add a tutorial for the testing framework
-+--
   Reporter:  russellm   | Owner: 
 Status:  new| Milestone:  1.3
  Component:  Documentation  |   Version:  1.0
 Resolution: |  Keywords: 
   Triage Stage:  Accepted   | Has patch:  0  
Needs documentation:  1  |   Needs tests:  0  
Patch needs improvement:  0  |  
-+--
Changes (by ericholscher):

  * needs_docs:  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 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] #5423: "dumpdata" should stream output one row at a time

[Django]

#5423: "dumpdata" should stream output one row at a time
-+--
   Reporter:  adrian | Owner:  ramiro   
   
 Status:  assigned   | Milestone:   
   
  Component:  Serialization  |   Version:  SVN  
   
 Resolution: |  Keywords:  dumpdata fixtures 
memory
   Triage Stage:  Accepted   | Has patch:  1
   
Needs documentation:  0  |   Needs tests:  0
   
Patch needs improvement:  0  |  
-+--
Changes (by ramiro):

  * keywords:  dumpdata loaddata fixtures memory => dumpdata fixtures
   memory


Comment:

 Removing ''loaddata'' keyword. Loaddata has its own ticket tracking memory
 its usage issues (#12007).

 Please test the latest patch and report back your experiences. I have
 created a test environment to measure, graph and compare memory usage:
 https://bitbucket.org/cramm/serializers_memory_usage/src

-- 
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] #9962: Add a tutorial for the testing framework

[Django]

#9962: Add a tutorial for the testing framework
-+--
   Reporter:  russellm   | Owner: 
 Status:  new| Milestone:  1.3
  Component:  Documentation  |   Version:  1.0
 Resolution: |  Keywords: 
   Triage Stage:  Accepted   | Has patch:  0  
Needs documentation:  0  |   Needs tests:  0  
Patch needs improvement:  0  |  
-+--
Changes (by ericholscher):

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


Comment:

 Sadly not going to have time to get this in for 1.3. Again.

-- 
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] #15191: Minor grammar fix in form validation docs

[Django]

#15191: Minor grammar fix in form validation docs
-+--
   Reporter:  berto  | Owner:  nobody
 Status:  new| Milestone:
  Component:  Uncategorized  |   Version:  1.2   
 Resolution: |  Keywords:
   Triage Stage:  Unreviewed | Has patch:  1 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by berto):

 * cc: berto (added)
  * needs_docs:  => 0
  * 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 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] #15191: Minor grammar fix in form validation docs

[Django]

#15191: Minor grammar fix in form validation docs
---+
 Reporter:  berto  |  Owner:  nobody
   Status:  new|  Milestone:
Component:  Uncategorized  |Version:  1.2   
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  1  |  
---+
 While reading the form validation documentation [#point1 (1)] I found this
 minor grammar issue.

 Thanks,
 -Roberto.

 [=#point1 (1)] http://docs.djangoproject.com/en/1.2/ref/forms/validation
 /#cleaning-and-validating-fields-that-depend-on-each-other, look for,
 "There are two way."

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