date:20140809

Re: [Django] #14030: Use F() objects in aggregates(), annotates() and values()

2014-08-09 Thread Django

#14030: Use F() objects in aggregates(), annotates() and values()
-+-
 Reporter:  delfick  |Owner:  jarshwah
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  aggregate, annotate  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by jarshwah):

 * owner:  smeatonj => jarshwah


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

Re: [Django] #23265: Django don't start on French Windows with Python 2.7 (but only in February, August and December!) (was: Django don't start on Windows with Python 2.7 (but only in august!))

2014-08-09 Thread Django

#23265: Django don't start on French Windows with Python 2.7 (but only in 
February,
August and December!)
-+-
 Reporter:  SpaceFox |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Core (Management |  Version:  1.6
  commands)  |   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 SpaceFox):

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


Comment:

 Replying to [ticket:23265 SpaceFox]:
 > On Windows / Python 2.7, if Django is set to use the French locale
 ("fra"), an UTF8 encoding error prevents it to start with this stack
 trace:
 >
 >
 > {{{
 > Validating models...
 >
 > 0 errors found
 > Unhandled exception in thread started by 
 > Traceback (most recent call last):
 >   File "C:\Users\SpaceFox\.virtualenvs\zdsenv\lib\site-
 packages\django\utils\autoreload.py", line 93, in wrapper
 > fn(*args, **kwargs)
 >   File "C:\Users\SpaceFox\.virtualenvs\zdsenv\lib\site-
 packages\django\core\management\commands\runserver.py", line 104,
 >  in inner_run
 > now = now.decode('utf-8')
 >   File "C:\Users\SpaceFox\.virtualenvs\zdsenv\lib\encodings\utf_8.py",
 line 16, in decode
 > return codecs.utf_8_decode(input, errors, True)
 > UnicodeDecodeError: 'utf8' codec can't decode byte 0xfb in position 2:
 invalid start byte
 > }}}
 >
 > How to reproduce this:
 >
 > - Windows (tested on Windows 8.1 x64), all updates OK
 > - Python 2.7 (Python 2.7.8 (default, Jun 30 2014, 16:08:48) [MSC v.1500
 64 bit (AMD64)] on win32)
 > - Django 1.6.5
 > - In settings.py, set locale to "fra":
 {{{locale.setlocale(locale.LC_TIME, 'fra')}}}
 > - Try to launch Django with {{{python manage.py runserver}}}. Kabooom!
 >
 > The problem comes for the django/core/management/commands/runserver.py
 line 102 to 104 :
 >
 > {{{
 > now = datetime.now().strftime('%B %d, %Y - %X')
 > if six.PY2:
 > now = now.decode('utf-8')
 > }}}
 >
 > These 3 lines suppose the strftime method returns an UTF-8 string...
 this is false when Django runs on Windows with Python 2.7.
 >
 > In French language, 3 month names have non-ASCII characters: "février",
 "août" and "décembre" (February, August and December).
 >
 > With described parameters, {{{now}}} is set as "ao¹t 09, 2014 -
 00:56:41". The crap that replaces the "û" character in "août" contains the
 0xfb character, which is illegal in UTF-8. This create the crash.
 >
 > The problem is the same in February and December due to the 0xe9 byte in
 {{{now}}}, caused by the "é" character.
 >
 > With other non-ASCII characters, this may "work" as long as there is no
 illegal byte in the given string: the output of this function will be
 broken (not what is expected) but there will be no exception thrown.
 >
 > I don't know how to correct this, therefore I can't provide any patch.

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

[Django] #23265: Django don't start on Windows with Python 2.7 (but only in august!)

2014-08-09 Thread Django

#23265: Django don't start on Windows with Python 2.7 (but only in august!)
+
 Reporter:  SpaceFox|  Owner:  nobody
 Type:  Uncategorized   | Status:  new
Component:  Core (Management commands)  |Version:  1.6
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 On Windows / Python 2.7, if Django is set to use the French locale
 ("fra"), an UTF8 encoding error prevents it to start with this stack
 trace:


 {{{
 Validating models...

 0 errors found
 Unhandled exception in thread started by 
 Traceback (most recent call last):
   File "C:\Users\SpaceFox\.virtualenvs\zdsenv\lib\site-
 packages\django\utils\autoreload.py", line 93, in wrapper
 fn(*args, **kwargs)
   File "C:\Users\SpaceFox\.virtualenvs\zdsenv\lib\site-
 packages\django\core\management\commands\runserver.py", line 104,
  in inner_run
 now = now.decode('utf-8')
   File "C:\Users\SpaceFox\.virtualenvs\zdsenv\lib\encodings\utf_8.py",
 line 16, in decode
 return codecs.utf_8_decode(input, errors, True)
 UnicodeDecodeError: 'utf8' codec can't decode byte 0xfb in position 2:
 invalid start byte
 }}}

 How to reproduce this:

 - Windows (tested on Windows 8.1 x64), all updates OK
 - Python 2.7 (Python 2.7.8 (default, Jun 30 2014, 16:08:48) [MSC v.1500 64
 bit (AMD64)] on win32)
 - Django 1.6.5
 - In settings.py, set locale to "fra": {{{locale.setlocale(locale.LC_TIME,
 'fra')}}}
 - Try to launch Django with {{{python manage.py runserver}}}. Kabooom!

 The problem comes for the django/core/management/commands/runserver.py
 line 102 to 104 :

 {{{
 now = datetime.now().strftime('%B %d, %Y - %X')
 if six.PY2:
 now = now.decode('utf-8')
 }}}

 These 3 lines suppose the strftime method returns an UTF-8 string... this
 is false when Django runs on Windows with Python 2.7.

 In French language, 3 month names have non-ASCII characters: "février",
 "août" and "décembre" (February, August and December).

 With described parameters, {{{now}}} is set as "ao¹t 09, 2014 - 00:56:41".
 The crap that replaces the "û" character in "août" contains the 0xfb
 character, which is illegal in UTF-8. This create the crash.

 The problem is the same in February and December due to the 0xe9 byte in
 {{{now}}}, caused by the "é" character.

 With other non-ASCII characters, this may "work" as long as there is no
 illegal byte in the given string: the output of this function will be
 broken (not what is expected) but there will be no exception thrown.

 I don't know how to correct this, therefore I can't provide any patch.

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

Re: [Django] #23173: SCRIPT_URL on WSGI is misinterpreted when PATH_INFO is empty

2014-08-09 Thread Django

#23173: SCRIPT_URL on WSGI is misinterpreted when PATH_INFO is empty
-+-
 Reporter:  j-sz@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  wsgi, script name,   | Triage Stage:  Accepted
  negative index slicing |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by janek37):

 One way to reproduce this bug is to run in a Django console:

 {{{
 from django.core.handlers.wsgi import get_script_name
 get_script_name({'SCRIPT_URL': '/foobar/'})
 }}}

 I'm not sure it's what you're looking for, but it does the job.

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

Re: [Django] #23173: SCRIPT_URL on WSGI is misinterpreted when PATH_INFO is empty

2014-08-09 Thread Django

#23173: SCRIPT_URL on WSGI is misinterpreted when PATH_INFO is empty
-+-
 Reporter:  j-sz@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  wsgi, script name,   | Triage Stage:  Accepted
  negative index slicing |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by bmispelon):

 Also, I took a quick look at other instances of `'\[:-[^0-9]'` and they
 all seem OK except maybe one.

 There's one in
 
https://github.com/django/django/blob/master/django/contrib/staticfiles/storage.py#L180
 that could be an issue but I couldn't figure out if there's actually a way
 to trigger the problematic case.
 If you can figure it out, please open a separate ticket.

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

Re: [Django] #23173: SCRIPT_URL on WSGI is misinterpreted when PATH_INFO is empty

2014-08-09 Thread Django

* stage: Unreviewed => Accepted

Comment:

OK, marking this as `accepted`.

FYI, it's easier for me to triage your ticket if you provide a concrete
example of how to trigger the bug because then I know how to try and
reproduce it.

If you just point to a line of code, I have to try and figure out
where/how that code is used and see if there's a way to trigger the bug in
a normal use-case. This can be hard and time consuming, especially if I'm
not familiar with the codebase (which is the case here for example).

This is why I asked for more details in my first comment.

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

Re: [Django] #19570: call_command options

2014-08-09 Thread Django

#19570: call_command options
-+-
 Reporter:  leftmoose|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core (Management |   Resolution:
  commands)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  1
 Keywords:  call_command, docs   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by claudep):

 I guess the patch I proposed for #22985 would solve this issue, too.

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

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

Re: [Django] #22985: call_command() ignores dest from make_option() and uses kwarg name instead

2014-08-09 Thread Django

#22985: call_command() ignores dest from make_option() and uses kwarg name 
instead
-+-
 Reporter:  giuliettamasina  |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:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

 * has_patch:  0 => 1


Comment:

 https://github.com/django/django/pull/3038

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

Re: [Django] #23173: SCRIPT_URL on WSGI is misinterpreted when PATH_INFO is empty

2014-08-09 Thread Django

#23173: SCRIPT_URL on WSGI is misinterpreted when PATH_INFO is empty
-+-
 Reporter:  j-sz@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  wsgi, script name,   | Triage Stage:
  negative index slicing |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by janek37):

 Replying to [comment:1 bmispelon]:
 > Isn't `path_info` guaranteed to be non-empty because of
 
https://github.com/django/django/blob/master/django/core/handlers/wsgi.py#L87-L92?

 No, it isn't. Look at it in context:
 
https://github.com/django/django/blob/master/django/core/handlers/wsgi.py#L233-L235.
 It reads PATH_INFO straight from the environment and it assumes an empty
 string if the variable is not set.

 >
 > Could you give us some details on what error you're seeing and how
 you're triggering it?
 >
 > Thanks.

 In my evironment the PATH_INFO variable is not set. I don't get any error
 message, I just get wrong urls when calling
 django.core.urlresolvers.reverse or {% url %} template tag. Eg. I have a
 WSGI server at /foobar/ and the resolve function returns '/some/url/'
 instead of '/foobar/some/url/'. Easy to see, when SCRIPT_URL variable is
 set to '/foobar/' and PAT_INFO is not set, get_script_name(environ) will
 return '' while it should return '/foobar/'. Just look at the code, it's
 obvious:
 
https://github.com/django/django/blob/master/django/core/handlers/wsgi.py#L229-L237

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

Re: [Django] #23236: forms.Form should support a Meta class like forms.ModelForm

2014-08-09 Thread Django

#23236: forms.Form should support a Meta class like forms.ModelForm
-+--
 Reporter:  django@… |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 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 bmispelon):

 I don't see what's "un-DRY" about extending the `__init__()` method and
 setting up the widget there.

 I like the plain `Form`'s (relative) simplicity and lack of a "magic"
 `Meta` class.
 Overriding things in `__init__()` is the normal Python way of doing
 things.

 All-in-all, I'm -0 on the idea.

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

Re: [Django] #23173: SCRIPT_URL on WSGI is misinterpreted when PATH_INFO is empty

2014-08-09 Thread Django

#23173: SCRIPT_URL on WSGI is misinterpreted when PATH_INFO is empty
-+-
 Reporter:  j-sz@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  wsgi, script name,   | Triage Stage:
  negative index slicing |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by bmispelon):

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


Comment:

 Isn't `path_info` guaranteed to be non-empty because of
 
https://github.com/django/django/blob/master/django/core/handlers/wsgi.py#L87-L92?

 Could you give us some details on what error you're seeing and how you're
 triggering 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/068.f68c073680cf8ed6fc3d32d180ad99db%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23222: Empty BinaryField != b'' on Python 2

2014-08-09 Thread Django

#23222: Empty BinaryField != b'' on Python 2
-+-
 Reporter:  wkschwartz@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by bmispelon):

 * stage:  Unreviewed => Accepted


Comment:

 Marking this as accepted per previous comments.

 This seem like it might be caused by six using buffers on python 2 [1].

 Thanks.

 [1] https://github.com/django/django/blob/master/django/utils/six.py#L681

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

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

[django/django] dc462a: Removed unused migrate option

2014-08-09 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: dc462a8ed55edacd71709f3db6fd225296871927
  
https://github.com/django/django/commit/dc462a8ed55edacd71709f3db6fd225296871927
  Author: Claude Paroz 
  Date:   2014-08-09 (Sat, 09 Aug 2014)

  Changed paths:
M django/core/management/commands/migrate.py
M django/db/backends/creation.py

  Log Message:
  ---
  Removed unused migrate option


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

Re: [Django] #22267: django.utils.html.smart_urlquote() is incorrectly unquoting the url

2014-08-09 Thread Django

#22267: django.utils.html.smart_urlquote() is incorrectly unquoting the url
---+
 Reporter:  meenzam@…  |Owner:  ienzam
 Type:  Bug|   Status:  assigned
Component:  Utilities  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by claudep):

 * needs_better_patch:  1 => 0


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

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

Re: [Django] #23264: db_constraint=False not enforced on migrations

2014-08-09 Thread Django

#23264: db_constraint=False not enforced on migrations
-+
 Reporter:  jmacul2  |Owner:  andrewgodwin
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-rc-2
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Andrew Godwin ):

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


Comment:

 In [changeset:"ee74f9fe3bcd8c2648e4623d5929fceac851b97f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ee74f9fe3bcd8c2648e4623d5929fceac851b97f"
 [1.7.x] Fixed #23264: Schema backends honour db_constraint
 }}}

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

[django/django] ee74f9: [1.7.x] Fixed #23264: Schema backends honour db_co...

2014-08-09 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: ee74f9fe3bcd8c2648e4623d5929fceac851b97f
  
https://github.com/django/django/commit/ee74f9fe3bcd8c2648e4623d5929fceac851b97f
  Author: Andrew Godwin 
  Date:   2014-08-09 (Sat, 09 Aug 2014)

  Changed paths:
M django/db/backends/schema.py
M tests/schema/models.py
M tests/schema/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #23264: Schema backends honour db_constraint


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

[django/django] 27b6f2: Fixed #23264: Schema backends honour db_constraint

2014-08-09 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 27b6f284353a7a477a1a0ae4beffd12003a91fb5
  
https://github.com/django/django/commit/27b6f284353a7a477a1a0ae4beffd12003a91fb5
  Author: Andrew Godwin 
  Date:   2014-08-09 (Sat, 09 Aug 2014)

  Changed paths:
M django/db/backends/schema.py
M tests/schema/models.py
M tests/schema/tests.py

  Log Message:
  ---
  Fixed #23264: Schema backends honour db_constraint


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

Re: [Django] #23264: db_constraint=False not enforced on migrations

2014-08-09 Thread Django

#23264: db_constraint=False not enforced on migrations
-+
 Reporter:  jmacul2  |Owner:  andrewgodwin
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-rc-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by andrewgodwin):

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


Comment:

 Ah, I didn't even know we had db_constraint! Adding 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/065.c2d581ee1ff533f0eb4ccf497b8864f2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #14030: Use F() objects in aggregates(), annotates() and values()

Re: [Django] #23265: Django don't start on French Windows with Python 2.7 (but only in February, August and December!) (was: Django don't start on Windows with Python 2.7 (but only in august!))

[Django] #23265: Django don't start on Windows with Python 2.7 (but only in august!)

Re: [Django] #23173: SCRIPT_URL on WSGI is misinterpreted when PATH_INFO is empty

Re: [Django] #23173: SCRIPT_URL on WSGI is misinterpreted when PATH_INFO is empty

Re: [Django] #23173: SCRIPT_URL on WSGI is misinterpreted when PATH_INFO is empty

Re: [Django] #19570: call_command options

Re: [Django] #22985: call_command() ignores dest from make_option() and uses kwarg name instead

Re: [Django] #23173: SCRIPT_URL on WSGI is misinterpreted when PATH_INFO is empty

Re: [Django] #23236: forms.Form should support a Meta class like forms.ModelForm

Re: [Django] #23173: SCRIPT_URL on WSGI is misinterpreted when PATH_INFO is empty

Re: [Django] #23222: Empty BinaryField != b'' on Python 2

[django/django] dc462a: Removed unused migrate option

Re: [Django] #22267: django.utils.html.smart_urlquote() is incorrectly unquoting the url

Re: [Django] #23264: db_constraint=False not enforced on migrations

[django/django] ee74f9: [1.7.x] Fixed #23264: Schema backends honour db_co...

[django/django] 27b6f2: Fixed #23264: Schema backends honour db_constraint

Re: [Django] #23264: db_constraint=False not enforced on migrations

18 matches

Site Navigation

Mail list logo

Footer information