[Django] #16491: transaction.is_dirty() is very (and surprisingly) conservative

[Django]

#16491: transaction.is_dirty() is very (and surprisingly) conservative
---+---
 Reporter:  mwhudson   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Milestone: |  Component:  Uncategorized
  Version:  1.3|   Severity:  Normal
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  1
UI/UX:  0  |
---+---
 As near as I can tell transaction.is_dirty() returns True if any queries
 have been executed at all (I think this is what lead to #15317 being
 reported). This is sort of fair enough (it's better to have a false
 positive for this sort of thing) but it certainly confused me for a good
 few minutes (commit_manually was complaining at me on exit).  If it can't
 be made more accurate, at least the docstring should be improved.  I'll
 try to come up with a patch tomorrow.

-- 
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] #16490: For select_for_update feature: DatabaseError not raised as expected when NOWAIT not supported; mult thread test also failing (on MySQL)

[Django]

#16490: For select_for_update feature: DatabaseError not raised as expected when
NOWAIT not supported; mult thread test also failing (on MySQL)
-+-
   Reporter:  jsdalton   |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: |   Severity:  Normal
   Triage Stage: |   Keywords:
  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by jsdalton):

 * cc: jim.dalton@… (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] #11665: django.test.TestCase should flush constraints

[Django]

#11665: django.test.TestCase should flush constraints
+---
   Reporter:  Glenn |  Owner:
   Type:  Bug   | Status:  new
  Milestone:|  Component:  Testing framework
Version:  SVN   |   Severity:  Normal
 Resolution:|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+---

Comment (by jsdalton):

 Just opened #16490, a report on the select_for_update error I mentioned
 above. Once those two failures are fixed, all backends will pass all
 tests.

-- 
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] #16490: For select_for_update feature: DatabaseError not raised as expected when NOWAIT not supported; mult thread test also failing (on MySQL)

[Django]

#16490: For select_for_update feature: DatabaseError not raised as expected when
NOWAIT not supported; mult thread test also failing (on MySQL)
--+--
 Reporter:  jsdalton  |  Owner:  nobody
 Type:  Bug   | Status:  new
Milestone:|  Component:  Database layer (models, ORM)
  Version:  SVN   |   Severity:  Normal
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  0 |  Easy pickings:  0
UI/UX:  0 |
--+--
 The following test fails on MySQL InnoDB. This appears to relate to the
 work recently done on #2705.

 {{{
 $ ./runtests.py --settings=testproject.settings
 select_for_update.SelectForUpdateTests
 Creating test database for alias 'default'...
 Creating test database for alias 'other'...
 F.s...F
 ==
 FAIL: test_block (modeltests.select_for_update.tests.SelectForUpdateTests)
 --
 Traceback (most recent call last):
   File
 "/Users/jsdalton/webs/testproject/src/django/django/test/testcases.py",
 line 615, in skip_wrapper
 return test_func(*args, **kwargs)
   File
 "/Users/jsdalton/webs/testproject/src/django/django/test/testcases.py",
 line 615, in skip_wrapper
 return test_func(*args, **kwargs)
   File
 
"/Users/jsdalton/webs/testproject/src/django/tests/modeltests/select_for_update/tests.py",
 line 209, in test_block
 self.assertEqual('Fred', p.name)
 AssertionError: 'Fred' != u'Reinhardt'

 ==
 FAIL: test_unsupported_nowait_raises_error
 (modeltests.select_for_update.tests.SelectForUpdateTests)
 --
 Traceback (most recent call last):
   File
 "/Users/jsdalton/webs/testproject/src/django/django/test/testcases.py",
 line 615, in skip_wrapper
 return test_func(*args, **kwargs)
   File
 "/Users/jsdalton/webs/testproject/src/django/django/test/testcases.py",
 line 615, in skip_wrapper
 return test_func(*args, **kwargs)
   File
 
"/Users/jsdalton/webs/testproject/src/django/tests/modeltests/select_for_update/tests.py",
 line 138, in test_unsupported_nowait_raises_error
 Person.objects.all().select_for_update(nowait=True)
 AssertionError: DatabaseError not raised

 --
 Ran 7 tests in 10.342s

 FAILED (failures=2, skipped=1)
 Destroying test database for alias 'default'...
 Destroying test database for alias 'other'...

 }}}


 The DatabaseError is not being raised because -- well, I wish I knew. The
 code block is being executed but the error is being caught, i.e. I can
 print to stdout but any exception is not being raised. The thread related
 error is also something I'm unclear on.

 As part of the work I am doing right now on #11665, these two issues are
 the *only* remaining failures in the MySQL test suite. Seriously, the only
 remaining failures. Given that this feature seems to be quite new, I'm
 hopeful that it's fresh on everyone's minds and easy enough to address,
 perhaps by the folks who worked so hard on #2705. If I can be of any
 assistance, let me know.

-- 
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] #16489: cache.close connection to request_finished needs to apply to all caches

[Django]

#16489: cache.close connection to request_finished needs to apply to all caches
+---
 Reporter:  jdunck  |Owner:  nobody
 Type:  Bug |   Status:  new
Milestone:  |Component:  Core (Cache system)
  Version:  1.3 | Severity:  Normal
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+---
 There is support for closing cache (if it has a .close callable), as seen
 here:
 
https://code.djangoproject.com/browser/django/trunk/django/core/cache/__init__.py?rev=16549#L181

 The trouble is that the request_finished connection is made only for the
 default .cache attribute.  This should be done for each cache backend, not
 just DEFAULT_CACHE_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.

[Django] #16488: Populating settings.CACHES based on settings.CACHE_BACKEND can fail

[Django]

#16488: Populating settings.CACHES based on settings.CACHE_BACKEND can fail
+---
 Reporter:  jdunck  |Owner:  nobody
 Type:  Bug |   Status:  new
Milestone:  |Component:  Core (Cache system)
  Version:  1.3 | Severity:  Normal
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+---
 I'm fairly sure this will be WONTFIX'd but I wanted to note this failure
 case in case it helps others.

 If django.core.cache is imported before settings finish loading, it is
 possible that settings.CACHE_BACKEND will not yet be set, so that forward-
 compatibility patching proceeds incorrectly -- using locmem rather than
 whatever may have been declared later.

 In my case, I ran into this with the fairly-common pattern of 2 settings
 files a.py and b.py, where b.py imports * from a.  A side-effect of
 importing a was that django.core.cache got imported.

 The final config is defined with CACHE_BACKEND = "dummy://", but CACHES
 ended up with default engine of "locmem://".

 Here's the code that patches CACHES from CACHE_BACKEND (if it's there):
 
https://code.djangoproject.com/browser/django/trunk/django/core/cache/__init__.py?rev=16549#L76

 Perhaps a better option would be to make the patching lazier...

-- 
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] #15894: SITE_CACHE does not invalidate in multiprocess environments

[Django]

#15894: SITE_CACHE does not invalidate in multiprocess environments
+
   Reporter:  Kronuz|  Owner:  nobody
   Type:  Bug   | Status:  new
  Milestone:|  Component:  contrib.sites
Version:  1.3   |   Severity:  Normal
 Resolution:|   Keywords:  cache invalidation
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  1
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
Changes (by fcurella):

 * cc: fcurella (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] #15894: SITE_CACHE does not invalidate in multiprocess environments

[Django]

#15894: SITE_CACHE does not invalidate in multiprocess environments
+
   Reporter:  Kronuz|  Owner:  nobody
   Type:  Bug   | Status:  new
  Milestone:|  Component:  contrib.sites
Version:  1.3   |   Severity:  Normal
 Resolution:|   Keywords:  cache invalidation
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  1
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
Changes (by fcurella):

 * ui_ux:   => 0
 * needs_tests:  0 => 1


Comment:

 've added a patch, but I have no idea on how to write tests that could
 simulate two processes. Suggestions are welcome!

-- 
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] #16487: F expression with timedelta does not work with __range query filter

[Django]

#16487: F expression with timedelta does not work with __range query filter
+--
 Reporter:  bendavis78  |  Owner:  nobody
 Type:  Bug | Status:  new
Milestone:  |  Component:  Database layer (models, ORM)
  Version:  1.3 |   Severity:  Normal
 Keywords:  |   Triage Stage:  Unreviewed
Has patch:  0   |  Easy pickings:  0
UI/UX:  0   |
+--
 Works:
 {{{
 #!python
 User.objects.filter(last_login__gt=F('date_joined')+timedelta(weeks=2))
 }}}

 Doesn't work:
 {{{
 #!python
 User.objects.filter(last_login__range=(F('date_joined'),
 F('date_joined')+timedelta(weeks=2)))
 }}}

-- 
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] #16486: Community Link Feed: Wrong links

[Django]

#16486: Community Link Feed: Wrong links
+
 Reporter:  emperorcezar@…  |  Owner:  nobody
 Type:  Bug | Status:  new
Milestone:  |  Component:  Djangoproject.com Web site
  Version:  1.3 |   Severity:  Normal
 Keywords:  |   Triage Stage:  Unreviewed
Has patch:  0   |  Easy pickings:  0
UI/UX:  0   |
+
 The community link feed:
 https://www.djangoproject.com/rss/community/links/

 All the links are only the domain, no path.

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

[Changeset] r16549 - django/trunk/django/contrib/contenttypes

[noreply]

Author: Alex
Date: 2011-07-19 10:19:32 -0700 (Tue, 19 Jul 2011)
New Revision: 16549

Modified:
   django/trunk/django/contrib/contenttypes/generic.py
Log:
Fixed some 5-space indents that were introduced with multidb.


Modified: django/trunk/django/contrib/contenttypes/generic.py
===
--- django/trunk/django/contrib/contenttypes/generic.py 2011-07-19 13:16:09 UTC 
(rev 16548)
+++ django/trunk/django/contrib/contenttypes/generic.py 2011-07-19 17:19:32 UTC 
(rev 16549)
@@ -52,9 +52,9 @@
 # using this model
 ContentType = get_model("contenttypes", "contenttype")
 if obj:
- return 
ContentType.objects.db_manager(obj._state.db).get_for_model(obj)
+return 
ContentType.objects.db_manager(obj._state.db).get_for_model(obj)
 elif id:
- return ContentType.objects.db_manager(using).get_for_id(id)
+return ContentType.objects.db_manager(using).get_for_id(id)
 else:
 # This should never happen. I love comments like this, don't you?
 raise Exception("Impossible arguments to GFK.get_content_type!")

-- 
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] #16485: Admin URL bug with CharField primary keys

[Django]

#16485: Admin URL bug with CharField primary keys
-+-
   Reporter:  sbaechler  |  Owner:  nobody
   Type:  Bug| Status:  closed
  Milestone: |  Component:  contrib.admin
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:  admin primary_key
  worksforme |  Has patch:  0
   Triage Stage:  Design |Needs tests:  0
  decision needed|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by ramiro):

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


Comment:

 Can't reproduce this with trunk tip nor the 1.3 release, using this model.

 {{{
 from django.db import models

 class FacebookPost(models.Model):
 id = models.CharField('id', max_length=40, primary_key=True)
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #11665: django.test.TestCase should flush constraints

[Django]

#11665: django.test.TestCase should flush constraints
+---
   Reporter:  Glenn |  Owner:
   Type:  Bug   | Status:  new
  Milestone:|  Component:  Testing framework
Version:  SVN   |   Severity:  Normal
 Resolution:|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+---
Changes (by jsdalton):

 * needs_better_patch:  1 => 0


Comment:

 Okay, did a bit more work on this and I think we're there -- for this
 ticket at least.

 Basically after running tests last night and analyzing the results, there
 are *only* two problems that exist:

 * A few `multiple_database` tests throw errors (the ones ramiro already
 identified). In this patch, I have simply disabled constraint checking for
 those test cases (in `setUp` and `tearDown`). This puts the tests back
 where they are now -- since right now there are no constraint checks being
 run and that's why they are passing. I propose we open a new, separate
 ticket for the issue because frankly I think it's out of the scope of this
 ticket to make a decision about how it should be handled.

 * A few `select_for_update` errors in MySQL. Basically, two of the
 `select_for_update` tests are failing for MySQL. They are failing
 presently (without the patch) and I don't have an easy solution for them
 either. Again, I propose we open a new ticket to handle these. It appears
 they are legitimate bugs from what I can tell -- the code being exercised
 is not behaving as expected, and this needs to be addressed.

 Removing the patch needs improvement flag, because this patch should be
 ready for checkin -- assuming no one has any concerns with the approach I
 took to solve the various little issues. Also, do we need documentation?

 Note again that that *includes* the patch from #3615 because that has not
 been committed yet, and the code there is required for this. For
 convenience, here again is a diff against that other patch which
 highlights more clearly the actual work being done for this ticket:
 http://paste.pocoo.org/show/442244/

-- 
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] #16388: django unittest bug

[Django]

#16388: django unittest bug
--+---
   Reporter:  freewave@…  |  Owner:  nobody
   Type:  Bug | Status:  closed
  Milestone:  |  Component:  Testing framework
Version:  1.3 |   Severity:  Normal
 Resolution:  needsinfo   |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+---

Comment (by freewave@…):

 Sorry!
 My prev python version is "Python 2.7a1 (r27a1:76691, Dec 6 2009,
 19:41:06) on win32". The problem exists in this version.
 Problem is gone when I reinstall python "Python 2.7.2 (default, Jun 12
 2011, 15:08:59) [MSC v.1500 32 bit (Intel)] on win32".

-- 
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] #15951: Document new backport policy.

[Django]

#15951: Document new backport policy.
-+-
   Reporter:  apollo13   |  Owner:  nobody
   Type: | Status:  closed
  Cleanup/optimization   |  Component:  Documentation
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution:  fixed  |  Has patch:  0
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by anonymous):

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


Comment:

 fixed in [16548]

-- 
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] #16469: Improve the "internals" docs

[Django]

#16469: Improve the "internals" docs
-+-
   Reporter:  aaugustin  |  Owner:  nobody
   Type: | Status:  closed
  Cleanup/optimization   |  Component:  Documentation
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution:  fixed  |  Has patch:  1
   Triage Stage:  Ready for  |Needs tests:  0
  checkin|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by jezdez):

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


Comment:

 In [16548]:
 {{{
 #!CommitTicketReference repository="" revision="16548"
 Fixed #16469 -- Improved documentation of Django internals, including the
 new backport policy. Many thanks to Aymeric Augustin.
 }}}

-- 
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] #16485: Admin URL bug with CharField primary keys

[Django]

#16485: Admin URL bug with CharField primary keys
-+-
   Reporter:  sbaechler  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  contrib.admin
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:  admin primary_key
   Triage Stage:  Design |  Has patch:  0
  decision needed|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by BernhardEssl):

 * needs_better_patch:   => 0
 * version:  1.3 => SVN
 * needs_docs:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Design decision needed


Comment:

 As far as I understand the ''quote'' function in util.py
 
https://code.djangoproject.com/browser/django/trunk/django/contrib/admin/util.py#L15
 do the escaping.
 I'm not sure if this is really a 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] #15315: modelform_factory should accept widgets argument

[Django]

#15315: modelform_factory should accept widgets argument
-+--
   Reporter:  SardarNL   |  Owner:  nobody
   Type:  New feature| Status:  new
  Milestone: |  Component:  Forms
Version:  1.2|   Severity:  Normal
 Resolution: |   Keywords:  dceu2011
   Triage Stage:  Ready for checkin  |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+--
Changes (by jezdez):

 * 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] #16414: Missing Windows build script for Sphinx

[Django]

#16414: Missing Windows build script for Sphinx
-+-
   Reporter: |  Owner:  nobody
  alexandrul | Status:  closed
   Type:  New|  Component:  Documentation
  feature|   Severity:  Normal
  Milestone: |   Keywords:
Version:  1.3|  Has patch:  1
 Resolution:  fixed  |Needs tests:  0
   Triage Stage:  Ready for  |  Easy pickings:  1
  checkin|
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by jezdez):

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


Comment:

 In [16547]:
 {{{
 #!CommitTicketReference repository="" revision="16547"
 Fixed #16414 -- Added standard Windows make batch file for Sphinx. Thanks,
 Aymeric Augustin.
 }}}

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

[Changeset] r16547 - in django/trunk/docs: . internals/contributing intro

[noreply]

Author: jezdez
Date: 2011-07-19 02:00:24 -0700 (Tue, 19 Jul 2011)
New Revision: 16547

Added:
   django/trunk/docs/make.bat
Modified:
   django/trunk/docs/README
   django/trunk/docs/internals/contributing/writing-documentation.txt
   django/trunk/docs/intro/whatsnext.txt
Log:
Fixed #16414 -- Added standard Windows make batch file for Sphinx. Thanks, 
Aymeric Augustin.

Modified: django/trunk/docs/README
===
--- django/trunk/docs/README2011-07-17 22:22:39 UTC (rev 16546)
+++ django/trunk/docs/README2011-07-19 09:00:24 UTC (rev 16547)
@@ -9,7 +9,8 @@
 
 * Install Sphinx (using ``easy_install Sphinx`` or some other method)
 
-* In this docs/ directory, type ``make html`` at a shell prompt.
+* In this docs/ directory, type ``make html`` (or ``make.bat html`` on
+  Windows) at a shell prompt.
 
 The documentation in _build/html/index.html can then be viewed in a web 
browser.
 

Modified: django/trunk/docs/internals/contributing/writing-documentation.txt
===
--- django/trunk/docs/internals/contributing/writing-documentation.txt  
2011-07-17 22:22:39 UTC (rev 16546)
+++ django/trunk/docs/internals/contributing/writing-documentation.txt  
2011-07-19 09:00:24 UTC (rev 16547)
@@ -40,8 +40,8 @@
 
 __ http://pygments.org
 
-Then, building the HTML is easy; just ``make html`` from the ``docs``
-directory.
+Then, building the HTML is easy; just ``make html`` (or ``make.bat html`` on
+Windows) from the ``docs`` directory.
 
 To get started contributing, you'll want to read the `reStructuredText
 Primer`__. After that, you'll want to read about the `Sphinx-specific markup`__

Modified: django/trunk/docs/intro/whatsnext.txt
===
--- django/trunk/docs/intro/whatsnext.txt   2011-07-17 22:22:39 UTC (rev 
16546)
+++ django/trunk/docs/intro/whatsnext.txt   2011-07-19 09:00:24 UTC (rev 
16547)
@@ -183,6 +183,13 @@
 
   You'll need `GNU Make`__ installed for this.
 
+  If you're on Windows you can alternatively use the included batch file:
+
+  .. code-block:: bat
+
+cd path\to\django\docs
+make.bat html
+
 * The HTML documentation will be placed in ``docs/_build/html``.
 
 .. note::

Added: django/trunk/docs/make.bat
===
--- django/trunk/docs/make.bat  (rev 0)
+++ django/trunk/docs/make.bat  2011-07-19 09:00:24 UTC (rev 16547)
@@ -0,0 +1,170 @@
+@ECHO OFF
+
+REM Command file for Sphinx documentation
+
+if "%SPHINXBUILD%" == "" (
+   set SPHINXBUILD=sphinx-build
+)
+set BUILDDIR=_build
+set ALLSPHINXOPTS=-d %BUILDDIR%/doctrees %SPHINXOPTS% .
+if NOT "%PAPER%" == "" (
+   set ALLSPHINXOPTS=-D latex_paper_size=%PAPER% %ALLSPHINXOPTS%
+)
+
+if "%1" == "" goto help
+
+if "%1" == "help" (
+   :help
+   echo.Please use `make ^` where ^ is one of
+   echo.  html   to make standalone HTML files
+   echo.  dirhtmlto make HTML files named index.html in directories
+   echo.  singlehtml to make a single large HTML file
+   echo.  pickle to make pickle files
+   echo.  json   to make JSON files
+   echo.  htmlhelp   to make HTML files and a HTML help project
+   echo.  qthelp to make HTML files and a qthelp project
+   echo.  devhelpto make HTML files and a Devhelp project
+   echo.  epub   to make an epub
+   echo.  latex  to make LaTeX files, you can set PAPER=a4 or 
PAPER=letter
+   echo.  text   to make text files
+   echo.  manto make manual pages
+   echo.  changesto make an overview over all changed/added/deprecated 
items
+   echo.  linkcheck  to check all external links for integrity
+   echo.  doctestto run all doctests embedded in the documentation if 
enabled
+   goto end
+)
+
+if "%1" == "clean" (
+   for /d %%i in (%BUILDDIR%\*) do rmdir /q /s %%i
+   del /q /s %BUILDDIR%\*
+   goto end
+)
+
+if "%1" == "html" (
+   %SPHINXBUILD% -b djangohtml %ALLSPHINXOPTS% %BUILDDIR%/html
+   if errorlevel 1 exit /b 1
+   echo.
+   echo.Build finished. The HTML pages are in %BUILDDIR%/html.
+   goto end
+)
+
+if "%1" == "dirhtml" (
+   %SPHINXBUILD% -b dirhtml %ALLSPHINXOPTS% %BUILDDIR%/dirhtml
+   if errorlevel 1 exit /b 1
+   echo.
+   echo.Build finished. The HTML pages are in %BUILDDIR%/dirhtml.
+   goto end
+)
+
+if "%1" == "singlehtml" (
+   %SPHINXBUILD% -b singlehtml %ALLSPHINXOPTS% %BUILDDIR%/singlehtml
+   if errorlevel 1 exit /b 1
+   echo.
+   echo.Build finished. The HTML pages are in %BUILDDIR%/singlehtml.
+   goto end
+)
+
+if "%1" == "pickle" (
+   %SPHINXBUILD% -b pickle %ALLSPHINXOPTS% %BUILDDIR%/pickle
+   if errorlevel 1 exit /b 1
+   echo.
+   echo.Build 

Re: [Django] #16468: Django IPAddressField incorrectly casts values when querying

[Django]

#16468: Django IPAddressField incorrectly casts values when querying
-+-
   Reporter:  anonymous  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Database layer
Version:  1.3|  (models, ORM)
 Resolution: |   Severity:  Normal
   Triage Stage:  Design |   Keywords:
  decision needed|  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-

Comment (by anonymous):

 Replying to [comment:8 aaugustin]:
 > Maybe. Feel free to submit a patch!
 Sure, I will take a peek inside Django's internals.

-- 
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] #13: Related objects interface should be tighter (edit_inline)

[Django]

#13: Related objects interface should be tighter (edit_inline)
-+-
   Reporter:  adrian |  Owner:  barbuza
   Type:  New| Status:  reopened
  feature|  Component:  contrib.admin
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:  nfa-someday nfa-
 Resolution: |  changelist
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  1  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by lea):

 * ui_ux:   => 0
 * easy:   => 0


Comment:

 I thought all wiki pages are editable? hmm. I put one in my
 [http://seoph1.cafe24.com/wordpress/ Blog in SEO]

-- 
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] #16485: Admin URL bug with CharField primary keys

[Django]

#16485: Admin URL bug with CharField primary keys
---+---
 Reporter:  sbaechler  |  Owner:  nobody
 Type:  Bug| Status:  new
Milestone: |  Component:  contrib.admin
  Version:  1.3|   Severity:  Normal
 Keywords:  admin primary_key  |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
UI/UX:  0  |
---+---
 I have the following primary key field:

 {{{
 id = models.CharField(_('id'), max_length=40, primary_key=True)
 }}}
 The value is: 126130274108967_190034094385251 (a Facebook post id)

 The admin interface change list correctly shows that id. But the url of
 the item is
 126130274108967_5F190034094385251/ notice the _5F... in the middle.

 This causes a 404 every time I create a new entry.

 Regards
 Simon

-- 
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] #16484: Duplicate entry sessions error

[Django]

#16484: Duplicate entry sessions error
---+--
 Reporter:  hash.3g@…  |  Owner:  nobody
 Type:  Bug| Status:  new
Milestone: |  Component:  contrib.sessions
  Version:  1.3|   Severity:  Normal
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
UI/UX:  0  |
---+--
 Hi, Sometimes we receive "duplicate entry" error from django sessions. See
 Traceback.

 {{{
 Traceback (most recent call last):

 File "/usr/local/lib/python2.6/dist-
 packages/django/core/handlers/base.py", line 178, in get_response
   response = middleware_method(request, response)
 File "/usr/local/lib/python2.6/dist-
 packages/django/contrib/sessions/middleware.py", line 36, in
 process_response
   request.session.save()
 File "/usr/local/lib/python2.6/dist-
 packages/django/contrib/sessions/backends/db.py", line 63, in save
   obj.save(force_insert=must_create, using=using)
 File "/usr/local/lib/python2.6/dist-packages/django/db/models/base.py",
 line 460, in save
   self.save_base(using=using, force_insert=force_insert,
 force_update=force_update)
 File "/usr/local/lib/python2.6/dist-packages/django/db/models/base.py",
 line 553, in save_base
   result = manager._insert(values, return_id=update_pk, using=using)
 File "/usr/local/lib/python2.6/dist-packages/django/db/models/manager.py",
 line 195, in _insert
   return insert_query(self.model, values, **kwargs)
 File "/usr/local/lib/python2.6/dist-packages/django/db/models/query.py",
 line 1436, in insert_query
   return query.get_compiler(using=using).execute_sql(return_id)
 File "/usr/local/lib/python2.6/dist-
 packages/django/db/models/sql/compiler.py", line 791, in execute_sql
   cursor = super(SQLInsertCompiler, self).execute_sql(None)
 File "/usr/local/lib/python2.6/dist-
 packages/django/db/models/sql/compiler.py", line 735, in execute_sql
   cursor.execute(sql, params)
 File "/usr/local/lib/python2.6/dist-
 packages/django/db/backends/mysql/base.py", line 86, in execute
   return self.cursor.execute(query, args)
 File "/usr/lib/pymodules/python2.6/MySQLdb/cursors.py", line 166, in
 execute
   self.errorhandler(self, exc, value)
 File "/usr/lib/pymodules/python2.6/MySQLdb/connections.py", line 35, in
 defaulterrorhandler
   raise errorclass, errorvalue
 IntegrityError: (1062, “Duplicate entry ‘e110c3788ccb21c76865285446102338’
 for key 'PRIMARY'”)
 }}}

 Periodically we do cleaning of out-of-date sessions, but it does not help
 from current error.

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