date:20140426

Re: [Django] #21927: URL namespacing improvements

2014-04-26 Thread Django

#21927: URL namespacing improvements
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (URLs)   |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by bendavis78):

 A major problem i see with url namespaces is that if the user of an app
 specifies a namespace, it will break url reversals within the app itself
 (even when using current_app). If I want my app to support namespacing,
 and I don't want my url reversals to break within my app, I have to
 provide a function that accepts a namespace argument and returns a triple
 and instruct the user to use that instead of specifying a namespace in in
 include(). This makes the namespace argument to include() fairly useless,
 IMHO. It also forces a non-standard API for namespacing urls.

 If what this ticket proposes can fix that, I'm all for it.

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

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

Re: [Django] #22510: Form fields cannot have names that are present as attributes on the form

2014-04-26 Thread Django

Comment (by loic84):

At the time I suggested we only allowed shadowing with `None`, @mjtamlyn
convinced me that we should follow normal Python inheritance/shadowing and
I think that was a good decision.

I see value in matching as closely as possible the MRO behavior, other
than the fact that `Field` magically remove themselves from the class
(whether shadowed or not), we are pretty good on that front.

Inheritance makes this kind of clash possible, but a single form couldn't
define both a `Field` and an attribute anyway.

To expose a `media=42` attribute like in the test of the proposed patch,
one can set `self.media` in `__init__()`, or ensure that it appears first
in the MRO. By ensuring it appears first in the MRO it won't shadow any
field, and it will not be shadowed itself because fields are removed from
the class.

We document:

{{{
It's possible to opt-out from a ``Field`` inherited from a parent class by
shadowing it. While any non-``Field`` value works for this purpose, it's
recommended to use ``None`` to make it explicit that a field is being
nullified.
}}}

Which is exactly the case describe in the tests.

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

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

Re: [Django] #5797: decorator_from_middleware can cause middleware hooks to run out of correct order.

2014-04-26 Thread Django

#5797: decorator_from_middleware can cause middleware hooks to run out of 
correct
order.
-+-
 Reporter:  jdunck   |Owner:
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  cache middleware | Triage Stage:  Accepted
  decorator gzip conditional http|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by hirokiky):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1


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

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

Re: [Django] #19210: django.utils.timesince() does not account for leap years

2014-04-26 Thread Django

#19210: django.utils.timesince() does not account for leap years
---+
 Reporter:  jnns   |Owner:
 Type:  Bug|   Status:  new
Component:  Utilities  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  date time  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by hirokiky):

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


Comment:

 Thanks @susan @timo. I can't take time for this problem, so I'm leaving.

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

Re: [Django] #5797: decorator_from_middleware can cause middleware hooks to run out of correct order.

2014-04-26 Thread Django

#5797: decorator_from_middleware can cause middleware hooks to run out of 
correct
order.
-+-
 Reporter:  jdunck   |Owner:
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  cache middleware | Triage Stage:  Accepted
  decorator gzip conditional http|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by hirokiky):

 * owner:  hirokiky =>
 * status:  assigned => new
 * has_patch:  1 => 0


Comment:

 The pull-requelt doesn't work current master brunch.
 (https://github.com/django/django/pull/659)

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

Re: [Django] #18225: Staticfiles template tag does not fail silently

2014-04-26 Thread Django

#18225: Staticfiles template tag does not fail silently
-+
 Reporter:  bouke|Owner:  moritzs
 Type:  Bug  |   Status:  closed
Component:  contrib.staticfiles  |  Version:  1.4
 Severity:  Normal   |   Resolution:  wontfix
 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 anon0405@…):

 It would be nice if there were a setting that toggled whether this fails
 loudly or silently -- often it is better to serve an html file with broken
 formatting (missing css), missing functionality (missing js), or missing
 niceties (missing .ico) than to throw up a server error and prevent any
 information from reaching the end user.

 Especially where the behavior of {% static %} is explicitly to not raise
 errors in development, the current behavior creates time bombs that are
 out of step with the rest of django's template error philosophy -- fail
 silently whenever possible.

 Two options are:
 * {% static 'file/path.stuff' True %} -- passing an optional parameter of
 whether to fail silently, so this can be turned on/off as needed
 * STATIC_TAG_FAILS_SILENTLY=True -- an option in settings.py

 If there isn't a way to make it fail silently in production, then the
 errors should somehow be raised in DEV so they are caught and 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.6490c7eb7ef3b00dc9b035a2f20c069b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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

2014-04-26 Thread Django

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

 * cc: kevin-brown (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/066.bbf278fe57bdc6dde5d80ff13c05398b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #9602: Add admin.site._registry manipulation methods

2014-04-26 Thread Django

#9602: Add admin.site._registry manipulation methods
-+-
 Reporter:  robhudson|Owner:  anonymous
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  1.0
 Severity:  Normal   |   Resolution:
 Keywords:  register modeladmin  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by anonymous):

 * status:  new => assigned
 * needs_tests:  0 => 1
 * easy:  0 => 1
 * owner:  nobody => anonymous
 * needs_docs:  0 => 1
 * has_patch:  0 => 1


Comment:

 useradmin = admin.site._registry.get(User, None)
 if useradmin:
 useradmin.list_display = useradmin.list_display + ('is_superuser',)
 else:
 class MyUserAdmin(AuthUserAdmin):
 list_display = ('username', 'email', 'first_name', 'last_name',
 'is_staff', 'is_superuser')
 admin.site.register(User, MyUserAdmin)

-- 
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.93a37155408bed69840aaab3d5e68f57%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22526: New check method on models not documented in release notes

2014-04-26 Thread Django

#22526: New check method on models not documented in release notes
---+
 Reporter:  kevin-brown|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.7-beta-2
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Django 1.7 adds a new `check` command for models that is called on the
 class.  As far as I can tell, this is only mentioned (briefly) in the
 documentation for the check framework.

 https://docs.djangoproject.com/en/1.7/topics/checks/#field-model-and-
 manager-checks

 If users create a model that has a method `check`, calling `manage.py
 check` will fail (because of the conflicting method names).

 {{{
 Traceback (most recent call last):
   File "manage.py", line 12, in 
 execute_from_command_line(sys.argv)
   File "/home/<>/.virtualenvs/<>/local/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 427, in
 execute_from_command_line
 utility.execute()
   File "/home/<>/.virtualenvs/<>/local/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 419, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/<>/.virtualenvs/<>/local/lib/python2.7/site-
 packages/django/core/management/base.py", line 288, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/home/<>/.virtualenvs/<>/local/lib/python2.7/site-
 packages/django/core/management/base.py", line 337, in execute
 output = self.handle(*args, **options)
   File "/home/<>/.virtualenvs/<>/local/lib/python2.7/site-
 packages/django/core/management/commands/check.py", line 39, in handle
 self.check(app_configs=app_configs, tags=tags,
 display_num_errors=True)
   File "/home/<>/.virtualenvs/<>/local/lib/python2.7/site-
 packages/django/core/management/base.py", line 370, in check
 all_issues = checks.run_checks(app_configs=app_configs, tags=tags)
   File "/home/<>/.virtualenvs/<>/local/lib/python2.7/site-
 packages/django/core/checks/registry.py", line 59, in run_checks
 new_errors = check(app_configs=app_configs)
   File "/home/<>/.virtualenvs/<>/local/lib/python2.7/site-
 packages/django/core/checks/model_checks.py", line 16, in check_all_models
 if app_configs is None or model._meta.app_config in app_configs]
 TypeError: unbound method check() must be called with [model name]
 instance as first argument (got nothing instead)
 }}}

 This is not mentioned in the release notes for Django 1.7 at all and
 worked fine in previous versions:

 https://docs.djangoproject.com/en/1.7/releases/1.7/

-- 
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/054.8c2ebf8428d46db66f2bf9230395c3ff%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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

2014-04-26 Thread Django

Comment (by anonymous):

Replying to [comment:4 anonymous]:
> I wonder if this issue is specific to a certain version of Postgres (or
maybe surfaced with it) as I have had Django 1.6.2 for some time and only
started hitting this issue after a Postgres package upgrade. I have
upgraded postgresql from 9.1.12 to 9.1.13 and started getting the error
after a reboot a couple of days later.
>
> We don't use LiveServerTestCase and I wasn't using CONN_MAX_AGE in my
settings. Setting CONN_MAX_AGE to 0 doesn't change anything for me.

Hello, it's me again. I guess it also only occurs with a test run that
produces failures. A successful test run or a test run that produces error
results will not produce the issue.

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

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

Re: [Django] #22525: syncdb should allow "y" or "n" when asking to create a user

2014-04-26 Thread Django

#22525: syncdb should allow "y" or "n" when asking to create a user
-+-
 Reporter:  Gumnos   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Uncategorized|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  new user, yes, no|  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Gumnos):

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


Comment:

 Also available in GitHub as
 https://github.com/Gumnos/django/compare/django:master...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.ebc69c690a0bddd8edd32f8f2d454d81%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22509: New Feature: Add new signals for django.contrib.auth's password change/reset

2014-04-26 Thread Django

#22509: New Feature: Add new signals for django.contrib.auth's password
change/reset
-+-
 Reporter:  xiaohanyu|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  auth, password,  | Triage Stage:
  signal |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 Could you create a custom user model with your own `set_password()`
 method?

-- 
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.02d92803a6ff51206b4c1d7d9d0032d6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22510: Form fields cannot have names that are present as attributes on the form

2014-04-26 Thread Django

#22510: Form fields cannot have names that are present as attributes on the form
-+--
 Reporter:  gc@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by timo):

 * cc: loic84 (added)
 * needs_better_patch:   => 0
 * severity:  Normal => Release blocker
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Loic, could you take a look at this?

-- 
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/071.f5ab72862f95d5e841ec930f93780669%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22524: New assertion assertQuerysetNotEqual

2014-04-26 Thread Django

#22524: New assertion assertQuerysetNotEqual
---+--
 Reporter:  amatellanes|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Testing framework  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords:  test   | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by timo):

 Personally, I don't care much for these type of negative assertions since
 there are an an infinite number of ways they can pass. Do you have a
 compelling use case in mind?

-- 
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/069.2bb0e4a008e4d9cff0f20a4eae5cb805%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22525: syncdb should allow "y" or "n" when asking to create a user

2014-04-26 Thread Django

#22525: syncdb should allow "y" or "n" when asking to create a user
--+---
 Reporter:  Gumnos|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Uncategorized |Version:  master
 Severity:  Normal|   Keywords:  new user, yes, no
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  1
--+---
 Currently the code requires that you type out "yes" or "no" in full when a
 simple "y" or "n" would do.

-- 
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/049.07cb8bf2513c8baa084b5ee2d3cbceb4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22524: New assertion assertQuerysetNotEqual

2014-04-26 Thread Django

#22524: New assertion assertQuerysetNotEqual
---+--
 Reporter:  amatellanes|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Testing framework  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords:  test   | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by amatellanes):

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


Comment:

 I started a pull request for this ticket here:
 [https://github.com/django/django/pull/2610]

-- 
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/069.d81543c78a23fa23c49a92ae76f6413e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22524: New assertion assertQuerysetNotEqual

2014-04-26 Thread Django

#22524: New assertion assertQuerysetNotEqual
---+
 Reporter:  amatellanes|  Owner:  nobody
 Type:  New feature| Status:  new
Component:  Testing framework  |Version:  1.6
 Severity:  Normal |   Keywords:  test
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Add new reverse assertion of `assertQuerysetEqual`.

-- 
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/054.89867608026c4b53553b081649eb372f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #15179: django.test.client.Client.login fake HttpRequest is not run through middlewares

2014-04-26 Thread Django

#15179: django.test.client.Client.login fake HttpRequest is not run through
middlewares
---+--
 Reporter:  Ciantic|Owner:  akaariai
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.7-beta-2
 Severity:  Release blocker|   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by aaugustin):

 Given the concerns expressed before committing this patch and the results
 seen during the beta, I would suggest to revert the change. The approach
 seems too fragile. It touches too many layers.

 I would also have closed the ticket as wontfix.

 `Client.login()` is a simple convenience feature. If it doesn't work, it
 isn't hard to write a `LoginMixin` providing a suitable `login` method for
 your website.

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

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

Re: [Django] #22254: Testing documentation doesn't make it clear that django.setup() needs to be called with setup_test_environment

2014-04-26 Thread Django

#22254: Testing documentation doesn't make it clear that django.setup() needs 
to be
called with setup_test_environment
-+-
 Reporter:  peter.landry@…   |Owner:
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.7-alpha-2
 Severity:  Normal   |   Resolution:
 Keywords:  app-loading  | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

 * status:  assigned => new
 * owner:  aaugustin =>
 * has_patch:  1 => 0
 * severity:  Release blocker => Normal
 * stage:  Ready for checkin => Unreviewed


Comment:

 `django.setup()` is now properly documented, so we can re-evaluate if
 something needs to be done for `setup_test_environment()`.

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

[django/django] a5cc99: [1.7.x] Documented django.setup().

2014-04-26 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: a5cc99de24be3e5ea4dfa287af678b86598b7915
  
https://github.com/django/django/commit/a5cc99de24be3e5ea4dfa287af678b86598b7915
  Author: Aymeric Augustin 
  Date:   2014-04-26 (Sat, 26 Apr 2014)

  Changed paths:
M docs/ref/applications.txt
M docs/ref/django-admin.txt

  Log Message:
  ---
  [1.7.x] Documented django.setup().

Thanks Eric Holscher and Tim Graham for the review.

Backport of 58ed387 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/535c12e154f5a_29fecb5d40787a%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 58ed38: Documented django.setup().

2014-04-26 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 58ed387db33e407f35c0486c1e7cbd37c35c8618
  
https://github.com/django/django/commit/58ed387db33e407f35c0486c1e7cbd37c35c8618
  Author: Aymeric Augustin 
  Date:   2014-04-26 (Sat, 26 Apr 2014)

  Changed paths:
M docs/ref/applications.txt
M docs/ref/django-admin.txt

  Log Message:
  ---
  Documented django.setup().

Thanks Eric Holscher and Tim Graham for the review.


-- 
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/535c126bb2955_270c8ffd40711bd%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #11776: HTML class for non-field errors

2014-04-26 Thread Django

#11776: HTML class for non-field errors
-+-
 Reporter:  Daniel Pope   |Owner:
 Type:  New feature  |  NickPresta
Component:  Forms|   Status:  assigned
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  1
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by anonymous):

 I'm still working on this -- I've just updated the PR.

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

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

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

2014-04-26 Thread Django

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

Comment (by anonymous):

 I wonder if this issue is specific to a certain version of Postgres (or
 maybe surfaced with it) as I have had Django 1.6.2 for some time and only
 started hitting this issue after a Postgres package upgrade. I have
 upgraded postgresql from 9.1.12 to 9.1.13 and started getting the error
 after a reboot a couple of days later.

 We don't use LiveServerTestCase and I wasn't using CONN_MAX_AGE in my
 settings. Setting CONN_MAX_AGE to 0 doesn't change anything for me.

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

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

[django/django] 996564: [1.7.x] Fix many many typos in comments throughout...

2014-04-26 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 996564df4d70947913c70b071cf4a6841c658be2
  
https://github.com/django/django/commit/996564df4d70947913c70b071cf4a6841c658be2
  Author: Alex Gaynor 
  Date:   2014-04-26 (Sat, 26 Apr 2014)

  Changed paths:
M django/contrib/admin/options.py
M django/contrib/auth/tests/test_decorators.py
M django/contrib/auth/tests/test_forms.py
M django/contrib/auth/tests/test_views.py
M django/contrib/formtools/tests/tests.py
M django/contrib/gis/db/backends/oracle/models.py
M django/contrib/gis/db/backends/postgis/models.py
M django/contrib/gis/db/backends/spatialite/models.py
M django/contrib/gis/db/backends/spatialite/operations.py
M django/contrib/gis/db/models/query.py
M django/contrib/gis/db/models/sql/compiler.py
M django/contrib/gis/gdal/__init__.py
M django/contrib/gis/geoip/base.py
M django/contrib/gis/maps/google/__init__.py
M django/contrib/gis/maps/google/zoom.py
M django/contrib/gis/utils/layermapping.py
M django/contrib/messages/storage/cookie.py
M django/contrib/sessions/tests.py
M django/db/backends/__init__.py
M django/db/models/fields/files.py
M django/db/models/query.py
M django/db/models/sql/compiler.py
M django/db/models/sql/datastructures.py
M django/db/models/sql/expressions.py
M django/db/models/sql/query.py
M django/db/models/sql/where.py
M django/forms/fields.py
M django/http/request.py
M django/templatetags/i18n.py
M django/test/runner.py
M django/test/testcases.py
M django/utils/archive.py
M django/utils/regex_helper.py
M django/views/generic/dates.py
M django/views/generic/detail.py
M tests/admin_checks/tests.py
M tests/admin_inlines/tests.py
M tests/admin_scripts/tests.py
M tests/admin_validation/tests.py
M tests/admin_views/admin.py
M tests/admin_views/tests.py
M tests/datatypes/tests.py
M tests/field_deconstruction/tests.py
M tests/file_uploads/tests.py
M tests/model_fields/models.py
M tests/model_forms/tests.py
M tests/model_inheritance_regress/tests.py
M tests/queries/tests.py
M tests/schema/tests.py
M tests/syndication_tests/tests.py
M tests/template_tests/test_response.py
M tests/template_tests/tests.py
M tests/validators/tests.py

  Log Message:
  ---
  [1.7.x] Fix many many typos in comments throughout the codebase

Backport of 2bcb8bfc8d 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/535bfcac1ff8d_4be112e3d34884de%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22447: Migrations have bases=(NewBase, ) for models with custom metaclass

2014-04-26 Thread Django

#22447: Migrations have bases=(NewBase,) for models with custom metaclass
-+--
 Reporter:  cdestigter   |Owner:  charettes
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-beta-1
 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
-+--

Comment (by bendavis78):

 I went ahead and created a [https://bitbucket.org/gutworth/six/pull-
 request/35/fixed-66-replace-the-implementation-of/diff:pull request] on
 ``six`` for this issue. Hopefully if it's merged in we can quickly merge a
 fix for Django as well.

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

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

[Django] #22523: Using unique_for_date option with models.DateTimeField causes UnicodeDecodeError

2014-04-26 Thread Django

#22523: Using unique_for_date option with models.DateTimeField causes
UnicodeDecodeError
-+-
 Reporter:  z|  Owner:  nobody
 Type:  Bug  | Status:  new
Component:   |Version:  1.6
  contrib.admin  |   Keywords:  unique_for_date, UnicodeDecodeError
 Severity:  Normal   |  Has patch:  0
 Triage Stage:   |  UI/UX:  0
  Unreviewed |
Easy pickings:  0|
-+-
 A basic Django application:

 models.py
 {{{
 from django.db import models

 class test(models.Model):
 slug = models.SlugField(unique_for_date='pub_date')
 pub_date = models.DateTimeField()
 }}}

 admin.py
 {{{
 from django.contrib import admin
 from app.models import test

 admin.site.register(test)
 }}}

 Creating new "test" entry using Django admin results in UnicodeDecodeError
 on save:

 {{{
 UnicodeDecodeError at /admin/app/test/add/
 'utf8' codec can't decode byte 0xcc in position 225: invalid continuation
 byteRequest Method:   POST
 Request URL:http://127.0.0.1:8000/admin/app/test/add/
 Django Version: 1.6.3
 Exception Type: UnicodeDecodeError
 Exception Value:'utf8' codec can't decode byte 0xcc in position
 225: invalid continuation byte
 .
 Unicode error hint

 The string that could not be encoded/decoded was: ONE '��
 }}}

 This code works fine up to Django 1.5.*.
 Using DateField instead of DateTimeField also works in current version of
 Django.

-- 
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/044.dac0efa178d66ae27add61d0f18fbfae%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 2bcb8b: Fix many many typos in comments throughout the cod...

2014-04-26 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2bcb8bfc8de5cd57ebb64b326cd7609aa0d8c1c7
  
https://github.com/django/django/commit/2bcb8bfc8de5cd57ebb64b326cd7609aa0d8c1c7
  Author: Alex Gaynor 
  Date:   2014-04-26 (Sat, 26 Apr 2014)

  Changed paths:
M django/contrib/admin/options.py
M django/contrib/auth/tests/test_decorators.py
M django/contrib/auth/tests/test_forms.py
M django/contrib/auth/tests/test_views.py
M django/contrib/formtools/tests/tests.py
M django/contrib/gis/db/backends/oracle/models.py
M django/contrib/gis/db/backends/postgis/models.py
M django/contrib/gis/db/backends/spatialite/models.py
M django/contrib/gis/db/backends/spatialite/operations.py
M django/contrib/gis/db/models/query.py
M django/contrib/gis/db/models/sql/compiler.py
M django/contrib/gis/gdal/__init__.py
M django/contrib/gis/geoip/base.py
M django/contrib/gis/maps/google/__init__.py
M django/contrib/gis/maps/google/zoom.py
M django/contrib/gis/utils/layermapping.py
M django/contrib/messages/storage/cookie.py
M django/contrib/sessions/tests.py
M django/db/backends/__init__.py
M django/db/models/fields/files.py
M django/db/models/query.py
M django/db/models/sql/compiler.py
M django/db/models/sql/datastructures.py
M django/db/models/sql/expressions.py
M django/db/models/sql/query.py
M django/db/models/sql/where.py
M django/forms/fields.py
M django/http/request.py
M django/templatetags/i18n.py
M django/test/runner.py
M django/test/testcases.py
M django/utils/archive.py
M django/utils/regex_helper.py
M django/views/generic/dates.py
M django/views/generic/detail.py
M tests/admin_checks/tests.py
M tests/admin_inlines/tests.py
M tests/admin_scripts/tests.py
M tests/admin_validation/tests.py
M tests/admin_views/admin.py
M tests/admin_views/tests.py
M tests/datatypes/tests.py
M tests/field_deconstruction/tests.py
M tests/file_uploads/tests.py
M tests/model_fields/models.py
M tests/model_forms/tests.py
M tests/model_inheritance_regress/tests.py
M tests/queries/tests.py
M tests/schema/tests.py
M tests/syndication_tests/tests.py
M tests/template_tests/test_response.py
M tests/template_tests/tests.py
M tests/validators/tests.py

  Log Message:
  ---
  Fix many many typos in comments throughout the codebase


-- 
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/535bea84f21b2_2699759d38982c1%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21597: (2006, 'MySQL server has gone away') in django1.6 when wait_timeout passed

2014-04-26 Thread Django

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

Comment:

Actually this is the intended behavior after #15119. See that ticket for
the rationale.

**If you hit this problem and don't want to understand what's going on,
don't reopen this ticket, just do this:**

- **RECOMMENDED SOLUTION: close the connection with `from django.db import
connection; connection.close()` when you know that your program is going
to be idle for a long time.**
- ''CRAPPY SOLUTION: increase wait_timeout so it's longer than the maximum
idle time of your program.''

In this context, idle time is the time between two successive database
queries.

--
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.18c5d1cdaec19f029fdca8a2806ac18b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22254: Testing documentation doesn't make it clear that django.setup() needs to be called with setup_test_environment

2014-04-26 Thread Django

#22254: Testing documentation doesn't make it clear that django.setup() needs 
to be
called with setup_test_environment
-+-
 Reporter:  peter.landry@…   |Owner:  aaugustin
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.7-alpha-2
 Severity:  Release blocker  |   Resolution:
 Keywords:  app-loading  | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by timo):

 * needs_better_patch:  1 => 0
 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #22254: Testing documentation doesn't make it clear that django.setup() needs to be called with setup_test_environment

2014-04-26 Thread Django

#22254: Testing documentation doesn't make it clear that django.setup() needs 
to be
called with setup_test_environment
-+-
 Reporter:  peter.landry@…   |Owner:  aaugustin
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.7-alpha-2
 Severity:  Release blocker  |   Resolution:
 Keywords:  app-loading  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 https://github.com/django/django/pull/2609 documents django.setup(). Can I
 haz review?

 I'm not convinced it's worth duplicating that information wherever
 setup_test_environment() is useful. If you hit `RuntimeError: App registry
 isn't ready yet.` Google will tell you how to fix it in 10 seconds. I'll
 let someone else deal with that part if you want to.

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

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

2014-04-26 Thread Django

#22328: Add --exclude option to compilemessages
-+-
 Reporter:  infraredgirl |Owner:
 Type:  New feature  |  infraredgirl
Component:  Core (Management |   Status:  closed
  commands)  |  Version:  master
 Severity:  Normal   |   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 loic84):

 * cc: loic@… (added)
 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 Fixed in 0707b824fe77e08ca8b75fcc3738ada694f2a3a6.

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

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

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

2014-04-26 Thread Django

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

 * cc: alexander@… (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/066.7f824adbcbe65ac592b56cd2ee745e27%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #3214: [patch] raw sql file doesn't recognize quotes correctly

2014-04-26 Thread Django

Comment (by Aymeric Augustin ):

In [changeset:"3bb0f118ca375f25cd0c03a5733ee2ef9d79dfa5"]:
{{{
#!CommitTicketReference repository=""
revision="3bb0f118ca375f25cd0c03a5733ee2ef9d79dfa5"
[1.7.x] Fixed #3214 -- Stopped parsing SQL with regex.

Avoided introducing a new regex-based SQL splitter in the migrations
framework, before we're bound by backwards compatibility.

Adapted this change to the legacy "initial SQL data" feature, even
though it's already deprecated, in order to facilitate the transition
to migrations.

sqlparse becomes mandatory for RunSQL on some databases (all but
PostgreSQL). There's no API to provide a single statement and tell
Django not to attempt splitting. Since we have a more robust splitting
implementation, that seems like a good tradeoff. It's easier to add a
new keyword argument later if necessary than to remove one.

Many people contributed to both tickets, thank you all, and especially
Claude for the review.

Refs #22401.

Backport of 8b5b199 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/086.ef35856c5cfd37619b5c0a2e4a799a59%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22401: SQL Function initial SQL data does not work.

2014-04-26 Thread Django

Comment (by Aymeric Augustin ):

Avoided introducing a new regex-based SQL splitter in the migrations
framework, before we're bound by backwards compatibility.

Adapted this change to the legacy "initial SQL data" feature, even
though it's already deprecated, in order to facilitate the transition
to migrations.

Many people contributed to both tickets, thank you all, and especially
Claude for the review.

Refs #22401.

Backport of 8b5b199 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.c87aa938441b4b93cc41c905cf02588e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #3214: [patch] raw sql file doesn't recognize quotes correctly

2014-04-26 Thread Django

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

Comment:

In [changeset:"8b5b199e20ad2d8d3e91873ce0cd5d3035e05ece"]:
{{{
#!CommitTicketReference repository=""
revision="8b5b199e20ad2d8d3e91873ce0cd5d3035e05ece"
Fixed #3214 -- Stopped parsing SQL with regex.

Avoided introducing a new regex-based SQL splitter in the migrations
framework, before we're bound by backwards compatibility.

Adapted this change to the legacy "initial SQL data" feature, even
though it's already deprecated, in order to facilitate the transition
to migrations.

Many people contributed to both tickets, thank you all, and especially
Claude for the review.

Refs #22401.
}}}

--
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/086.4bcde865f672046930604be3d3b927f3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 3bb0f1: [1.7.x] Fixed #3214 -- Stopped parsing SQL with re...

2014-04-26 Thread GitHub

Branch: refs/heads/stable/1.7.x
Home: https://github.com/django/django
Commit: 3bb0f118ca375f25cd0c03a5733ee2ef9d79dfa5

https://github.com/django/django/commit/3bb0f118ca375f25cd0c03a5733ee2ef9d79dfa5
Author: Aymeric Augustin
Date: 2014-04-26 (Sat, 26 Apr 2014)

Changed paths:
M django/core/management/sql.py
M django/db/backends/__init__.py
M django/db/backends/postgresql_psycopg2/base.py
M django/db/backends/postgresql_psycopg2/operations.py
M django/db/migrations/operations/special.py
M docs/internals/contributing/writing-code/unit-tests.txt
M docs/ref/migration-operations.txt
M docs/releases/1.7.txt
M tests/initial_sql_regress/tests.py
M tests/migrations/test_operations.py
M tests/requirements/base.txt

Log Message:
---
[1.7.x] Fixed #3214 -- Stopped parsing SQL with regex.

Avoided introducing a new regex-based SQL splitter in the migrations
framework, before we're bound by backwards compatibility.

Adapted this change to the legacy "initial SQL data" feature, even
though it's already deprecated, in order to facilitate the transition
to migrations.

Many people contributed to both tickets, thank you all, and especially
Claude for the review.

Refs #22401.

Backport of 8b5b199 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/535bd4f839060_dd0bffd3842df%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22401: SQL Function initial SQL data does not work.

2014-04-26 Thread Django

Comment (by Aymeric Augustin ):

In [changeset:"8b5b199e20ad2d8d3e91873ce0cd5d3035e05ece"]:
{{{
#!CommitTicketReference repository=""
revision="8b5b199e20ad2d8d3e91873ce0cd5d3035e05ece"
Fixed #3214 -- Stopped parsing SQL with regex.

Avoided introducing a new regex-based SQL splitter in the migrations
framework, before we're bound by backwards compatibility.

Adapted this change to the legacy "initial SQL data" feature, even
though it's already deprecated, in order to facilitate the transition
to migrations.

Many people contributed to both tickets, thank you all, and especially
Claude for the review.

Refs #22401.
}}}

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

[django/django] 8b5b19: Fixed #3214 -- Stopped parsing SQL with regex.

2014-04-26 Thread GitHub

Branch: refs/heads/master
Home: https://github.com/django/django
Commit: 8b5b199e20ad2d8d3e91873ce0cd5d3035e05ece

https://github.com/django/django/commit/8b5b199e20ad2d8d3e91873ce0cd5d3035e05ece
Author: Aymeric Augustin
Date: 2014-04-26 (Sat, 26 Apr 2014)

Log Message:
---
Fixed #3214 -- Stopped parsing SQL with regex.

Avoided introducing a new regex-based SQL splitter in the migrations
framework, before we're bound by backwards compatibility.

Adapted this change to the legacy "initial SQL data" feature, even
though it's already deprecated, in order to facilitate the transition
to migrations.

Many people contributed to both tickets, thank you all, and especially
Claude for the review.

Refs #22401.

--
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/535bd4d8c5b4e_12eaf93d3c42985%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 22d992: [1.7.x] Specified 'csv and unicode' note as Python...

2014-04-26 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 22d99200a16c06ba5fa2ee9fc35c941143e9b0fb
  
https://github.com/django/django/commit/22d99200a16c06ba5fa2ee9fc35c941143e9b0fb
  Author: Claude Paroz 
  Date:   2014-04-26 (Sat, 26 Apr 2014)

  Changed paths:
M docs/howto/outputting-csv.txt

  Log Message:
  ---
  [1.7.x] Specified 'csv and unicode' note as Python 2 only

Backport of 2128b3a6 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/535bbe54b37fb_7b736d3d3c37965%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 2128b3: Specified 'csv and unicode' note as Python 2 only

2014-04-26 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2128b3a6887a45e99724f52ac2eaf4a5f4d97c84
  
https://github.com/django/django/commit/2128b3a6887a45e99724f52ac2eaf4a5f4d97c84
  Author: Claude Paroz 
  Date:   2014-04-26 (Sat, 26 Apr 2014)

  Changed paths:
M docs/howto/outputting-csv.txt

  Log Message:
  ---
  Specified 'csv and unicode' note as Python 2 only


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

[django/django] e441ce: [1.7.x] Updated doc links to point to Python 3 doc...

2014-04-26 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: e441cebce340f54741be957817cc034000deab3c
  
https://github.com/django/django/commit/e441cebce340f54741be957817cc034000deab3c
  Author: Claude Paroz 
  Date:   2014-04-26 (Sat, 26 Apr 2014)

  Changed paths:
M docs/conf.py
M docs/intro/tutorial01.txt
M docs/intro/tutorial04.txt
M docs/ref/applications.txt
M docs/ref/contrib/auth.txt
M docs/ref/contrib/sites.txt
M docs/ref/exceptions.txt
M docs/ref/files/file.txt
M docs/ref/request-response.txt
M docs/ref/templates/builtins.txt
M docs/ref/utils.txt
M docs/ref/validators.txt
M docs/releases/1.0-porting-guide.txt
M docs/releases/1.5-alpha-1.txt
M docs/releases/1.5-beta-1.txt
M docs/releases/1.5.txt
M docs/releases/1.6.txt
M docs/releases/1.7.txt
M docs/topics/db/examples/many_to_many.txt
M docs/topics/i18n/timezones.txt
M docs/topics/python3.txt
M docs/topics/testing/tools.txt

  Log Message:
  ---
  [1.7.x] Updated doc links to point to Python 3 documentation

Backport of 680a0f08b 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/535bbcd8e8d69_6e0bb45d344515e%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 680a0f: Updated doc links to point to Python 3 documentati...

2014-04-26 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 680a0f08b1ace39f995fce975caabb1875b07c6f
  
https://github.com/django/django/commit/680a0f08b1ace39f995fce975caabb1875b07c6f
  Author: Claude Paroz 
  Date:   2014-04-26 (Sat, 26 Apr 2014)

  Changed paths:
M docs/conf.py
M docs/intro/tutorial01.txt
M docs/intro/tutorial04.txt
M docs/ref/applications.txt
M docs/ref/contrib/auth.txt
M docs/ref/contrib/sites.txt
M docs/ref/exceptions.txt
M docs/ref/files/file.txt
M docs/ref/request-response.txt
M docs/ref/templates/builtins.txt
M docs/ref/utils.txt
M docs/ref/validators.txt
M docs/releases/1.0-porting-guide.txt
M docs/releases/1.5-alpha-1.txt
M docs/releases/1.5-beta-1.txt
M docs/releases/1.5.txt
M docs/releases/1.6.txt
M docs/releases/1.7.txt
M docs/topics/db/examples/many_to_many.txt
M docs/topics/i18n/timezones.txt
M docs/topics/python3.txt
M docs/topics/testing/tools.txt

  Log Message:
  ---
  Updated doc links to point to Python 3 documentation


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

Re: [Django] #3214: [patch] raw sql file doesn't recognize quotes correctly

2014-04-26 Thread Django

#3214: [patch] raw sql file doesn't recognize quotes correctly
-+-
 Reporter:  shaunc  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Ready for
 Keywords:  rawsql migrations|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 Thanks a lot for the review!

 I don't think the assert on the number on statements is useful. I'll just
 remove it.

 What matters is that each statement creates an object and that 9 objects
 are created.

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

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

[django/django] 6d6af7: Sycned .hginore with .gitignore.

2014-04-26 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6d6af7244b7e3c42ef77c89d6c3e8e0e79e7176f
  
https://github.com/django/django/commit/6d6af7244b7e3c42ef77c89d6c3e8e0e79e7176f
  Author: Florian Apolloner 
  Date:   2014-04-26 (Sat, 26 Apr 2014)

  Changed paths:
M .hgignore

  Log Message:
  ---
  Sycned .hginore with .gitignore.


-- 
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/535bb73be1e97_71edd53d3812126%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22522: doc error in "Limiting the maximum number of form"

2014-04-26 Thread Django

#22522: doc error in "Limiting the maximum number of form"
---+--
 Reporter:  daizhan@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timo):

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


Comment:

 The sentence looks correct to me, i.e. if max_num > existing objects, then
 it's safe to add extra forms.

-- 
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/073.a877e7c72f95a60d53dce9e74aab0a8c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #3214: [patch] raw sql file doesn't recognize quotes correctly

2014-04-26 Thread Django

#3214: [patch] raw sql file doesn't recognize quotes correctly
-+-
 Reporter:  shaunc  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Ready for
 Keywords:  rawsql migrations|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by claudep):

 Thanks Aymeric, nice patch!

 There are however test failures in initial_sql_regress, I had to apply
 this:
 {{{
 --- a/tests/initial_sql_regress/tests.py
 +++ b/tests/initial_sql_regress/tests.py
 @@ -27,7 +27,10 @@ class InitialSQLTests(TestCase):
  """
  connection = connections[DEFAULT_DB_ALIAS]
  custom_sql = custom_sql_for_model(Simple, no_style(), connection)
 -self.assertEqual(len(custom_sql), 9)
 +if connection.features.requires_sqlparse_for_splitting:
 +self.assertEqual(len(custom_sql), 9)
 +else:
 +self.assertEqual(len(custom_sql), 1)
  with connection.cursor() as cursor:
  for sql in custom_sql:
  cursor.execute(sql)
 }}}
 Apart from that, I think it's RFC.

-- 
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/086.fa925bce3ad5e73ea675af7a80faa016%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22521: Moderinze CSV export docs to cover UTF8 sheets.

2014-04-26 Thread Django

#22521: Moderinze CSV export docs to cover UTF8 sheets.
-+-
 Reporter:  brycenesbitt |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.6
Component:  Documentation|   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:  csv  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by claudep):

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


Comment:

 I'm not sure it's the role of Django to promote workaround hacks for
 proprietary software. BOM markers seem to be controversial for UTF-8
 files, so let's that for blogs or Django snippets.
 I'm closing the ticket for now, but feel free to open a discussion on
 django-dev mailing list, and reopen it if you get support.

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

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

[django/django] 0707b8: Fixed #22328 -- Added --exclude option to compilem...

2014-04-26 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 0707b824fe77e08ca8b75fcc3738ada694f2a3a6
  
https://github.com/django/django/commit/0707b824fe77e08ca8b75fcc3738ada694f2a3a6
  Author: Ana Krivokapic 
  Date:   2014-04-26 (Sat, 26 Apr 2014)

  Changed paths:
M AUTHORS
M django/core/management/commands/compilemessages.py
M django/core/management/commands/makemessages.py
M docs/man/django-admin.1
M docs/ref/django-admin.txt
M docs/releases/1.8.txt
A tests/i18n/exclude/__init__.py
A tests/i18n/exclude/canned_locale/en/LC_MESSAGES/django.po
A tests/i18n/exclude/canned_locale/fr/LC_MESSAGES/django.po
A tests/i18n/exclude/canned_locale/it/LC_MESSAGES/django.po
M tests/i18n/test_compilation.py
M tests/i18n/test_extraction.py

  Log Message:
  ---
  Fixed #22328 -- Added --exclude option to compilemessages and makemessages.


-- 
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/535b85f28e55_73f76f9d3429176%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[Django] #22522: doc error in "Limiting the maximum number of form"

2014-04-26 Thread Django

#22522: doc error in "Limiting the maximum number of form"
---+
 Reporter:  daizhan@…  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 "If the value of max_num is greater than the number of existing objects,
 up to extra additional blank forms will be added to the formset, so long
 as the total number of forms does not exceed max_num."
 the above paragraph has a writing error, "the value of max_num is smaller,
 not greater, than the number of existing objects ..."
 [https://docs.djangoproject.com/en/1.7/topics/forms/formsets/#limiting-
 the-maximum-number-of-forms]

-- 
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/058.14ce7578ebb4af1e1ce2fb6f1406b968%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #3214: [patch] raw sql file doesn't recognize quotes correctly

2014-04-26 Thread Django

#3214: [patch] raw sql file doesn't recognize quotes correctly
-+-
 Reporter:  shaunc  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Ready for
 Keywords:  rawsql migrations|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * has_patch:  0 => 1


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

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

Re: [Django] #3214: [patch] raw sql file doesn't recognize quotes correctly

2014-04-26 Thread Django

#3214: [patch] raw sql file doesn't recognize quotes correctly
-+-
 Reporter:  shaunc  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Ready for
 Keywords:  rawsql migrations|  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * stage:  Accepted => Ready for checkin


Comment:

 I think this is good to go: https://github.com/django/django/pull/2608

 I ran the "test_run_sql" test on all four core database backends with and
 without sqlparse. It's skipped in three cases and passes in five cases.

-- 
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/086.15e32bbeb5361808f0cbe52849db3d2b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #3214: [patch] raw sql file doesn't recognize quotes correctly

2014-04-26 Thread Django

#3214: [patch] raw sql file doesn't recognize quotes correctly
-+-
 Reporter:  shaunc  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:  rawsql migrations|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 Oracle seems to choke on `\n`:

 {{{
 DatabaseError: ORA-00911: invalid character
 }}}

-- 
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/086.89010e625f85f24672a8caaac2cdb06a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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-04-26 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|
-+-

Comment (by charettes):

Calling `order_by('team_id')` doesn't raise a `FieldError` anymore on
Django 1.7 and silently behave just like `order_by('team')`.

If we want to avoid breaking code that might rely on this in 1.7 we should
fix it now. Else we'll have to deal with this by introducing an entry
point to `order_by` in order to opt-out of this unexpected behavior.

I wrote a patch for
[https://github.com/charettes/django/compare/ticket-19195-fk-order_by-
attname the order_by issue here].

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

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

Re: [Django] #15179: django.test.client.Client.login fake HttpRequest is not run through middlewares

2014-04-26 Thread Django

#15179: django.test.client.Client.login fake HttpRequest is not run through
middlewares
---+--
 Reporter:  Ciantic|Owner:  akaariai
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.7-beta-2
 Severity:  Release blocker|   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by loic84):

 How about taking advantage of https://docs.djangoproject.com/en/dev/ref
 /request-response/#django.http.HttpRequest.urlconf.

 We could set a custom urlconf that contains a login/logout view from
 `contrib.auth` and use these.

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

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

54 matches

Mail list logo