date:20140501

[Django] #22558: missing a word in "how to contribute to django"

2014-05-01 Thread Django

#22558: missing a word in "how to contribute to django"
--+
 Reporter:  bjb@… |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  1 |  UI/UX:  0
--+
 In master, 1.7, 1.6 and 1.5, on page
 https://docs.djangoproject.com/en/1.6/intro/contributing/#installing-git,
 in the second sentence of the second paragraph it says:

 `If you get messages saying that this command could be found`

 and it should say

 `If you get messages saying that this command could not be found`


 I have made this change in my github fork of django:
 https://github.com/bjb/django

 on master, stable/1.5.x, stable/1.6.x and stable/1.7.x .


 https://github.com/bjb/django/tree/stable/1.5.x
 https://github.com/bjb/django/tree/stable/1.6.x
 https://github.com/bjb/django/tree/stable/1.7.x
 https://github.com/bjb/django/tree/master

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

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

[django/django] 5ab93b: [1.7.x] Fix migration autodector to work correctly...

2014-05-01 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 5ab93bbe747f5af185631a4ea591a501e3f8a06c
  
https://github.com/django/django/commit/5ab93bbe747f5af185631a4ea591a501e3f8a06c
  Author: Chris Beaven 
  Date:   2014-05-02 (Fri, 02 May 2014)

  Changed paths:
M django/db/migrations/autodetector.py
M tests/migrations/test_autodetector.py

  Log Message:
  ---
  [1.7.x] Fix migration autodector to work correctly with custom deconstructed 
values


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

[django/django] a0c4b8: Fix migration autodector to work correctly with cu...

2014-05-01 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a0c4b8465db3a4b2df247912d79c5c0a752cee76
  
https://github.com/django/django/commit/a0c4b8465db3a4b2df247912d79c5c0a752cee76
  Author: Chris Beaven 
  Date:   2014-05-02 (Fri, 02 May 2014)

  Changed paths:
M django/db/migrations/autodetector.py
M tests/migrations/test_autodetector.py

  Log Message:
  ---
  Fix migration autodector to work correctly with custom deconstructed values


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

[Django] #22557: staticfiles.json keeps deleted entries when collectstatic is run

2014-05-01 Thread Django

#22557: staticfiles.json keeps deleted entries when collectstatic is run
-+-
 Reporter:   |  Owner:  nobody
  tedtieken  | Status:  new
 Type:  Bug  |Version:  1.7-beta-2
Component:   |   Keywords:  hashed_files, collectstatic,
  contrib.staticfiles|  manifest
 Severity:  Normal   |  Has patch:  0
 Triage Stage:   |  UI/UX:  0
  Unreviewed |
Easy pickings:  0|
-+-
 There is some surprising behavior when the new HashedFilesMixin is used
 with the new ManifestFilesMixin.

 When you run {{{manage.py collectstatic --clear}}}:

 1) a copy of the old manifest.json is loaded from disk into memory at
 {{{ManifestFilesMixin.hashed_files}}}.  This happens at the very beginning
 of collectstatic (when {{{ManifestFilesMixin.__init__}}} is called, which
 happens when the storage is initialized, which happens during
 {{{Command.__init__}}})
 2) the old manifest.json is deleted (which would lead most people to
 believe the old manifest information is deleted as well)
 3) new files are added to the {{{ManifestFilesMixin.hashed_files}}} dict,
 and updated files get their records updated.  But, this is building on top
 of the last version of manifest.json.  Keys for deleted files are never
 removed and the deleted file mappings persist in the new manifest.json
 which gets written back to disk at the end of collectstatic's post_process
 phase.

 There are at least a few problems caused by the current setup:
 1) It can lead to hard-to-find asset bugs.  If you rename the mypage.css
 file to mynewpage.css, but forget to update all of the templates, the {{{
 {% static %} }}} template tag will happily serve you the stale cache
 record.  This could lead to submarine bugs that aren't caught until
 production as few sites have full enough test suites to catch missing css.
 And the issue could get buried even deeper if you concatenate your CSS.

 2) staticfiles.json has a memory leak.  New files get added, but deleted
 files never get deleted unless you physically delete the staticfiles.json
 record.

 3) If you write code that does anything with
 {{{ManifestFilesMixin.hashed_files}}}, you can't trust the cache and you
 have no way of cleaning it up when you find cache misses.  (how I found
 the bug) I'm writing a css concatenator and because staticfiles.json never
 gets cleared, I have to keep a separate manifest for my mappings.

 This problem may also exist when you use the CachedFilesMixin.  I haven't
 tested that, but a quick read over the code suggests similar behavior
 exists there.  2 is less of an issue because caches are built to drop data
 over time. 3 is less of an issue because you can easily delete stale cache
 keys from anywhere in your application.


 I see a few ways to fix the problem, and I'm sure there are others:

 Option 1: clear the hashed files cache when collectstatic is run with
 --clear.

 If the code in
 {{{django.contrib.staticfiles.management.commands.collectstatic}}} on
 lines 88-89 is changed from:

 {{{
 if self.clear:
 self.clear_dir('')
 }}}

 to

 {{{
 if self.clear:
 self.clear_dir('')
 if hasattr(self.storage, "hashed_files"):
 self.storage.hashed_files.clear()
 }}}

 This is pretty simple when you're using a manifest but, when a cache
 backend is used without a separate cache defined for staticfiles, this
 looks like it will clear _THE ENTIRE_ default cache.


 Option 2: Move the cleanup work into the StaticFilesStorage, add a call
 from collectstatic.

 If we added something like an {{{on_collectstatic}}} method to staticfiles
 storages and call it during collectstatic, we could have better
 encapsulation of this kind of cleanup that is also more futureproof.

 in {{{django.contrib.staticfiles.management.commands.collectstatic}}} add
 the following somewhere before post_process (~ line 107):
 {{{
 if hasattr(self.storage, "on_collectstatic"):
 self.storage.on_collectstatic(self)
 }}}


 Which would allow us to add to the ManifestFilesMixin:
 {{{
 def on_collectstatic(command_object, *args, **kwargs):
 if command_object.clear:
 self.hashed_files = OrderedDict()

 }}}

 This lets us to do manifest files related cleanup work in the
 ManifestFilesMixin, and anyone who needs to can do custom cleanup of their
 own storage.


 Option 3: add a warning to the documentation,


 Of the options, I like some version of 2 the best.

 I don't think this is necessarily a release blocker, but as soon as people
 start using the ManifestFilesMixin they're going to start bumping into
 this whether they realize it or not.

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

Re: [Django] #22552: 1.7 beta 3 regression - BoundField.value() tries to call GenericRelatedObjectManager instance without args

2014-05-01 Thread Django

#22552: 1.7 beta 3 regression - BoundField.value() tries to call
GenericRelatedObjectManager instance without args
-+-
 Reporter:  stephenmcd   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:
  contrib.contenttypes   |  1.7-beta-2
 Severity:  Release blocker  |   Resolution:  invalid
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


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

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

Re: [Django] #22485: makemigrations fails with dependencies to unmigrated apps

2014-05-01 Thread Django

#22485: makemigrations fails with dependencies to unmigrated apps
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  migrations,  | Triage Stage:  Accepted
  unmigrated, makemigrations |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by hjwp):

 my bad. I thought 1.7b3 included the fix.  Can confirm it's fixed in
 stable/1.7.x from gh.

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

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

Re: [Django] #22485: makemigrations fails with dependencies to unmigrated apps

2014-05-01 Thread Django

#22485: makemigrations fails with dependencies to unmigrated apps
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  migrations,  | Triage Stage:  Accepted
  unmigrated, makemigrations |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by charettes):

 @hjwp I can't reproduce your issue with Py2.7, Py3.4 and master,
 stable/1.7.x. Looking at your requirements it seems your still using 1.7b1
 and not the latest master or stable/1.7.x.

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

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

Re: [Django] #22485: makemigrations fails with dependencies to unmigrated apps

2014-05-01 Thread Django

#22485: makemigrations fails with dependencies to unmigrated apps
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  migrations,  | Triage Stage:  Accepted
  unmigrated, makemigrations |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by truddick):

 Works for me, too. I had a bit of a speedbump figuring out how to install
 the patched version of 1.7, so for future reference here's what I did:

 {{{
 sudo pip uninstall django  # was 1.7b3
 sudo pip install git+https://github.com/django/django@stable/1.7.x
 }}}

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

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

Re: [Django] #22485: makemigrations fails with dependencies to unmigrated apps

2014-05-01 Thread Django

Comment (by hjwp):

I'm still seeing a problem. Repo here:

{{{
git clone https://github.com/hjwp/book-example.git # simple app with
custom user model
cd book-example/
git checkout 841635507
mkdir ../database
python3 manage.py migrate
# errors

rm accounts/migrations/0001_initial.py # attempt to recreate migration
python3 manage.py makemigrations
python3 manage.py migrate # still errors
}}}

Hope it's of use. I think my custom user model may be a bit weird,
because when I make an even simpler one (in the chapter_16 branch)
everything is ok...

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

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

Re: [Django] #22556: close_if_unusuable_or_obsolete should handle InterfaceError

2014-05-01 Thread Django

#22556: close_if_unusuable_or_obsolete should handle InterfaceError
-+-
 Reporter:  pennersr |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.6
  (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 timo):

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


Comment:

 Can you please try with 1.6.4? This may have been fixed in #21202.

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

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

Re: [Django] #22552: 1.7 beta 3 regression - BoundField.value() tries to call GenericRelatedObjectManager instance without args

2014-05-01 Thread Django

#22552: 1.7 beta 3 regression - BoundField.value() tries to call
GenericRelatedObjectManager instance without args
-+-
 Reporter:  stephenmcd   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:
  contrib.contenttypes   |  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by devo):

 @loic84 - you're a superstar, that resolves the issue on my end. Thank you
 very much!

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

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

Re: [Django] #8936: add databrowse-like functionality to the admin

2014-05-01 Thread Django

#8936: add databrowse-like functionality to the admin
---+-
 Reporter:  simon  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  1.0
 Severity:  Normal |   Resolution:
 Keywords:  django pony| Triage Stage:  Someday/Maybe
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by timo):

 If you want to see this, make a proposal (comment 12 looks good) and
 implement it with tests and documentation. That will be more useful than
 lamenting the fact that no one has done it.

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

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

[Django] #22556: close_if_unusuable_or_obsolete should handle InterfaceError

2014-05-01 Thread Django

#22556: close_if_unusuable_or_obsolete should handle InterfaceError
--+
 Reporter:  pennersr  |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.6
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 With Django 1.6.2 I ran into the following stack trace:

 {{{
 ...
 close_old_connections()
   File "/somewhere/virtualenv/local/lib/python2.7/site-
 packages/django/db/__init__.py", line 94, in close_old_connections
 conn.close_if_unusable_or_obsolete()
   File "/somewhere/virtualenv/local/lib/python2.7/site-
 packages/django/db/backends/__init__.py", line 462, in
 close_if_unusable_or_obsolete
 if self.is_usable():
   File "/somewhere/virtualenv/local/lib/python2.7/site-
 packages/django/db/backends/postgresql_psycopg2/base.py", line 192, in
 is_usable
 self.connection.cursor().execute("SELECT 1")
 InterfaceError: connection already closed
 <... at 0xac6ec0c> failed with InterfaceError
 }}}

 I see that `close_if_unusuable_or_obsolete` gracefully handles
 `DatabaseError` exceptions. Shouldn't `InterfaceError` be caught as well?

 FWIW -- I am invoking `close_old_connections` myself because I am making
 heavy use of greenlets. I would like to call a Django method to close
 connections if needed, without having to worry about exceptions like
 these.

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

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

Re: [Django] #8936: add databrowse-like functionality to the admin

2014-05-01 Thread Django

#8936: add databrowse-like functionality to the admin
---+-
 Reporter:  simon  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  1.0
 Severity:  Normal |   Resolution:
 Keywords:  django pony| Triage Stage:  Someday/Maybe
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by anonymous):

 It's weird to see a feature that was requested 6 years ago, by multiple
 people, still not being implemented. Instead, the "admins" refused this a
 number of times, calling it a pony, and generally ignoring what actual
 users want. It's very sad.

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

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

Re: [Django] #22552: 1.7 beta 3 regression - BoundField.value() tries to call GenericRelatedObjectManager instance without args

2014-05-01 Thread Django

#22552: 1.7 beta 3 regression - BoundField.value() tries to call
GenericRelatedObjectManager instance without args
-+-
 Reporter:  stephenmcd   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:
  contrib.contenttypes   |  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by loic84):

 @stephenmcd could you try https://gist.github.com/11458982?

 With the latest master of both Mezzanine and Django I get `ImportError:
 cannot import name 'conf' from 'mezzanine'` when attempting to `runserver`
 (probably a circular import); as a result the patch is completely
 untested, let me know the outcome.

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

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

[Django] #22555: Migration doesn't work when fields are added using contribute_to_class

2014-05-01 Thread Django

#22555: Migration doesn't work when fields are added using contribute_to_class
-+-
 Reporter:   |  Owner:  nobody
  Matt3o12   | Status:  new
 Type:  Bug  |Version:  1.7-beta-2
Component:   |   Keywords:  migration, fake, __fake__,
  Migrations |  contribute_to_class
 Severity:  Release  |  Has patch:  0
  blocker|  UI/UX:  0
 Triage Stage:   |
  Unreviewed |
Easy pickings:  0|
-+-
 When you create a custom Field that implements the `contribute_to_class`
 and add another Field that way, it won't be possible to use migration.

 The code I used:

 {{{
 #!python
 class MyField(models.CharField):
 def contribute_to_class(self, cls, name):
 if not cls._meta.abstract:
 field = CharField(max_length = 20)
 cls.add_to_class("%s_mycontribute" % name, field)


 super(MyField, self).contribute_to_class(cls, name)

 }}}

 What happens if the original model is used (`app.models.MyModel`):
 1. contribute_to_class is called and adds additional fields (in my
 example, `MyField`).
 2. contribute_to_class calls it super function and adds the original field
 (`CharField`).

  Everything works. The model has 2 fields: `MyField`, and `CharField`.

 ---

 When python tries to create a migration (now the model `__fake__.MyModel`
 is used).
 1. contribute_to_class is called. The model already has the contributed
 CharField (with the name %s_mycontribute) (why does the model already have
 it?).
 2. MyField with the exactly name is added again (and no exception is
 thrown?!).
 3. The original field (MyField) is added.

  The view now has 3 fields: `MyField`, `CharField`, and `CharField` again
 (both `CharField`s have the same name).
 The next step django does is trying to migrate my model but it fails with
 the exception: "django.db.utils.OperationalError: duplicate column name:
 charFile_mycontribute" because the field was created twice.


 My guess:
 The original model is somewhere copied and the fields in _meta are not
 cleaned correctly.

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

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

Re: [Django] #20856: Error with admin popups: expected a character buffer object

2014-05-01 Thread Django

#20856: Error with admin popups: expected a character buffer object
-+-
 Reporter:  heppner.mark@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.6
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  admin, str,  | Triage Stage:
  character, inline, popup   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 1.5 is in security fix only mode. You can fix it by writing proper
 `__unicode__()` methods in your application as described above.

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

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

Re: [Django] #20856: Error with admin popups: expected a character buffer object

2014-05-01 Thread Django

#20856: Error with admin popups: expected a character buffer object
-+-
 Reporter:  heppner.mark@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  admin, str,  | Triage Stage:
  character, inline, popup   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by dloewenherz):

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


Comment:

 This bug still affects Django 1.5.6 as well. I think the fact that it
 affects two Django versions is enough reason to backport a fix. Thoughts?

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

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

Re: [Django] #22432: Switching model on an M2M field results in a broken db (no change to the automatic through table)

2014-05-01 Thread Django

#22432: Switching model on an M2M field results in a broken db (no change to the
automatic through table)
-+--
Reporter: melinath |Owner: timo
Type: Bug | Status: assigned
Component: Migrations | Version: 1.7-beta-1
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0| Needs documentation: 0
Needs tests: 0| Patch needs improvement: 0
Easy pickings: 0|UI/UX: 0
-+--

Comment (by timo):

[https://github.com/django/django/commit/a449e7fe#diff-
0c8f495bfee773ab7b5409533bd6d7efL164 The check here] prevents any action
from being taken if the many to many table name hasn't changed which is
the case if you simply change the model. I'm not sure exactly how we
should handle this as I would guess existing data should probably be
dropped. I checked how south handled this, but it looks like
`schemamigration --auto` doesn't detect a change if the `ManyToManyField`
model is changed.

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

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

Re: [Django] #22248: Model renaming doesn't work backwards

2014-05-01 Thread Django

#22248: Model renaming doesn't work backwards
--+
 Reporter:  andrewgodwin  |Owner:  andrewgodwin
 Type:  Bug   |   Status:  assigned
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by timo):

 There's a test in tests/migrations/test_operations.py
 (test_rename_model_with_related) that should be uncommented when this is
 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.299e7a6683d0bc60e14629f4d57bb4a0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22432: Switching model on an M2M field results in a broken db (no change to the automatic through table)

2014-05-01 Thread Django

#22432: Switching model on an M2M field results in a broken db (no change to the
automatic through table)
-+--
 Reporter:  melinath |Owner:  timo
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by timo):

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


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

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

Re: [Django] #22420: Postgresql connections not being dropped between tests?

2014-05-01 Thread Django

#22420: Postgresql connections not being dropped between tests?
---+--
 Reporter:  bacongobbler   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.6
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timo):

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


Comment:

 All right thanks, please reopen if you determine otherwise.

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

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

Re: [Django] #22420: Postgresql connections not being dropped between tests?

2014-05-01 Thread Django

#22420: Postgresql connections not being dropped between tests?
---+--
 Reporter:  bacongobbler   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.6
 Severity:  Normal |   Resolution:
 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 anonymous):

 Replying to [comment:7 anonymous]:
 > Replying to [comment:6 timo]:
 > > Any chance you could provide a minimal test project that reproduces
 the issue?
 > >
 > > Also you said, "A successful test run or a test run that produces
 error results will not produce the issue." but the example in the
 description doesn't appear to have any failures?
 >
 > Good points. I just tried again with a forced failure and an error. Now
 of course it appears to be reproducing in all 3 cases. (Fail, Error,
 Pass). Bah. I will try to get a GitHub project together and post back
 here.

 I have been trying to narrow this down by reproducing with a minimal
 project and eliminating variables one by one in the project with the
 error. I still haven't been able to get it to reproduce in the minimal
 project (https://github.com/WimpyAnalytics/djangobug22420). However I was
 able to determine that the problem only occurs on my larger project when
 all of the following circumstances are true:
 1. I am using a custom test runner (I have tried Django Nose and Django
 Juno)
 2. I am using Django Blog Zinnia
 3. I am using a Custom User Model

 Anyway, I think it's safe to say that my particular issue is not with
 Django itself.

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

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

Re: [Django] #22551: Oracle backend using bytes in isoformat

2014-05-01 Thread Django

#22551: Oracle backend using bytes in isoformat
-+-
 Reporter:  fatal10110@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:  oracle isoformat |  Unreviewed
  dates  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by Claude Paroz ):

 In [changeset:"d5a9d74eec66ce7e21eae2d9a5065fdd637333c5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d5a9d74eec66ce7e21eae2d9a5065fdd637333c5"
 [1.7.x] Fixed #22551 -- Made oracle backend method Python 3 compatible

 Thanks fatal10110 at gmail.com for the report. The fix is 1.6-only
 because that code has been refactored in 1.7 (6983201cfb).
 'Docs-only' forward port of 120a98120 from 1.6.x.
 }}}

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

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

Re: [Django] #22554: Typographical error in the tutorial

2014-05-01 Thread Django

#22554: Typographical error in the tutorial
---+--
 Reporter:  daniel@…   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timo):

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


Comment:

 What page is the error on? I don't see it in the tutorial for any
 supported version.

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

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

Re: [Django] #22551: Oracle backend using bytes in isoformat

2014-05-01 Thread Django

#22551: Oracle backend using bytes in isoformat
-+-
 Reporter:  fatal10110@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:  oracle isoformat |  Unreviewed
  dates  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by Claude Paroz ):

 In [changeset:"2ce51967638ac9f01c1c25bb33d51115ce99e0df"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2ce51967638ac9f01c1c25bb33d51115ce99e0df"
 Fixed #22551 -- Made oracle backend method Python 3 compatible

 Thanks fatal10110 at gmail.com for the report. The fix is 1.6-only
 because that code has been refactored in 1.7 (6983201cfb).
 'Docs-only' forward port of 120a98120 from 1.6.x.
 }}}

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

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

[django/django] 2ce519: Fixed #22551 -- Made oracle backend method Python ...

2014-05-01 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2ce51967638ac9f01c1c25bb33d51115ce99e0df
  
https://github.com/django/django/commit/2ce51967638ac9f01c1c25bb33d51115ce99e0df
  Author: Claude Paroz 
  Date:   2014-05-01 (Thu, 01 May 2014)

  Changed paths:
M docs/releases/1.6.5.txt

  Log Message:
  ---
  Fixed #22551 -- Made oracle backend method Python 3 compatible

Thanks fatal10110 at gmail.com for the report. The fix is 1.6-only
because that code has been refactored in 1.7 (6983201cfb).
'Docs-only' forward port of 120a98120 from 1.6.x.


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

[django/django] d5a9d7: [1.7.x] Fixed #22551 -- Made oracle backend method...

2014-05-01 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: d5a9d74eec66ce7e21eae2d9a5065fdd637333c5
  
https://github.com/django/django/commit/d5a9d74eec66ce7e21eae2d9a5065fdd637333c5
  Author: Claude Paroz 
  Date:   2014-05-01 (Thu, 01 May 2014)

  Changed paths:
M docs/releases/1.6.5.txt

  Log Message:
  ---
  [1.7.x] Fixed #22551 -- Made oracle backend method Python 3 compatible

Thanks fatal10110 at gmail.com for the report. The fix is 1.6-only
because that code has been refactored in 1.7 (6983201cfb).
'Docs-only' forward port of 120a98120 from 1.6.x.


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

[Django] #22554: Typographical error in the tutorial

2014-05-01 Thread Django

#22554: Typographical error in the tutorial
---+
 Reporter:  daniel@…   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 This question at stackoverflow summarizes the problem nicely:
 http://stackoverflow.com/questions/22768262/nameerror-not-defined

 polls/admin.py has a class called ChoiceInline, which is referenced in the
 PollAdmin class as ChoiceInLine (i.e., there's a big 'L' when there should
 be a little 'l', or vice versa)

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

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

Re: [Django] #22551: Oracle backend using bytes in isoformat

2014-05-01 Thread Django

#22551: Oracle backend using bytes in isoformat
-+-
 Reporter:  fatal10110@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:  oracle isoformat |  Unreviewed
  dates  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"120a981207aacb7453c0e064ec5b3d011ec68345"]:
 {{{
 #!CommitTicketReference repository=""
 revision="120a981207aacb7453c0e064ec5b3d011ec68345"
 [1.6.x] Fixed #22551 -- Made oracle backend method Python 3 compatible

 Thanks fatal10110 at gmail.com for the report. The fix is 1.6-only
 because that code has been refactored in 1.7 (6983201cfb).
 }}}

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

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

[django/django] 120a98: [1.6.x] Fixed #22551 -- Made oracle backend method...

2014-05-01 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 120a981207aacb7453c0e064ec5b3d011ec68345
  
https://github.com/django/django/commit/120a981207aacb7453c0e064ec5b3d011ec68345
  Author: Claude Paroz 
  Date:   2014-05-01 (Thu, 01 May 2014)

  Changed paths:
M django/db/backends/oracle/base.py
M docs/releases/1.6.5.txt

  Log Message:
  ---
  [1.6.x] Fixed #22551 -- Made oracle backend method Python 3 compatible

Thanks fatal10110 at gmail.com for the report. The fix is 1.6-only
because that code has been refactored in 1.7 (6983201cfb).


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

Re: [Django] #22549: DateTimeField raises timezone awareness related RuntimeWarnings when it should'nt

2014-05-01 Thread Django

#22549: DateTimeField raises timezone awareness related RuntimeWarnings when it
should'nt
-+-
 Reporter:  matias@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 Look two lines above -- the complete code is:

 {{{
 if isinstance(value, datetime.datetime):
 return value
 if isinstance(value, datetime.date):
 # ... stuff you complain about
 }}}

 If value is a `datetime.datetime` the fist branch returns, you don't hit
 the second 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/075.1f91d503dec353163d0912102eac8950%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22553: Add ability to refresh queryset

2014-05-01 Thread Django

#22553: Add ability to refresh queryset
-+-
 Reporter:  giggaflop@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (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 aaugustin):

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


Comment:

 Maybe `_clone()` already does what you need.

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

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

Re: [Django] #22551: Oracle backend using bytes in isoformat

2014-05-01 Thread Django

#22551: Oracle backend using bytes in isoformat
-+-
 Reporter:  fatal10110@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  oracle isoformat |  Unreviewed
  dates  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by fatal10110@…):

 Replying to [comment:1 manfre]:
 > For Python 2.7, without the '''b''':
 >
 > {{{
 > TypeError: isoformat() argument 1 must be char, not unicode
 > }}}

 oops, I did not read well your comment

 I'm using Python 3 and its ok without the '''b''' ...

 But if you will check the python documentation you will see that no matter
 wich version of python, they are using it without the '''b'''

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

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

Re: [Django] #22551: Oracle backend using bytes in isoformat

2014-05-01 Thread Django

#22551: Oracle backend using bytes in isoformat
-+-
 Reporter:  fatal10110@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  oracle isoformat |  Unreviewed
  dates  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by fatal10110@…):

 Replying to [comment:1 manfre]:
 > For Python 2.7, without the '''b''':
 >
 > {{{
 > TypeError: isoformat() argument 1 must be char, not unicode
 > }}}

 Python 2.7 + ?

 We are running django on Python 3...

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

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

Re: [Django] #22551: Oracle backend using bytes in isoformat

2014-05-01 Thread Django

#22551: Oracle backend using bytes in isoformat
-+-
 Reporter:  fatal10110@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  oracle isoformat |  Unreviewed
  dates  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by manfre):

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


Comment:

 For Python 2.7, without the '''b''':

 {{{
 TypeError: isoformat() argument 1 must be char, not unicode
 }}}

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

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

Re: [Django] #22395: Deleting a model and fields that relate to it results in ValueError: Related model '.' cannot be resolved

2014-05-01 Thread Django

#22395: Deleting a model and fields that relate to it results in ValueError:
Related model '.' cannot be resolved
+--
 Reporter:  melinath|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7-beta-1
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by timo):

 @melinath, could you check if this is still an issue as the ticket you
 referenced above has been resolved? If it still is, some steps to
 reproduce would be helpful, as it will be easier than reversing them from
 the details you've provided.

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

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

Re: [Django] #22552: 1.7 beta 3 regression - BoundField.value() tries to call GenericRelatedObjectManager instance without args

2014-05-01 Thread Django

#22552: 1.7 beta 3 regression - BoundField.value() tries to call
GenericRelatedObjectManager instance without args
-+-
 Reporter:  stephenmcd   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:
  contrib.contenttypes   |  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by stephenmcd):

 Also yes I've been referring to GenericRelation as GFK which really
 confuses things, sorry about that!

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

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

Re: [Django] #22411: Migrations attempt to create content types without first running contenttypes sync/migrations

2014-05-01 Thread Django

#22411: Migrations attempt to create content types without first running
contenttypes sync/migrations
+--
Reporter: melinath|Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7-beta-1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 |UI/UX: 0
+--
Changes (by timo):

* cc: timo (added)

Comment:

I don't think adding a dependency on `contenttypes` would be wise since
the app should be optional and if we added that then if
`django.contrib.contenttypes` isn't in `INSTALLED_APPS`, you'd get an
error when migrating: `ValueError: Dependency on unknown app
contenttypes`. This raises a more general issue that unlike the
`post_syncdb` signal, when `post_migrate` is fired there's no guarantee
that the tables for all other apps will exist. I'm not sure if there's an
existing method to check whether or not a model's table has been created.

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

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

Re: [Django] #22552: 1.7 beta 3 regression - BoundField.value() tries to call GenericRelatedObjectManager instance without args

2014-05-01 Thread Django

#22552: 1.7 beta 3 regression - BoundField.value() tries to call
GenericRelatedObjectManager instance without args
-+-
 Reporter:  stephenmcd   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:
  contrib.contenttypes   |  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by stephenmcd):

 Sorry I really rushed the bug report.

 Some useful context might be where a related issue came up and was
 resolved as part of the 1.6.1 bugfix release:
 https://code.djangoproject.com/ticket/21428

 Again that was for the example with GFKs using custom form fields in the
 admin,something Mezzanine has made heavy use of for a few years now.

 I'm not sure how useful it will be to go over the Mezzanine code base,
 it's a very complex example. I might be able to dig up the old example we
 had for #21428 - either way it will take me some time.

 Anyway here are the relevant parts:

 Here is our GFK field:
 
https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/generic/fields.py#L164

 Here is a base model that many subclass, eventually using it:
 
https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/core/models.py#L125

 Here is an admin class with the above field in its fieldsets:
 
https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/core/admin.py#L34-L52

 And finally, here is the actual widget that the admin's form will use for
 the GFK:
 
https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/generic/forms.py#L18

 As you can see there are a significant number of layers to this and so
 without knowing much about Mezzanine I fear going over its code might not
 prove very useful. Again, I'll try and come up with a minimal code example
 if I can, it might just take me some time. Alternatively it's quite easy
 to reproduce this by installing the current master branch of Mezzanine
 from GitHub and running one of these admin change interfaces against
 Django 1.7 beta.

 The guts of it is though it's always been possible for GFK fields to be
 exposed as form fields in the admin given a custom widget, and this has
 regressed due to the new `__call__` implementation, and that one extra
 check in `BoundField.value()` will resolve it at least.

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

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

Re: [Django] #22170: Add initial migrations for contrib apps

2014-05-01 Thread Django

#22170: Add initial migrations for contrib apps
-+-
 Reporter:  timo |Owner:
 Type:  New feature  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

 * stage:  Accepted => Ready for checkin


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

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

[django/django] d56267: [1.7.x] Fixed #22539 -- Copied exclude argument in...

2014-05-01 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: d56267ba57f28395946fadd6401ad7e1606c3cb0
  
https://github.com/django/django/commit/d56267ba57f28395946fadd6401ad7e1606c3cb0
  Author: Yehonatan Daniv 
  Date:   2014-05-01 (Thu, 01 May 2014)

  Changed paths:
M django/db/models/base.py
M tests/validation/__init__.py
M tests/validation/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #22539 -- Copied exclude argument in Model.full_clean() to 
prevent side effects.

Backport of e2e4cdba11 from master


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

Re: [Django] #22539: Model.full_clean() mutates exclude argument

2014-05-01 Thread Django

#22539: Model.full_clean() mutates exclude argument
-+-
 Reporter:  maggotfish@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by Tim Graham ):

 In [changeset:"d56267ba57f28395946fadd6401ad7e1606c3cb0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d56267ba57f28395946fadd6401ad7e1606c3cb0"
 [1.7.x] Fixed #22539 -- Copied exclude argument in Model.full_clean() to
 prevent side effects.

 Backport of e2e4cdba11 from master
 }}}

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

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

Re: [Django] #22539: Model.full_clean() mutates exclude argument

2014-05-01 Thread Django

#22539: Model.full_clean() mutates exclude argument
-+-
 Reporter:  maggotfish@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"e2e4cdba1178ebcfd95c19eb063abd55b4afbcbb"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e2e4cdba1178ebcfd95c19eb063abd55b4afbcbb"
 Fixed #22539 -- Copied exclude argument in Model.full_clean() to prevent
 side effects.
 }}}

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

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

[django/django] e2e4cd: Fixed #22539 -- Copied exclude argument in Model.f...

2014-05-01 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e2e4cdba1178ebcfd95c19eb063abd55b4afbcbb
  
https://github.com/django/django/commit/e2e4cdba1178ebcfd95c19eb063abd55b4afbcbb
  Author: Yehonatan Daniv 
  Date:   2014-05-01 (Thu, 01 May 2014)

  Changed paths:
M django/db/models/base.py
M tests/validation/__init__.py
M tests/validation/tests.py

  Log Message:
  ---
  Fixed #22539 -- Copied exclude argument in Model.full_clean() to prevent side 
effects.


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

Re: [Django] #22051: Running `makemigrations` twice in a row fails

2014-05-01 Thread Django

#22051: Running `makemigrations` twice in a row fails
-+
 Reporter:  bmispelon|Owner:  andrewgodwin
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by timo):

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


Comment:

 I think the bases error is a duplicate of #22447 as I cannot reproduce the
 error with the models in comment 7 and 9 on the latest master. Please open
 a new ticket if there are other issues.

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

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

Re: [Django] #22435: Adding a ManyToManyField and running makemigrations prompts for a default

2014-05-01 Thread Django

#22435: Adding a ManyToManyField and running makemigrations prompts for a 
default
-+
 Reporter:  andrewsg |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   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 timo):

 * has_patch:  0 => 1
 * severity:  Normal => Release blocker


Comment:

 I didn't see a way to do this without special casing M2M:
 [https://github.com/django/django/pull/2625 PR].

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

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

Re: [Django] #22416: Migrate can't create ManyToManyField for Model migrated in the same run (was: Migrate can't create ManyToManyField for Model wigrated in the same run)

2014-05-01 Thread Django

#22416: Migrate can't create ManyToManyField for Model migrated in the same run
-+-
 Reporter:  roughdesignapps@…|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Migrations   |  1.7-alpha-2
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 I tried reproducing the second issue this based on the given info but
 could not. Please reopen if you can reproduce on the latest master or
 1.7.x with additional 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/083.0054edc7f25bbc1479553739b3cadcf5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22539: Model.full_clean() mutates exclude argument

2014-05-01 Thread Django

#22539: Model.full_clean() mutates exclude argument
-+-
 Reporter:  maggotfish@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by maggotfish@…):

 * has_patch:  0 => 1


Comment:

 PR here: https://github.com/django/django/pull/2622

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

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

Re: [Django] #22552: 1.7 beta 3 regression - BoundField.value() tries to call GenericRelatedObjectManager instance without args

2014-05-01 Thread Django

Comment (by loic84):

Putting `and not getattr(data, "do_not_call_in_templates", False)` in
`BoundField.value()` is ugly since this it's outside the template system.

I don't quite understand how you can provide a custom widget for GFK, it's
a virtual field, it doesn't implement a `formfield` method, and it doesn't
even inherit it from `models.Field` since it subclasses `object` directly.

Real support for virtualfields hasn't landed in Django yet (refs
https://github.com/konk/django/tree/soc2013/composite-fields).

Also GenericRelatedObjectManager is from `GenericRelation` not
`GenericForeignKey`.

Could you provide more context? Maybe some examples or pointers to the
mezzanine codebase?

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

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

[Django] #22553: Add ability to refresh queryset

2014-05-01 Thread Django

#22553: Add ability to refresh queryset
--+
 Reporter:  giggaflop@…   |  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.6
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 I propose adding a Queryset method '.refresh()' which will clear the
 built-in cache on any queryset passed to it.

 I suggest an initial implementation of:


 {{{
 def refresh(self, *args, **kwargs):
 """
 Returns a new QuerySet instance with the args ANDed to the
 existing
 set.
 """
 self._result_cache = None
 return self
 }}}

 Reason this is requested:

 When I'm using modelformsets I typically find the need to refresh the
 queryset that is used by the ModelFormset.

 To do this I perform the following action:


 {{{
 updated_formset = ConciergeUserPoolFormset(request.POST)
 if updated_formset.is_valid():
 updated_formset.save()
 queryset = updated_formset.get_queryset()
 # we need an updated queryset, not the cached version. set the
 results cache to None to force re-fetch
 queryset._result_cache = None
 updated_formset = ConciergeUserPoolFormset(queryset=queryset)
 }}}

 This is not an obvious solution to the issue of updating a ModelFormset or
 forcing a queryset update in general, it also uses a private method of the
 Queryset object which I would prefer to avoid.

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

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

Re: [Django] #22263: KeyError: 'to' in MigrationAutodetector with uncommon rel.to setup (django-taggit)

2014-05-01 Thread Django

#22263: KeyError: 'to' in MigrationAutodetector with uncommon rel.to setup 
(django-
taggit)
+
 Reporter:  blueyed |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by timo):

 * easy:  1 => 0


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

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

Re: [Django] #21638: Infinite migrations when using AUTH_USER_MODEL

2014-05-01 Thread Django

#21638: Infinite migrations when using AUTH_USER_MODEL
-+-
 Reporter:  patrick@…|Owner:  Andrew
 Type:  Bug  |  Godwin 
Component:  Migrations   |   Status:  closed
 Severity:  Normal   |  Version:  master
 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 timo):

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


Comment:

 With the latest master and stable/1.7.x I cannot reproduce infinite
 migrations given the above code.

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

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

Re: [Django] #22552: 1.7 beta 3 regression - BoundField.value() tries to call GenericRelatedObjectManager instance without args

2014-05-01 Thread Django

#22552: 1.7 beta 3 regression - BoundField.value() tries to call
GenericRelatedObjectManager instance without args
-+-
 Reporter:  stephenmcd   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:
  contrib.contenttypes   |  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

 * severity:  Normal => Release blocker
 * cc: loic84 (added)
 * needs_better_patch:   => 0
 * component:  Uncategorized => contrib.contenttypes
 * needs_tests:   => 0
 * needs_docs:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Change is 04a2a6b0f9cb6bb98edfe84bf4361216d60a4e38. What do you think
 Loic?

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

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

Re: [Django] #22545: Ticket spam catcher doesn't validate me as human (and does arithmetic wrong)

2014-05-01 Thread Django

#22545: Ticket spam catcher doesn't validate me as human (and does arithmetic
wrong)
-+-
 Reporter:  bjb@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  *.djangoproject.com  |  Version:  1.6
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 It's still more difficult for a human than for a computer :-(

 I wish we had a better solution, or fewer than a thousand daily spam
 attempts.

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

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

Re: [Django] #19457: ImageField size detection fails for some files even when PIL could succeed

2014-05-01 Thread Django

#19457: ImageField size detection fails for some files even when PIL could 
succeed
--+
 Reporter:  melinath  |Owner:  bak1an
 Type:  Bug   |   Status:  closed
Component:  File uploads/storage  |  Version:  1.4
 Severity:  Normal|   Resolution:  fixed
 Keywords:  image | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by aaugustin):

 Only security fixes get backported.

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

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

[Django] #22552: 1.7 beta 3 regression - BoundField.value() tries to call GenericRelatedObjectManager instance without args

2014-05-01 Thread Django

#22552: 1.7 beta 3 regression - BoundField.value() tries to call
GenericRelatedObjectManager instance without args
---+
Reporter: stephenmcd | Owner: nobody
Type: Bug| Status: new
Component: Uncategorized |Version: 1.7-beta-2
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
---+
In Mezzanine we have a form widget for GFK fields. With Django 1.7 beta 3,
we get the following error:

http://hastebin.com/qixuzotumi.mel

AFAICT: In Django 1.6, `GenericRelatedObjectManager` was not callable, but
in 1.7 it implements `__call__`. `BoundField.value()` then calls an
instance of it without args, but `GenericRelatedObjectManager.__call__`
expects a `manager` arg. `GenericRelatedObjectManager` also implements
`do_not_call_in_templates`, which seems appropriate here. If I change
`BoundField.value()` callable check to include `and not getattr(data,
"do_not_call_in_templates", False)` then it resolves the issue.

Happy to submit a patch if this sounds like the correct fix - really not
sure though, quite out of my depth.

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

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

[Django] #22551: Oracle backend using bytes in isoformat

2014-05-01 Thread Django

#22551: Oracle backend using bytes in isoformat
--+
 Reporter:  fatal10110@…  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.6
 Severity:  Normal|   Keywords:  oracle
 Triage Stage:  Unreviewed|  isoformat dates
Easy pickings:  1 |  Has patch:  0
  |  UI/UX:  0
--+
 Hi , seems like we have some micro bug here, using oracle + django-celery
 :


 {{{
  File "-/site-packages/django/db/backends/oracle/base.py", line 449, in
 year_lookup_bounds_for_datetime_field
 return [b.isoformat(b' ') for b in bounds]

   File "-/site-packages/django/db/backends/oracle/base.py", line 449, in
 
 return [b.isoformat(b' ') for b in bounds]

 TypeError: isoformat() argument 1 must be a unicode character, not bytes
 }}}

 The reason of the excetion is "date_hierarchy" in admin part of django-
 celery


 {{{
 date_hierarchy = 'tstamp'
 }}}


 But it should work , beacause in models all is fine


 {{{
 tstamp = models.DateTimeField(_('event received at'), db_index=True)
 }}}

 From django documentation: " Set date_hierarchy to the name of a DateField
 or '''DateTimeField''' in your model, and the change list page will
 include a date-based drilldown navigation by that field."

 The code in oracle/base.py


 {{{
 def year_lookup_bounds_for_datetime_field(self, value):
 # The default implementation uses datetime objects for the bounds.
 # This must be overridden here, to use a formatted date (string)
 as
 # 'second' instead -- cx_Oracle chops the fraction-of-second part
 # off of datetime objects, leaving almost an entire second out of
 # the year under the default implementation.
 bounds = super(DatabaseOperations,
 self).year_lookup_bounds_for_datetime_field(value)
 if settings.USE_TZ:
 bounds = [b.astimezone(timezone.utc).replace(tzinfo=None) for
 b in bounds]
 return [b.isoformat(b' ') for b in bounds]

 }}}

 Example from python documentantion of how to use the isoformat() method:


 {{{
 datetime(2002, 12, 25, tzinfo=TZ()).isoformat(' ')
 }}}


 They are not using '''b''' to convert the seperator to bytes..

 Should I remove the b or it's important ?

 Thanks.

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

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

Re: [Django] #22328: Add --exclude option to compilemessages

2014-05-01 Thread Django

Comment (by loic84):

The `-e` shorthand introduced for `makemessages --exclude` caused a
regression due to a conflict with the existing `makemessages
--extensions`.

Refs https://groups.google.com/d/topic/django-
developers/a7jksjMWmbY/discussion.

Backward compatible options are:
1. no shorthand at all for the two commands.
2. no shorthand for `makemessages`.
3. change both shorthands to -x (eXclude).

I went with option 3 in https://github.com/django/django/pull/2621,
feedback 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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.80bcd8e828774da6d306b4a870473288%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

59 matches

Mail list logo