date:20140212

Re: [Django] #19195: Using distinct([*fields]) filter on a foreign key produces an ordering error when the foreign key has a Meta ordering field.

2014-02-12 Thread Django

#19195: Using distinct([*fields]) filter on a foreign key produces an ordering
error when the foreign key has a Meta ordering field.
-+-
 Reporter:  chrisedgemon@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  distinct, query  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by charettes):

 * cc: charettes (added)


Old description:

> I tried to using a distinct filter like this:
> Appearance.objects.order_by('team').distinct('team'); this fails with the
> following Database Error: "DatabaseError: SELECT DISTINCT ON expressions
> must match initial ORDER BY expressions"
>
> It is possible to work around this problem by using this modified filter:
> Appearance.objects.order_by('team__id').distinct('team__id').
>
> Model definition: http://pastebin.com/index/J45fy9fr
> Full traceback: http://pastebin.com/feSFMbzX

New description:

 I tried to using a distinct filter like this:
 Appearance.objects.order_by('team').distinct('team'); this fails with the
 following Database Error: "DatabaseError: SELECT DISTINCT ON expressions
 must match initial ORDER BY expressions"

 It is possible to work around this problem by using this modified filter:
 `Appearance.objects.order_by('team__id').distinct('team__id')`.

 Model definition: http://pastebin.com/index/J45fy9fr
 Full traceback: http://pastebin.com/feSFMbzX

--

Comment:

 Just hit this issue and had a hard time figuring out what I've done wrong.

 Intuitively I tried `.distinct('related_id').order_by('related_id')` after
 realizing removing my `Related._meta.ordering` solved the issue but, as
 pointed out by akaariai, this is not allowed ATM.

 Replying to [comment:3 akaariai]:
 > I think we should allow using .order_by('team_id') here.
 >
 > Related fields have two attributes on model level - team and team_id in
 this case. We allow using team_id in many places in the ORM already, and
 to me it seems we should allow it in order_by and distinct, too.
 >
 > Is there some reason to *not* allow them?

 I can't think of any reason we'd like *not* to allow them. It looks like
 sanest to expose an API to explicitly opt-out of the existing related
 model ordering behavior while maintaining backward compatibility.

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

Re: [Django] #22033: 'Model' object has no attribute 'replace'

2014-02-12 Thread Django

#22033: 'Model' object has no attribute 'replace'
---+--
 Reporter:  strelnikovdmitrij  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Utilities  |  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 strelnikovdmitrij):

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


Comment:

 I'm stupid, cycling references, sorry guys

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

Re: [Django] #22022: Allow field subclasses to require additional SQL

2014-02-12 Thread Django

#22022: Allow field subclasses to require additional SQL
-+-
 Reporter:  mjtamlyn |Owner:  nobody
 Type:  New feature  |   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:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by russellm):

 * stage:  Unreviewed => Accepted


Comment:

 In principle, sounds like a reasonable proposition to me. There's clearly
 some discussion happening on the pull request, but I suspect that this
 will only shape the final form of the feature, not the base functionality.

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

Re: [Django] #22033: 'Model' object has no attribute 'replace'

2014-02-12 Thread Django

#22033: 'Model' object has no attribute 'replace'
---+--
 Reporter:  strelnikovdmitrij  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Utilities  |  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
---+--
Changes (by strelnikovdmitrij):

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


Comment:

 models are ok

 class AddressManager(models.Manager):
 def get_queryset(self):
 return QuerySet(self.model, using=self._db)

 def address_for_object(self, obj):
 object_type = ContentType.objects.get_for_model(obj)
 return self.get_queryset().filter(content_type__pk=object_type.id,
 object_id=obj.id)

 class Address(models.Model):
 objects = AddressManager()

 content_type = models.ForeignKey(ContentType, editable=False)
 object_id = models.PositiveIntegerField(editable=False)
 content_object = generic.GenericForeignKey()

 type = models.IntegerField(choices=AddressType.CHOICES)

 country = models.CharField(max_length=2, choices=COUNTRIES_SHORT)
 city = models.CharField(max_length=60)
 city_id = models.IntegerField(default=0, editable=False)
 city_part = models.CharField(max_length=60, blank=True)
 district = models.CharField(max_length=60, blank=True)
 street = models.CharField(max_length=120)
 street_number = models.CharField(max_length=10)
 house_number = models.CharField(max_length=10, blank=True)
 postal_code = models.CharField(max_length=5)

 # @property
 # def get_street(self):
 # return '%s %s' % (self.street, self.get_street_number())
 #
 # def get_street_number(self):
 # if self.house_number:
 # return '%s/%s' % (self.street_number, self.house_number)
 # return '%s' % self.street_number
 #
 @classmethod
 def types(cls):
 return AddressType
 #
 # def clean(self):
 # self.content_object = Company.objects.get(pk=1)

 # def __unicode__(self):
 # return self.country
 # return smart_text('%s, %s, %s' % (self.street, self.city,
 self.country))


 # def __str__(self):
 # return smart_text('%s, %s, %s' % (self.street, self.city,
 self.country))

 if I create model with data loaded from web (xml, parsed) and save, it
 return this error on trying to delete via admin.
 if I create model with data hardcoded in view and save, it return this
 error on trying to delete via admin.
 If I create model thru admin, with the same values, everything is ok.

 fiedls with chars Řeporje, or Smíchov

 I did some research.
 fields from views - are contains data in unicode with \u09 chars and
 failed on display
 fields created thru admin contains data in str (or unicode) but contains
 data with \x03..chars

 I can edit model, can delete thru shell, everything works. But on trying
 to delete raise exception, on putting to choices to field, also raise
 exception

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

Re: [Django] #22033: 'Model' object has no attribute 'replace'

2014-02-12 Thread Django

#22033: 'Model' object has no attribute 'replace'
---+--
 Reporter:  strelnikovdmitrij  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Utilities  |  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 bmispelon):

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


Comment:

 Hi,

 It's hard to say without seeing your `models.py` but you most likely have
 an issue with one of your models' `__unicode__` method (or `__str__` if
 you're using Python 3).

 I'll mark this as `invalid`. Please provide your `models.py` if you reopen
 it.

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

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

2014-02-12 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
-+-

Comment (by anonymous):

 Having the same issue as the above about admin pop ups.

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

Re: [Django] #21856: Crash when DATABASES = {}

2014-02-12 Thread Django

#21856: Crash when DATABASES = {}
-+
 Reporter:  aaugustin|Owner:  andrewgodwin
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 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 Andrew Godwin ):

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


Comment:

 In [changeset:"f0f1ba75b090e533c1b39f516cea2d9a15307ac3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f0f1ba75b090e533c1b39f516cea2d9a15307ac3"
 Fixed #21856: Don't crash runserver when DATABASES = {}
 }}}

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

[django/django] 7e941b: Reverting unapplied migrations check away from bei...

2014-02-12 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7e941ba67ceab8a74ba50509d13ed4298f8305cd
  
https://github.com/django/django/commit/7e941ba67ceab8a74ba50509d13ed4298f8305cd
  Author: Andrew Godwin 
  Date:   2014-02-12 (Wed, 12 Feb 2014)

  Changed paths:
M django/core/checks/__init__.py
R django/core/checks/migrations.py
M django/core/management/commands/runserver.py

  Log Message:
  ---
  Reverting unapplied migrations check away from being a system-level check.

This reverts commit 0ac13eccebb3d879f79b31585b1e81f655067179.


  Commit: f0f1ba75b090e533c1b39f516cea2d9a15307ac3
  
https://github.com/django/django/commit/f0f1ba75b090e533c1b39f516cea2d9a15307ac3
  Author: Andrew Godwin 
  Date:   2014-02-12 (Wed, 12 Feb 2014)

  Changed paths:
M django/core/management/commands/runserver.py

  Log Message:
  ---
  Fixed #21856: Don't crash runserver when DATABASES = {}


Compare: https://github.com/django/django/compare/dbe82e74f2ed...f0f1ba75b090

-- 
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/52fbc70c335e3_948c9fd3855980%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22033: 'Model' object has no attribute 'replace'

2014-02-12 Thread Django

#22033: 'Model' object has no attribute 'replace'
---+
 Reporter:  strelnikovdmitrij  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Utilities  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 ..dev/django/django/utils/html.py in escape

 def escape(text):
 """
 Returns the given text with ampersands, quotes and angle brackets
 encoded for use in HTML.
 """
 return mark_safe(force_text(text).replace('&', '&').replace('<',
 '<').replace('>', '>').replace('"', '"').replace("'", '''))
 ...
 escape = allow_lazy(escape, six.text_type)

 local vars
 VariableValue
 text
 Error in formatting: coercing to Unicode: need string or buffer, Object
 found

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

Re: [Django] #21856: Crash when DATABASES = {}

2014-02-12 Thread Django

#21856: Crash when DATABASES = {}
-+
 Reporter:  aaugustin|Owner:  andrewgodwin
 Type:  Bug  |   Status:  assigned
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 andrewgodwin):

 * owner:  Andrew Godwin  => andrewgodwin
 * status:  new => assigned


Comment:

 On the contrary, I think this is only relevant when running ``runserver``
 - not having applied migrations is a valid state for a Django project and
 is only really of concern if you are trying to run the website and
 interact with it (and even then you might want it).

 I'm going to move it back from being a check and fix it a different way.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.ba67ce1146bd60b4e96aebd8fdc6ce7f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] b333de: Add --empty option to makemigrations

2014-02-12 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b333de0f5dc6e66bd77cce9ffe0eef06a9e31f02
  
https://github.com/django/django/commit/b333de0f5dc6e66bd77cce9ffe0eef06a9e31f02
  Author: Andrew Godwin 
  Date:   2014-02-12 (Wed, 12 Feb 2014)

  Changed paths:
M django/core/management/commands/makemigrations.py

  Log Message:
  ---
  Add --empty option to makemigrations


  Commit: 80bbe2265d1afd43f8519427ad8ce0b147aceb43
  
https://github.com/django/django/commit/80bbe2265d1afd43f8519427ad8ce0b147aceb43
  Author: Andrew Godwin 
  Date:   2014-02-12 (Wed, 12 Feb 2014)

  Changed paths:
M django/db/migrations/operations/special.py

  Log Message:
  ---
  Remove redunant code from RunPython operation


  Commit: bad9456b9cabd6a14fe6e3edeacde55b51fbffdc
  
https://github.com/django/django/commit/bad9456b9cabd6a14fe6e3edeacde55b51fbffdc
  Author: Andrew Godwin 
  Date:   2014-02-12 (Wed, 12 Feb 2014)

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

  Log Message:
  ---
  Fix my slightly hasty autodetector changes


  Commit: dbe82e74f2ed4ae2f63247af75161ad00ab34a44
  
https://github.com/django/django/commit/dbe82e74f2ed4ae2f63247af75161ad00ab34a44
  Author: Andrew Godwin 
  Date:   2014-02-12 (Wed, 12 Feb 2014)

  Changed paths:
M docs/index.txt
A docs/ref/migration-operations.txt
A docs/ref/schema-editor.txt
M docs/topics/migrations.txt

  Log Message:
  ---
  Add reference documentation for operations and stubs for schemaeditor.


Compare: https://github.com/django/django/compare/7e27885c6e75...dbe82e74f2ed

-- 
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/52fbc3497fb15_948c9fd3855583%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21856: Crash when DATABASES = {}

2014-02-12 Thread Django

#21856: Crash when DATABASES = {}
-+-
 Reporter:  aaugustin|Owner:  Andrew
 Type:  Bug  |  Godwin 
Component:  Migrations   |   Status:  new
 Severity:  Release blocker  |  Version:  master
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by mlavin):

 I wasn't seeing this when running the Django test suite. I see this
 warning is also issued when you run {{{migrate}}} from #22031 which isn't
 wanted. I don't agree with the resolution that this doesn't belong in the
 checks framework. This fits precisely into its stated purpose.

 > The system check framework is a set of static checks for validating
 Django projects. It detects common problems and provides hints for how to
 fix them.

 There should be a way to suppress this check when it is not known to not
 be relevant such was when running {{{migrate}}}.

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

Re: [Django] #22002: AppConfig.ready() and tests

2014-02-12 Thread Django

Comment (by mjtamlyn):

I discovered this accidentally investigating (bad) solutions for #22022. I
propose just docs. At the moment, `manage.py test` is not special cased in
the core management. We call `django.setup()` and then branch on the
command used. I think that we should:

1) recommend never interacting with the database in `ready()` (or in
startup code in general - this is what migrations are for right?)
2) mention that it would be run against the main database even in testing

I don't think it's actually that big a deal about the test/prod situation.
Such code would be run *every time* you call a management command of any
kind, so you'd soon find out if you were breaking the db. We could
theoretically explicitly error during the calls to `ready()` if we try to
obtain a connection cursor, but that would be a bit dirty in its
implementation.

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

Re: [Django] #22031: Checks framework complains about unapplied migrations when running `manage.py migrate`

2014-02-12 Thread Django

#22031: Checks framework complains about unapplied migrations when running
`manage.py migrate`
-+--
 Reporter:  bmispelon|Owner:
 Type:  New feature  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by mjtamlyn):

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


Comment:

 This is effectively a duplicate of #21856 - this warning should not be
 part of the checks framework.

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

Re: [Django] #22032: Document settings.MIGRATION_MODULES

2014-02-12 Thread Django

#22032: Document settings.MIGRATION_MODULES
--+
 Reporter:  bmispelon |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Release blocker   |   Resolution:
 Keywords:  migrations| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by mjtamlyn):

 * severity:  Normal => Release blocker


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

[Django] #22032: Document settings.MIGRATION_MODULES

2014-02-12 Thread Django

#22032: Document settings.MIGRATION_MODULES
-+-
   Reporter:  bmispelon  |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |Version:  master
  Component: |   Keywords:  migrations
  Documentation  |  Has patch:  0
   Severity:  Normal |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  1
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 There's no mention of this new setting in the documentation.

 From what I understand, it's a way to override where Django can find
 migrations for a given app.

 It's a dictionary where keys are the names of applications and the values
 are the name of the module (inside the app) where the migrations reside.

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

[Django] #22031: Checks framework complains about unapplied migrations when running `manage.py migrate`

2014-02-12 Thread Django

#22031: Checks framework complains about unapplied migrations when running
`manage.py migrate`
---+
   Reporter:  bmispelon|  Owner:
   Type:  New feature  | Status:  new
  Component:  Migrations   |Version:  master
   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|
---+
 Suppose you've created a new application with some models and you've
 subsequently run `manage.py makemigrations`.

 The next step is to run `manage.py migrate`.

 When you do that, the first thing that you see is the checks framework
 telling you that you have unapplied migrations and that you should run
 `manage.py migrate`.

 That doesn't seem very helpful and I think it'd be better in this case to
 not output anything.

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

Re: [Django] #22030: AttributeError: 'CharField' object has no attribute 'swappable_setting'

2014-02-12 Thread Django

#22030: AttributeError: 'CharField' object has no attribute 'swappable_setting'
-+---
 Reporter:  bmispelon|Owner:
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-alpha-1
 Severity:  Release blocker  |   Resolution:
 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 bmispelon):

 * version:  1.6 => 1.7-alpha-1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.b3c5a2a5971ea178277252acbf49ea1d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22030: AttributeError: 'CharField' object has no attribute 'swappable_setting'

2014-02-12 Thread Django

#22030: AttributeError: 'CharField' object has no attribute 'swappable_setting'
---+-
   Reporter:  bmispelon|  Owner:
   Type:  Bug  | Status:  new
  Component:  Migrations   |Version:  1.6
   Severity:  Release blocker  |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+-
 Here's how to reproduce:

 Create an app with a simple `models.py` (and put it in
 `settings.INSTALLED_APPS`):
 {{{#!python
 from django.db import models

 class Foo(models.Model):
 pass
 }}}

 Run `makemigrations` and then `migrate`.

 Then change the `Foo` model to be:
 {{{#!python
 class Foo(models.Model):
 foo = models.CharField(max_length=10, default='')
 }}}

 After that, running `manage.py makemigrations` breaks with the following
 traceback:
 {{{
 Traceback (most recent call last):
   File "manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "./django/core/management/__init__.py", line 427, in
 execute_from_command_line
 utility.execute()
   File "./django/core/management/__init__.py", line 419, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "./django/core/management/base.py", line 287, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "./django/core/management/base.py", line 336, in execute
 output = self.handle(*args, **options)
   File "./django/core/management/commands/makemigrations.py", line 80, in
 handle
 changes = autodetector.changes(graph=loader.graph,
 trim_to_apps=app_labels or None)
   File "./django/db/migrations/autodetector.py", line 33, in changes
 changes = self._detect_changes()
   File "./django/db/migrations/autodetector.py", line 236, in
 _detect_changes
 swappable_setting = new_apps.get_model(app_label,
 model_name)._meta.get_field_by_name(field_name)[0].swappable_setting
 AttributeError: 'CharField' object has no attribute 'swappable_setting'
 }}}

 Breakage was introduced in commit
 11c021336c8cb1c92be998f1a44c89a746275107.

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

Re: [Django] #22023: .values() followed by defer() or only() results invalid data or crash

2014-02-12 Thread Django

#22023: .values() followed by defer() or only() results invalid data or crash
-+-
 Reporter:  jtiai|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  orm  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Lauxley):

 I was curious so i tracked down the issue,
 the iterator() method of the ValuesQuerySet doesn't use the
 deferred_loading attribute of the query, even though the docstring of
 Query.deferred_to_data says that :
 "This [self.deferred_loading] is used to compute the columns to select
 from the database and also by the QuerySet class to work out which fields
 are being initialised on each model."

 So a quick patch (django 1.4.5)
 {{{#!python
 @@ -956,7 +956,14 @@
  def iterator(self):
  # Purge any extra columns that haven't been explicitly asked for
  extra_names = self.query.extra_select.keys()
 -field_names = self.field_names
 +deferred_fields, defer = self.query.deferred_loading
 +if deferred_fields:
 +if not defer:
 +field_names = list(deferred_fields)
 +else:
 +field_names = list(set(self.field_names) -
 deferred_fields)
 +else:
 +field_names = self.field_names
  aggregate_names = self.query.aggregate_select.keys()

  names = extra_names + field_names + aggregate_names
 }}}

 This is probably not the 'right' way to do it, only an hint.
 I strongly feel that this should not be computed in the iterator method,
 i'm not even sure why the QuerySet class would need to do it itself, but
 i'm probably missing something.

 Note:
 .values('field_a').only('field_b') and .values('field_a').defer('field_a')
 will still raise a DatabaseError, but i think it's fine in this case.

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

Re: [Django] #22029: documentation: new best place to put the signal handler registration

2014-02-12 Thread Django

#22029: documentation: new best place to put the signal handler registration
-+-
 Reporter:  un33k|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   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 un33k):

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


Comment:

 '''Also:
 '''
 '''This:'''
 "Sent by the migrate command before it starts to install an application."
 '''Could be changed to:'''
 "Sent by the migrate command before it starts to install an application
 that has a models module."

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

[Django] #22029: documentation: new best place to put the signal handler registration

2014-02-12 Thread Django

#22029: documentation: new best place to put the signal handler registration
--+
Reporter: un33k | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation |Version: master
Severity: Normal| Keywords:
Triage Stage: Unreviewed| Has patch: 0
Easy pickings: 0 | UI/UX: 0
--+
The new best place for registering the signal handlers are in the ready()
of the AppConfig.

This way, the signals properly emit with the server starts and also via
the django-admin shell.

The documentation would benefit from an update indicating the new feature
of Django 1.7.

The following section may require the update.

https://docs.djangoproject.com/en/dev/ref/signals/#django.db.models.signals.pre_migrate

https://docs.djangoproject.com/en/dev/ref/signals/#django.db.models.signals.post_migrate

'''This:'''
"Any handlers that listen to this signal need to be written in a
particular place: a management module in one of your INSTALLED_APPS. If
handlers are registered anywhere else they may not be loaded by migrate."
'''Could be changed to:'''
"Any handlers that listen to this signal need to be written in a
particular place: the AppConfig.ready() within the apps module in one of
your INSTALLED_APPS. If handlers are registered anywhere else they may not
be loaded by migrate."

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

Re: [Django] #20434: Have a template tag grammar instead of handling token/parser for every tag, and make it possible to introspect the grammar.

2014-02-12 Thread Django

#20434: Have a template tag grammar instead of handling token/parser for every 
tag,
and make it possible to introspect the grammar.
-+-
 Reporter:  jonathanslenders |Owner:
 Type:  New feature  |  jonathanslenders
Component:  Template system  |   Status:  assigned
 Severity:  Normal   |  Version:
 Keywords:   |   Resolution:
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by berkerpeksag):

 * cc: berker.peksag@… (added)


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

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

Re: [Django] #22028: documentation: apps without models.py can register for db related signals

2014-02-12 Thread Django

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

Comment:

'''Correction''':

This:
"It may be None if the application doesn’t contain a models module."
Could be changed to:
"It may be None if the application doesn’t contain a models module. Please
note that the database related signals such as pre_migrate / post_migrate
signals are only emitted for applications that have a models module.

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

[Django] #22028: documentation: apps without models.py can register for db related signals

2014-02-12 Thread Django

#22028: documentation: apps without models.py can register for db related
signals
-+-
Reporter: un33k| Owner: nobody
Type: | Status: new
Cleanup/optimization |Version: master
Component: Documentation| Keywords: apps without models
Severity: Normal | database signals
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0| UI/UX: 0
-+-
Before Django 1.7, all apps in the INSTALLED_APPS required to have a
models.py, and they could latch onto the database related signals such as
the '''pre_syncdb''' and the '''post_syncdb'''. So the documentations
didn't need to be specific.

However, with the introduction of the AppConfig, apps no longer required a
models.py and hence the documentation could benefit from an extra line of
explanation that ONLY the apps that have the models.py could register to
the database related signals.

On this page:

https://docs.djangoproject.com/en/dev/ref/applications/#django.apps.AppConfig.models_module

This:
"It may be None if the application doesn’t contain a models module."
Could be changed to:
"It may be None if the application doesn’t contain a models module. Please
note that only applications with a models module can register for the
database related signals such as '''pre_migrate''' / '''post_migrate'''
signals.

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

Re: [Django] #21581: collecstatic --clear is too lax about warning users

2014-02-12 Thread Django

Comment (by Tim Graham ):

In [changeset:"d6db48e5f6320ec3d76419b67c6a3819f078be5c"]:
{{{
#!CommitTicketReference repository=""
revision="d6db48e5f6320ec3d76419b67c6a3819f078be5c"
[1.6.x] Reworked the detection of local storages for the collectstatic
command.

Before 4befb30 the detection was broken because we used isinstance
against a LazyObject rather than against a Storage class. That commit
fixed it by looking directly at the object wrapped by LazyObject.
This could however be a problem to anyone who subclasses the
collectstatic management Command and directly supplies a Storage class.

Refs #21581.

Backport of 7e27885c6e7588471fd94a4def16b7081577bdfc 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/064.699784170956bf905e3d5b87357483f9%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] d6db48: [1.6.x] Reworked the detection of local storages f...

2014-02-12 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: d6db48e5f6320ec3d76419b67c6a3819f078be5c
  
https://github.com/django/django/commit/d6db48e5f6320ec3d76419b67c6a3819f078be5c
  Author: Loic Bistuer 
  Date:   2014-02-12 (Wed, 12 Feb 2014)

  Changed paths:
M django/contrib/staticfiles/management/commands/collectstatic.py
M tests/staticfiles_tests/tests.py

  Log Message:
  ---
  [1.6.x] Reworked the detection of local storages for the collectstatic 
command.

Before 4befb30 the detection was broken because we used isinstance
against a LazyObject rather than against a Storage class. That commit
fixed it by looking directly at the object wrapped by LazyObject.
This could however be a problem to anyone who subclasses the
collectstatic management Command and directly supplies a Storage class.

Refs #21581.

Backport of 7e27885c6e7588471fd94a4def16b7081577bdfc 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/52fb9bd2816fc_b461029d3c65757%40hookshot-fe12-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21581: collecstatic --clear is too lax about warning users

2014-02-12 Thread Django

Comment (by Tim Graham ):

In [changeset:"7e27885c6e7588471fd94a4def16b7081577bdfc"]:
{{{
#!CommitTicketReference repository=""
revision="7e27885c6e7588471fd94a4def16b7081577bdfc"
Reworked the detection of local storages for the collectstatic command.

Refs #21581.
}}}

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

[django/django] 7e2788: Reworked the detection of local storages for the c...

2014-02-12 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7e27885c6e7588471fd94a4def16b7081577bdfc
  
https://github.com/django/django/commit/7e27885c6e7588471fd94a4def16b7081577bdfc
  Author: Loic Bistuer 
  Date:   2014-02-12 (Wed, 12 Feb 2014)

  Changed paths:
M django/contrib/staticfiles/management/commands/collectstatic.py
M tests/staticfiles_tests/tests.py

  Log Message:
  ---
  Reworked the detection of local storages for the collectstatic command.

Before 4befb30 the detection was broken because we used isinstance
against a LazyObject rather than against a Storage class. That commit
fixed it by looking directly at the object wrapped by LazyObject.
This could however be a problem to anyone who subclasses the
collectstatic management Command and directly supplies a Storage class.

Refs #21581.


-- 
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/52fb9b53957c5_18f7ed5d3c409c6%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22026: Celebrate your success: We're quick to beat ourselves up when we don't reach our health and fitness goals, but we rarely celebrate our successes. When you've achieved one of your goal

2014-02-12 Thread Django

#22026: Celebrate your success: We're quick to beat ourselves up when we don't
reach our health and fitness goals, but we rarely celebrate our successes.
When you've achieved one of your goals, give yourself a pat on the back.
Treat yourself to a massage, a new pair of shoes, or a night out with your
friends.
---+
Reporter: anonymous | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized |Version: 1.6
Severity: Normal | Keywords: Xtreme Muscle Recovery
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
---+
You don't get to act until New Assemblage's Day to oblige resolutions to
improve your eudaimonia and fitness. Disregarding of the period or day,
you can necessitate proceeding now to achieve your welfare and suitability
goals. Here are few tips to get you started:
Superior one region to activity on: Many grouping make the slip of
disagreeable to neaten himself or herself into a new being overnight. It's
unjustified to look yourself to, at the photo of a digit, move habits that
you know spent period cultivating. Instead, superior one welfare and
suitability country to job on.
select a fact goal: Speech that you "deprivation to decline coefficient"
or "get in appearance" is too unclear. You condition to rise up with a
tangible content in prescript to manoeuvre your development and keep your
success. Xtreme Muscle Recovery

select a existent goal: If you've been a sweetener junkie for 20 period,
you can't await to go inhuman poultry long. You may be healthy to cut
dulcify out for a few life or even a few weeks, but you won't be competent
to have it up for the position of your living.
Opt for incremental exchange: In the edulcorate scenario, synopsis a
serial of steps you can withdraw over second to accomplish your goal. The
position manoeuvre strength be to shift from prescribed soda to sugar-free
tonic. After successfully doing that for a month, rig the incoming stair -
maybe a turn from regularised to sugar-free ice toiletries, or restricting
desserts to weekends only. Incorporating lilliputian changes over
dimension dramatically increases the quantity that you'll work it a
unceasing way change sustenance: In a gild that supersizes everything,
it's never unchaste to put with your health and shape goals. Recruit the
aid of a individual, lineage member, or co-worker - someone who give
service you outride with the thought. If your content is to go to the gym
cardinal present a period, for representative, informed that your soul is
ready there for you strength be just the payment you require to create
sure you result through. For artifact motive, put a buck in a jar every
moment you go to the gym, then initiate yourself to som Xtreme Muscle
Recovery

Keep your success: We're fast to cheat ourselves up when we don't strain
our eudaimonia and fitness goals, but we rarely keep our successes. When
you've achieved one of your goals, elasticity yourself a pat on the
affirm. Treat yourself to a massage, a new twain of shoes, or a period out
with your friends.
[http://xtrememusclerecoveryreview.com/]

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

[django/django] 73f51e: Fixed #22025 -- Listing app followed by app.Model ...

2014-02-12 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 73f51e411372ba3e74ccf5a2c2be88927ac2c6dd
  
https://github.com/django/django/commit/73f51e411372ba3e74ccf5a2c2be88927ac2c6dd
  Author: Eli Bendersky 
  Date:   2014-02-12 (Wed, 12 Feb 2014)

  Changed paths:
M django/core/management/commands/dumpdata.py
M tests/fixtures/tests.py

  Log Message:
  ---
  Fixed #22025 -- Listing app followed by app.Model in dumpdata command

When invoked as follows:

  $ python manage.py dumpdata blogapp blogapp.Tag

Django would throw a TypeError. This commit fixes the problem and provides
a test.


-- 
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/52fb8697bed0b_362debdd40113581%40hookshot-fe10-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22025: TypeError in the dumpdata command when listing "app app.Model"

2014-02-12 Thread Django

#22025: TypeError in the dumpdata command when listing "app app.Model"
-+-
 Reporter:  eliben@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Baptiste Mispelon ):

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


Comment:

 In [changeset:"73f51e411372ba3e74ccf5a2c2be88927ac2c6dd"]:
 {{{
 #!CommitTicketReference repository=""
 revision="73f51e411372ba3e74ccf5a2c2be88927ac2c6dd"
 Fixed #22025 -- Listing app followed by app.Model in dumpdata command

 When invoked as follows:

   $ python manage.py dumpdata blogapp blogapp.Tag

 Django would throw a TypeError. This commit fixes the problem and provides
 a test.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.53944ab988619c03396a0d0dab186136%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22025: TypeError in the dumpdata command when listing "app app.Model"

2014-02-12 Thread Django

#22025: TypeError in the dumpdata command when listing "app app.Model"
-+-
 Reporter:  eliben@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by eliben):

 Replying to [comment:2 anonymous]:
 > Added a test in the pull request.

 Sorry, logged in now.

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

Re: [Django] #22025: TypeError in the dumpdata command when listing "app app.Model"

2014-02-12 Thread Django

#22025: TypeError in the dumpdata command when listing "app app.Model"
-+-
 Reporter:  eliben@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by anonymous):

 Added a test in the pull request.

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

Re: [Django] #22025: TypeError in the dumpdata command when listing "app app.Model"

2014-02-12 Thread Django

#22025: TypeError in the dumpdata command when listing "app app.Model"
-+-
 Reporter:  eliben@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by bmispelon):

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


Comment:

 Hi,

 I can indeed reproduce the issue.

 The pull request looks reasonable but you'll need to add some tests for it
 to be merged.

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

[Django] #22025: TypeError in the dumpdata command when listing "app app.Model"

2014-02-12 Thread Django

#22025: TypeError in the dumpdata command when listing "app app.Model"
+
 Reporter:  eliben@…|  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Core (Management commands)  |Version:  master
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  1
Easy pickings:  0   |  UI/UX:  0
+
 When running:

 {{{

 $ python manage.py dumpdata  blogapp blogapp.Tag

 }}}

 I get:

 {{{

 Traceback (most recent call last):
   File "manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   ...
   ...
 TypeError: argument of type 'NoneType' is not iterable

 }}}

 A fix is in this pull request: https://github.com/django/django/pull/2262

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

Re: [Django] #22018: Checks error on ModelAdmins with multiple fields in one line using lists

2014-02-12 Thread Django

#22018: Checks error on ModelAdmins with multiple fields in one line using lists
---+
 Reporter:  jwa|Owner:  jwa
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  checks | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by jwa):

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


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

Re: [Django] #22024: there are no tests for assertContains

2014-02-12 Thread Django

#22024: there are no tests for assertContains
-+-
 Reporter:  hjwp |Owner:  hjwp
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.6
Component:  Utilities|   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by hjwp):

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


Comment:

 right-o. my bad!

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

Re: [Django] #22024: there are no tests for assertContains

2014-02-12 Thread Django

#22024: there are no tests for assertContains
-+-
 Reporter:  hjwp |Owner:  hjwp
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  Utilities|   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
-+-

Comment (by anonymous):

 aha!  well, i guess i should have tried that :)  let's have a look...

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

Re: [Django] #22018: Checks error on ModelAdmins with multiple fields in one line using lists

2014-02-12 Thread Django

#22018: Checks error on ModelAdmins with multiple fields in one line using lists
---+
 Reporter:  jwa|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  checks | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by bmispelon):

 * easy:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 As discussed on IRC, while these might be two separate issues, it's likely
 that both would be fixed by flattening the `fields` attribute before
 checking for duplicate fields so I think it makes sense to keep this as
 one single ticket.

 I'll also mark this as `easy pickings` since it shouldn't be too hard to
 fix.

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

Re: [Django] #22024: there are no tests for assertContains

2014-02-12 Thread Django

#22024: there are no tests for assertContains
-+-
 Reporter:  hjwp |Owner:  hjwp
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  Utilities|   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
-+-

Comment (by bmispelon):

 Hi,

 What about `test_client_regress.tests.AssertContainsTests` and
 `test_utils.tests.HTMLEqualTests`?

 They seem to be testing the behavior of `assertContains` to me (I found
 them by changing `assertContains` to always return `True` and running the
 full test suite to see what broke).

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

Re: [Django] #22024: there are no tests for assertContains

2014-02-12 Thread Django

#22024: there are no tests for assertContains
-+-
 Reporter:  hjwp |Owner:  hjwp
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  Utilities|   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 anonymous):

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


Comment:

 in case the trac github plugin magic doesn't work, here's the PR
 https://github.com/django/django/pull/2267

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

Re: [Django] #22023: .values() followed by defer() or only() results invalid data or crash

2014-02-12 Thread Django

#22023: .values() followed by defer() or only() results invalid data or crash
-+-
 Reporter:  jtiai|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  orm  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by bmispelon):

 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * version:  1.5 => master
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 I can reproduce this on sqlite and it seems to be an old problem (I tested
 all versions of Django until 1.4 and they're all affected).

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

Re: [Django] #22018: Checks error on ModelAdmins with multiple fields in one line using lists

2014-02-12 Thread Django

#22018: Checks error on ModelAdmins with multiple fields in one line using lists
---+--
 Reporter:  jwa|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  checks | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by jwa):

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


Comment:

 Additionally, these check methods contain a bug whereas they are trying to
 prevent duplicate fields on a ModelAdmin form. Using `len(set())` on
 nested tuples will not guarantee that there are, in fact, no duplicates. I
 think this requires fixing as well.

 This ModelAdmin for example will pass the checks even though it contains
 duplicate fields:

 {{{
 class FooAdmin(admin.ModelAdmin):
 fields = ('one', ('one', 'two'))
 }}}

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

[Django] #22024: there are no tests for assertContains

2014-02-12 Thread Django

#22024: there are no tests for assertContains
--+--
 Reporter:  hjwp  |  Owner:  hjwp
 Type:  Cleanup/optimization  | Status:  new
Component:  Utilities |Version:  1.6
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+--
 I've been thinking of ways to tweak assertContains, thought about trying a
 couple of them out, and was shocked, shocked to discover that this test
 helper method has no tests of its own!

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

[Django] #22023: .values() followed by defer() or only() results invalid data or crash

2014-02-12 Thread Django

#22023: .values() followed by defer() or only() results invalid data or crash
--+
 Reporter:  jtiai |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.5
 Severity:  Normal|   Keywords:  orm
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Given model

 {{{
 class MyModel(models.Model):
 field_a = models.CharField(max_length=100)
 field_b = models.IntegerField()
 field_c = models.TextField()
 }}}

 Query {{{ MyModel.objects.values().only('field_b') }}}
 Returns totally incorrect set of fields

 Query {{{ MyModel.objects.values().defer('field_b') }}}
 Returns all fields but data is shifted starting from field_b

 Query {{{ MyModel.objects.values('field_a').only('field_b') }}}
 Results a crash due malformed SQL.

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

Re: [Django] #22015: Hide relationships with related_name='+' in contrib.admindocs (was: Hide relationships with related_name='+')

2014-02-12 Thread Django

#22015: Hide relationships with related_name='+' in contrib.admindocs
---+
 Reporter:  motiejus   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admindocs  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  1
---+

Comment (by timo):

 As noted on the PR, admindocs is severely lacking in tests and
 bootstrapping them enough to be able to write a test for this change is
 more work than the reporter wants to do. If anyone else is interested in
 this patch, the first step will be to do 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/066.ae80313eef2ec5df4988e7ca59f2053b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20745: Document the template language's silencing of TypeError

2014-02-12 Thread Django

#20745: Document the template language's silencing of TypeError
-+-
 Reporter:  robin|Owner:  Baptiste
 Type:  Bug  |  Mispelon 
Component:  Template system  |   Status:  closed
 Severity:  Normal   |  Version:  1.5
 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 bmispelon):

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


Comment:

 Hi,

 The fix for this issue will be part of the 1.7 release which only supports
 versions of Python above 2.7 [1] so this shouldn't be a problem.


 [1] https://docs.djangoproject.com/en/dev/releases/1.7/#python-
 compatibility

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

Re: [Django] #20745: Document the template language's silencing of TypeError

2014-02-12 Thread Django

#20745: Document the template language's silencing of TypeError
-+-
 Reporter:  robin|Owner:  Baptiste
 Type:  Bug  |  Mispelon 
Component:  Template system  |   Status:  new
 Severity:  Normal   |  Version:  1.5
 Keywords:   |   Resolution:
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 pczerkas@…):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.124df36442769ea773fd899c36d04367%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20745: Document the template language's silencing of TypeError

2014-02-12 Thread Django

#20745: Document the template language's silencing of TypeError
-+-
 Reporter:  robin|Owner:  Baptiste
 Type:  Bug  |  Mispelon 
Component:  Template system  |   Status:  closed
 Severity:  Normal   |  Version:  1.5
 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
-+-

Comment (by pczerkas@…):

 inspect.getcallargs is unavailable in Python 2.6

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

[Django] #22022: Allow field subclasses to require additional SQL

2014-02-12 Thread Django

In postgres, a number of data types require a specific extension to be
installed. We have one instance of this in core at present, which is the
`postgis` extension. Our documentation recommends[1] (in postgres 9.1+)
that you explicitly create the extension in your primary database by hand,
and then we customise the `_create_test_db` method on the postgis database
backend to ensure the test database has the relevant extensions installed.

Other third party apps[2] recommend adding the extension to the template
to ensure it's present in tests.

I wish to avoid adding a custom backend to d.c.postgres if at all
possible, especially as using it in conjunction with gis should be
permissible. Consequently, I'd like if possible for model fields to have
`pre_create_sql` to allow each individual field to create the extensions
as needed. The same mechanism could also be used for a user defined custom
field to create functions which could then be used as a custom transform
object.

This feature will be useful for:
1) one part of the de-hack-gis project
2) hstore
3) citext, trigrams, generating uuids database side and other possible
future features of d.c.postgres

I've written a draft patch[3]. It probably needs some work (hence patch
needs improvement) but an initial review of the names and code layout
would be useful.

[1]

https://docs.djangoproject.com/en/1.6/ref/contrib/gis/install/postgis/#creating-a
-spatial-database-with-postgis-2-0-and-postgresql-9-1
[2] https://github.com/djangonauts/django-hstore#running-the-tests
[3] https://github.com/django/django/pull/2266

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

Re: [Django] #22019: add section for definitive Model.objects documentation

2014-02-12 Thread Django

Comment (by cjerdonek):

It doesn't need to be extensive. It might only be a few sentences, say
like the

[https://docs.djangoproject.com/en/dev/ref/models/instances/#django.db.models.Model.save
Model.save docs], which primarily points the reader to other places.

The point is just to have `Model.objects` appear //some// place in the API
docs. It can simply be a hub that links people elsewhere (e.g. the
"Retrieving objects" section I mentioned above as well as the managers
section you mentioned).

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

Re: [Django] #22019: add section for definitive Model.objects documentation

2014-02-12 Thread Django

#22019: add section for definitive Model.objects documentation
-+-
 Reporter:  cjerdonek|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  models,objects   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by mjtamlyn):

 There is no need for extensive documentation of `objects` - it's a
 `Manager` instance so the managers doc is the reference:
 https://docs.djangoproject.com/en/dev/topics/db/managers/

 Making these links more explicit might be useful though.

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

[Django] #22021: weight loss 305

2014-02-12 Thread Django

#22021: weight loss 305
---+-
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:  DIET ULTIMO
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+-
 think antineeded to make a great great it's happening think distinct
 wonderful painfully keeps villas at hopkins dehydrated it's very very
 important to me that yousee kind to teaching tools and think that i am
 very in he fell eighty trolley and field andmock special ends treating it
 right now and then and ithink freaks they think a lot creates and i'm
 justkind of very cranberry the world i would use a different people
 facebook will contain package thatincludes unique spring number in a non-
 printingthat's happened i forget batman are common free accede to
 catherine in fact thatthey don't freak on hold faculty artie democratic
 three five two eight tons andtons bristol mile off its most still trying
 to get matched advancebooking he can didn't see any kind eat and go out
 and do you think it'simportant for people have a ingenuity lifting
 relaxing break down down and practiced in changing things aroundjust yet
 analytic sumner in and out in theweakening when he went home
  they're going to bet resulting[http://dietultimohq.com/ DIET ULTIMO]
 somethingbad happens when you come from to maintain the do you think when
 really and your kind of investment to date we have a treatment and after
 admittingthat you can react for big party jump at the age having to get a
 bit for the month i'm alittle bit monday and he's cheating him out deepak
 twenty bt certain iraq to crack trying to keepback on himself that trying
 to keep the fact that ithink that you need to be back in conflict with any
 into the route you didnot think you know you know down instead of just
 meet in bali for locally bath and get back to saint louis jstraightaway
 seize a chance to do anything about it pays convalescentfinances gimmick
 get and disagree dvd and competent hack he didn't
 http://dietultimohq.com/

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

[Django] #22020: No Wrinkle Fresh Face

2014-02-12 Thread Django

#22020: No Wrinkle Fresh Face
---+
 Reporter:  maryfox339@…   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:  admin
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 So if working out and eating healthy is what makes you feel confident gray
 and where me it makes you feel confident great and here are you comedy
 yourself as long as you feel get inside that is all that matters bananas
 by chance a nap anyways I am getting that my personal test because you
 guys asked for me to do this video but I just want to not because I don’t
 want you guys to get the wrong impression and you guys know me I'm just
 purely showing you I do I'm not telling you have to do this out at all
 I'll cut happen time.

 I don’t even do this is like a once an eight-week occurrence that I
 actually eat like this can do you think so something you
 [http://aktiveamadvice.com/ Aktive AM] know and if you would like to see
 an updated router which I know I keep saying this is my video measures got
 a thumbs up this video because this item I really doubt this idea is
 almost done this idea is not really done I have to finish something with
 my desk area that's why haven’t lived under America’s it's not completely
 done yet but once I finish that router will be gone up release in here so
 if you want to rooms are doesn't this video.

 I think that's it starting off with the food set I eat when I got my local
 market I like to shop the perimeter market and usually and most markets
 the printer is where they have all the produce like vegetables and fruits
 and olive be unprocessed foods so I like to stay away from the middle of
 them market which is a lot of the processed packaged and frozen sections
 bids I basically tried to keep clean this doesn't happen every day because
 I crave a bunch unhealthy foods just like any person would say by doing
 this I'm less tempted and less likely to you by John C you going healthy
 tips that I try to remember it.

 http://aktiveamadvice.com/

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

[django/django] e0381c: Fixed #22017 -- Prevented RuntimeError on Python 3

2014-02-12 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e0381cdf2e7f677c5b29f2e3351993e92915569a
  
https://github.com/django/django/commit/e0381cdf2e7f677c5b29f2e3351993e92915569a
  Author: Claude Paroz 
  Date:   2014-02-12 (Wed, 12 Feb 2014)

  Changed paths:
M django/utils/autoreload.py

  Log Message:
  ---
  Fixed #22017 -- Prevented RuntimeError on Python 3

Refs #21049. Thanks quinox for the report.


-- 
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/52fb3e411ec19_64b44a3d3c9817%40hookshot-fe9-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21049: RuntimeError when running ./manage.py runserver

2014-02-12 Thread Django

#21049: RuntimeError when running ./manage.py runserver
--+--
 Reporter:  lvella@…  |Owner:  mburst
 Type:  Bug   |   Status:  closed
Component:  Python 3  |  Version:  1.6-beta-1
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--

Comment (by Claude Paroz ):

 In [changeset:"e0381cdf2e7f677c5b29f2e3351993e92915569a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e0381cdf2e7f677c5b29f2e3351993e92915569a"
 Fixed #22017 -- Prevented RuntimeError on Python 3

 Refs #21049. Thanks quinox for the report.
 }}}

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

Re: [Django] #22017: RuntimeError: dictionary changed size during iteration

2014-02-12 Thread Django

#22017: RuntimeError: dictionary changed size during iteration
--+---
 Reporter:  quinox|Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Python 3  |  Version:  1.7-alpha-1
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+---
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"e0381cdf2e7f677c5b29f2e3351993e92915569a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e0381cdf2e7f677c5b29f2e3351993e92915569a"
 Fixed #22017 -- Prevented RuntimeError on Python 3

 Refs #21049. Thanks quinox for the report.
 }}}

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

Re: [Django] #22017: RuntimeError: dictionary changed size during iteration

2014-02-12 Thread Django

#22017: RuntimeError: dictionary changed size during iteration
--+---
 Reporter:  quinox|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Python 3  |  Version:  1.7-alpha-1
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+---
Changes (by claudep):

 * easy:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 Regression was introduced in 15f82c701161b327cef54b469c00b6cbe01534db.

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

59 matches

Mail list logo