[Django] #22188: actually weight loss

2014-03-02 Thread Django 
#22188: actually weight loss
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I do something my worst fears just going to sleep and not waking up in the
 morning in something as hardest thing for me PhD research to know that he
 attacked amass now I'll added yeah and I'm here long you that's why I my
 watch videos P and scary to me you know and that I mean thing bad he can
 actually deiform that is something that thank I mean mind-blowing okay I
 can I can I had no
 [url="http://nutratoneplusblog.com/"]NUTRA TONE PLUS[/url] idea and I cud
 and the gym and the so I am I mean the Selene mister I'm dating about it
 and actually stake I'll hours the turning point for me I think unique you
 light yourself so on me just gets up on me like you know why need to
 change need to change everything of on towers the breaking point for me
 ever since then worked out have been try my best to lose the weight
 because I don't wannadie I feel like every night when I go to sleep at one
 year from in a wake up and I’m and how I do that and really want crisis
 how to be able to take me to that next level to be able to lose on my way
 hard me today the boy ever since.
 [http://nutratoneplusblog.com/]

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

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

[Django] #22187: usually weigh loss

2014-03-02 Thread Django 
#22187: usually weigh loss
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I do have Google and your six-month call it's going to be Liz 55 pounds 55
 pounds may seem so easy compared tithe eighty pounds but we're getting
 down to the nitty-gritty this is the next phase for your face to go and
 call it a milestone it's physical monster we've actually getting
 appreciate and and [url="http://nutratoneplusblog.com/"]NUTRA TONE
 PLUS[/url] experiences the body you been working really fun now we
 California is for you want to be 203 Verizon mass it's not set in yet that
 he's that I'm doing this on my own now and I have that nervousness and
 Fatima summit I believe in %um by because when I'm usually by myself Icon
 acquit you got this Rachel but I'm going to go into it and I'm going to
 give it my all and I'm going to do my best to you me this next go in and
 get ready for my mouse on 31 Mar on now to love this here in the last time
 I had a real vacation and now I'm getting to spend in grief remember other
 and I get to spend it at 289 pounds fees beautiful but again I'm that
 thesis such a beautiful place.
 http://nutratoneplusblog.com/

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

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

[Django] #22186: completely renovated weight loss

2014-03-02 Thread Django 
#22186: completely renovated weight loss
---+
 Reporter:  jali.jal   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 yes we want to eat lots of fruits and vegetables but it really is helpful
 to keep a supply of frozen fruits and vegetables available at all times to
 back up that fresh they're just as nutritious and they can stay in your
 freezer up to six months really important to have the right foods
 [url="http://nutratoneplusblog.com/"]NUTRA TONE PLUS[/url]
  available all times so you can maintain a healthy lifestyle go are back
 home now to cancel done I gottatake actually home felt like forever since
 I've been back go out welcome all as she's a boot camp my crew came in
 completely renovated your spy Jan we took her living weeks from the beach
 is beautiful Jehu believers say now in addition I have my crew bring in
 all these different tools offer food preparation we got her everything
 that she needs to make this process easy and fun because it has to be
 reasonable lifestyle has to be sustainable don’t think I've have it to my
 living here yeah now to Maria you three months of everything when it comes
 to these transformations broken in two phases phase
 http://nutratoneplusblog.com/

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

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

Re: [Django] #22125: Unnecessary creation of index for ManyToManyField

2014-03-02 Thread Django 
#22125: Unnecessary creation of index for ManyToManyField
-+-
 Reporter:  tbhtan3@…|Owner:  bwreilly
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.6
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by bwreilly):

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


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

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

Re: [Django] #21188: Use DeprecationWarning subclasses for deprecated features

2014-03-02 Thread Django 
#21188: Use DeprecationWarning subclasses for deprecated features
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core (Other) |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * stage:  Accepted => Ready for checkin


Comment:

 Reviewed the PR by moving warnings subclasses from
 `django.core.exceptions` to `django.utils.deprecation` and it seems to be
 completed.

 I ran the full test suite against the {Py2, Py3} X {SQLite3, PostgreSQL}
 matrix with `python -Wonce` and didn't get any failures or warnings
 (except the already existing wizard ones on Py3).

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

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

2014-03-02 Thread Django 
#22019: add section for definitive Model.objects documentation
--+
 Reporter:  cjerdonek |Owner:  nheyning
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:  models nlsprint14 | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by cjerdonek):

 * status:  closed => new
 * resolution:  fixed =>
 * stage:  Ready for checkin => Accepted


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

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

2014-03-02 Thread Django 
#22019: add section for definitive Model.objects documentation
-+-
 Reporter:  cjerdonek|Owner:  nheyning
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.6
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  models nlsprint14|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by cjerdonek):

 Reopening to address the two points in my previous comment (hyperlinking
 and adding to the reference section).

 Yes, I agree that with the current section organization of the model
 reference section, it's not clear where an `objects` class attribute
 should go (all of the sections are titled somewhat specifically).

 Looking at the sections more carefully, I think the most natural location
 is probably the
 [https://docs.djangoproject.com/en/dev/ref/models/instances/ Model
 instance reference] section, even though strictly speaking that section is
 about instance attributes and methods rather than class attributes.  But
 the introductory sentence does read, "This document describes the details
 of the Model API."  Also, early on in the "Creating objects" subsection,
 the page does discuss adding a custom `objects` manager.

 If we want to be more correct with the title, we could even consider
 changing the title to the more general "Model class reference."

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

[django/django] 90577c: Removed WSGI upgrade instructions for Django 1.3 a...

2014-03-02 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 90577c0eb4f46352322d5911e1d7ae69dcf149e7
  
https://github.com/django/django/commit/90577c0eb4f46352322d5911e1d7ae69dcf149e7
  Author: Tim Graham 
  Date:   2014-03-02 (Sun, 02 Mar 2014)

  Changed paths:
M docs/howto/deployment/wsgi/index.txt

  Log Message:
  ---
  Removed WSGI upgrade instructions for Django 1.3 and earlier.


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

Re: [Django] #16727: contrib.contenttypes.views.shortcut error

2014-03-02 Thread Django 
#16727: contrib.contenttypes.views.shortcut error
--+
 Reporter:  anonymous |Owner:  tcsorrel
 Type:  Bug   |   Status:  assigned
Component:  contrib.contenttypes  |  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 tcsorrel):

 * needs_tests:  1 => 0


Comment:

 Please find a fix with the corresponding tests included in this pull
 request :
 https://github.com/django/django/pull/2388
 I preferred not to use regular expression thinking that 3 "startswith"
 tests might be faster.

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

Re: [Django] #22114: URLField form adds trailing slash to pathless URLs

2014-03-02 Thread Django 
#22114: URLField form adds trailing slash to pathless URLs
-+
 Reporter:  coredumperror@…  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by claudep):

 You're right, I probably read #11826 too quickly. I just uploaded a new
 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/081.ea3c7db76e440bda52289469528e2bae%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17642: min_num on admin inline formsets

2014-03-02 Thread Django 
#17642: min_num on admin inline formsets
-+-
 Reporter:   |Owner:  tback
  krzysztof.szczesny@…   |   Status:  assigned
 Type:  New feature  |  Version:
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  admin min_num|  Needs documentation:  0
  formsets   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  1
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by asteinlein):

 * cc: anders@… (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/086.d030f60049d962fe7151269e59a694d8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18381: Underscore in CharField primary key breaks the admin "view on site" link

2014-03-02 Thread Django 
#18381: Underscore in CharField primary key breaks the admin "view on site" link
-+-
 Reporter:  dappawit |Owner:  apollo13
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  0|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by timo):

 * version:  1.6 => 1.4


Comment:

 Please open a new ticket for related issues, rather than reopening a
 ticket where the fix has already been released. 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/066.101bf1815a50e9ca7a93a23788141552%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18381: Underscore in CharField primary key breaks the admin "view on site" link

2014-03-02 Thread Django 
#18381: Underscore in CharField primary key breaks the admin "view on site" link
-+-
 Reporter:  dappawit |Owner:  apollo13
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.4
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  0|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by timo):

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


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

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

Re: [Django] #15995: Problems in ModelForm._post_clean

2014-03-02 Thread Django 
#15995: Problems in ModelForm._post_clean
--+
 Reporter:  apollo13  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Forms |  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 anubhav9042):

 Its
 [https://github.com/django/django/blob/master/django/forms/models.py#L406]
 and
 [https://github.com/django/django/blob/master/django/forms/models.py#L408]
 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/066.39e2486f516c0886f452e4e5de1c5901%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22185: CSRF cookie should be configurable

2014-03-02 Thread Django 
#22185: CSRF cookie should be configurable
--+
 Reporter:  rogerhu   |  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  contrib.csrf  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+
 Internet Explorer has the ability to block/disable persistent cookies
 (http://support.microsoft.com/kb/196955), and corruption of the index.dat
 cache
 (i.e. disk errors that need to be repaired via CHKDSK) can cause Django
 sites to authenticate correctly but fail to do FORM POST's.  To
 avoid this behavior, provide the option to configure the CSRF cookie age
 so that cookies can be configured to be persistent or session-based.

 Changes (including test and documentation) are included here:

 https://github.com/django/django/pull/2387/files

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

[django/django] 4aaea2: [1.6.x] Fixed some typos in the documentation.

2014-03-02 Thread GitHub 
  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 4aaea2921d7c98dd98fc99596239f8863cb312cc
  
https://github.com/django/django/commit/4aaea2921d7c98dd98fc99596239f8863cb312cc
  Author: Baptiste Mispelon 
  Date:   2014-03-02 (Sun, 02 Mar 2014)

  Changed paths:
M docs/glossary.txt
M docs/intro/tutorial05.txt
M docs/ref/contrib/formtools/form-wizard.txt
M docs/ref/contrib/gis/commands.txt
M docs/ref/contrib/gis/geoquerysets.txt
M docs/ref/contrib/gis/measure.txt
M docs/ref/contrib/gis/testing.txt
M docs/topics/auth/customizing.txt

  Log Message:
  ---
  [1.6.x] Fixed some typos in the documentation.

Thanks to Rodolfo Carvalho and Piotr Kasprzyk
for the patch.

Partial backport of ea4da8e63c314b4f7cbcb4dd06eef466c1e872ed 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/53135ac63597_15b11157d44636f2%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] ea4da8: Fixed some typos in the documentation.

2014-03-02 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ea4da8e63c314b4f7cbcb4dd06eef466c1e872ed
  
https://github.com/django/django/commit/ea4da8e63c314b4f7cbcb4dd06eef466c1e872ed
  Author: Baptiste Mispelon 
  Date:   2014-03-02 (Sun, 02 Mar 2014)

  Changed paths:
M docs/glossary.txt
M docs/intro/tutorial05.txt
M docs/ref/checks.txt
M docs/ref/contrib/formtools/form-wizard.txt
M docs/ref/contrib/gis/commands.txt
M docs/ref/contrib/gis/geoquerysets.txt
M docs/ref/contrib/gis/measure.txt
M docs/ref/contrib/gis/testing.txt
M docs/ref/migration-operations.txt
M docs/topics/auth/customizing.txt

  Log Message:
  ---
  Fixed some typos in the documentation.

Thanks to Rodolfo Carvalho and Piotr Kasprzyk
for the patch.


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

Re: [Django] #22130: Accelerated deprecation fix_ampersands and clean_html

2014-03-02 Thread Django 
#22130: Accelerated deprecation fix_ampersands and clean_html
-+-
 Reporter:  erikr|Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Utilities|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  nlsprint14   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Erik Romijn ):

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


Comment:

 In [changeset:"6268792e19ab37446e438f4777c0bb8e786c5c3f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6268792e19ab37446e438f4777c0bb8e786c5c3f"
 Fixed #22130 -- fixed template_tests/defaultfilters order dependent test
 failure
 }}}

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

Re: [Django] #22130: Accelerated deprecation fix_ampersands and clean_html

2014-03-02 Thread Django 
#22130: Accelerated deprecation fix_ampersands and clean_html
-+-
 Reporter:  erikr|Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Utilities|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  nlsprint14   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"a08f906556c14357852bbc9c4c7d10c6558dafcf"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a08f906556c14357852bbc9c4c7d10c6558dafcf"
 Merge pull request #2383 from erikr/fix-tests-fix-ampersands-deprecation

 Fixed #22130 -- fixed template_tests/defaultfilters order dependent test
 failure
 }}}

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

[django/django] 626879: Fixed #22130 -- fixed template_tests/defaultfilter...

2014-03-02 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6268792e19ab37446e438f4777c0bb8e786c5c3f
  
https://github.com/django/django/commit/6268792e19ab37446e438f4777c0bb8e786c5c3f
  Author: Erik Romijn 
  Date:   2014-03-02 (Sun, 02 Mar 2014)

  Changed paths:
M tests/defaultfilters/tests.py

  Log Message:
  ---
  Fixed #22130 -- fixed template_tests/defaultfilters order dependent test 
failure


  Commit: a08f906556c14357852bbc9c4c7d10c6558dafcf
  
https://github.com/django/django/commit/a08f906556c14357852bbc9c4c7d10c6558dafcf
  Author: Aymeric Augustin 
  Date:   2014-03-02 (Sun, 02 Mar 2014)

  Changed paths:
M tests/defaultfilters/tests.py

  Log Message:
  ---
  Merge pull request #2383 from erikr/fix-tests-fix-ampersands-deprecation

Fixed #22130 -- fixed template_tests/defaultfilters order dependent test failure


Compare: https://github.com/django/django/compare/7ba29189fabc...a08f906556c1

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

Re: [Django] #22130: Accelerated deprecation fix_ampersands and clean_html

2014-03-02 Thread Django 
#22130: Accelerated deprecation fix_ampersands and clean_html
-+-
 Reporter:  erikr|Owner:  aaugustin
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Utilities|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  nlsprint14   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 I spend some time working on this and I cannot figure out what's going on.
 It doesn't appear to be related to warning filters. If you insert the
 following code in `test_fix_ampersands`:

 {{{
 print("\n\nWARNING STATE\n")
 for f in warnings.filters:
 print(f)
 if f[1] and f[1].pattern: print('' + f[1].pattern)
 if f[3] and f[3].pattern: print('' + f[3].pattern)
 }}}

 you can see that the warning filters are exactly identical with or without
 running the `template_tests` first, even though captured warnings are
 different .

 While attempting to nail down the issue, I hit #22184, and that's more
 work than I'm willing to do just to test a deprecation warning that very
 obviously works. I don't want to waste more time on this, so I'll just
 merge Erik's pull request.

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

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

[Django] #22184: template_tests relies on leaking state

2014-03-02 Thread Django 
#22184: template_tests relies on leaking state
---+
   Reporter:  aaugustin|  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  Template system  |Version:  master
   Severity:  Normal   |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 `./runtests.py template_tests.tests` fails with a very long output, which
 simply says that the template loaders failed to locate the
 `inclusion.html` template.

 `./runtests.py template_tests.test_loaders template_tests.tests` works.

 We should figure out what part of `template_tests.test_loaders`
 `template_tests.tests` depends on and make it possible to run
 `template_tests.tests` by itself.

 I discovered this while working on
 https://code.djangoproject.com/ticket/22130#comment:10.

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

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

Re: [Django] #16727: contrib.contenttypes.views.shortcut error

2014-03-02 Thread Django 
#16727: contrib.contenttypes.views.shortcut error
--+
 Reporter:  anonymous |Owner:  tcsorrel
 Type:  Bug   |   Status:  assigned
Component:  contrib.contenttypes  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by tcsorrel):

 * owner:  nobody => tcsorrel
 * status:  new => assigned
 * cc: thomas@… (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/067.65b6c43b9760952e1401d814d027f316%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22183: Migrations don't work with custom through table on M2M fields

2014-03-02 Thread Django 
#22183: Migrations don't work with custom through table on M2M fields
-+-
 Reporter:  apollo13 |Owner:
 Type:  Bug  |  andrewgodwin
Component:  Migrations   |   Status:  new
 Severity:  Release blocker  |  Version:  master
 Keywords:  sql, migrations, |   Resolution:
  m2m| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by MarkusH):

 * cc: info@… (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.60676458e83a2c70cc610ed1b52ddb7e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 7ba291: Restored aliases for two APIs removed by app-loadi...

2014-03-02 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7ba29189fabccdfde34071846bc08252588554d7
  
https://github.com/django/django/commit/7ba29189fabccdfde34071846bc08252588554d7
  Author: Aymeric Augustin 
  Date:   2014-03-02 (Sun, 02 Mar 2014)

  Changed paths:
M django/db/models/loading.py

  Log Message:
  ---
  Restored aliases for two APIs removed by app-loading.


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

Re: [Django] #22183: Migrations don't work with custom through table on M2M fields

2014-03-02 Thread Django 
#22183: Migrations don't work with custom through table on M2M fields
-+-
 Reporter:  apollo13 |Owner:
 Type:  Bug  |  andrewgodwin
Component:  Migrations   |   Status:  new
 Severity:  Release blocker  |  Version:  master
 Keywords:  sql, migrations, |   Resolution:
  m2m| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by apollo13):

 Attached patch fixes it for me; but now the migrations are created oddly:
 {{{
 Migrations for 'testing':
   0001_initial.py:
 - Create model Test1
 - Create model M2M
 - Create model Test2
   0001_m2m_test2.py:
 - Add field test2 to m2m
 }}}
 If it would create Test1 and Test2 first it wouldn't need two migrations.

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

Re: [Django] #22183: Migrations don't work with custom through table on M2M fields (was: Migrations don't work reliably with M2M fields.)

2014-03-02 Thread Django 
#22183: Migrations don't work with custom through table on M2M fields
-+-
 Reporter:  apollo13 |Owner:
 Type:  Bug  |  andrewgodwin
Component:  Migrations   |   Status:  new
 Severity:  Release blocker  |  Version:  master
 Keywords:  sql, migrations, |   Resolution:
  m2m| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by apollo13):

 The main issue seems to be that the migration is created as follows:
 {{{
 migrations.CreateModel(
 name='Test2',
 fields=[
 (u'id', models.AutoField(verbose_name=u'ID',
 serialize=False, auto_created=True, primary_key=True)),
 ('m2m', models.ManyToManyField(to='testing.Test1')),
 ],
 options={
 },
 bases=(models.Model,),
 ),
 }}}
 This means the through property is not considered, and as such Django
 correctly tries to create `testing_test2_m2m` 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/066.e9982e1468ffeb74f552767d95d84685%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22183: Migrations don't work reliably with M2M fields.

2014-03-02 Thread Django 
#22183: Migrations don't work reliably with M2M fields.
-+-
   Reporter:  apollo13   |  Owner:  andrewgodwin
   Type:  Bug| Status:  new
  Component: |Version:  master
  Migrations |   Keywords:  sql, migrations,
   Severity:  Release|  m2m
  blocker|  Has patch:  0
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 Given those models:
 {{{
 from django.db import models
 #from taggit.managers import *


 class M2M(models.Model):
 test1 = models.ForeignKey('Test1', related_name='+')
 test2 = models.ForeignKey('Test2', related_name='+')

 class Test1(models.Model):
 pass

 class Test2(models.Model):
 m2m = models.ManyToManyField(Test1, through=M2M)

 #class Test3(models.Model):
 #tags = TaggableManager()
 }}}

 The created schema will look like:
 {{{
 CREATE TABLE "testing_test1" ("id" integer NOT NULL PRIMARY KEY
 AUTOINCREMENT);
 CREATE TABLE "testing_test2" ("id" integer NOT NULL PRIMARY KEY
 AUTOINCREMENT);
 CREATE TABLE "testing_test2_m2m" ("id" integer NOT NULL PRIMARY KEY
 AUTOINCREMENT, "test2_id" integer NOT NULL REFERENCES "testing_test2"
 ("id"), "test1_id" integer NOT NULL REFERENCES "testing_test1" ("id"),
 UNIQUE ("test2_id", "test1_id"));
 CREATE TABLE "testing_m2m" ("id" integer NOT NULL PRIMARY KEY
 AUTOINCREMENT, "test1_id" integer NOT NULL REFERENCES "testing_test1"
 ("id"), "test2_id" integer NOT NULL REFERENCES "testing_test2" ("id"));
 }}}
 The issue here is that there is a table named "testing_test2_m2m" which
 shouldn't be there!

 Attached you will find a full project demonstrating this 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/051.1466571e70d29847b4ba94746bee60a2%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19508: Implement URL decoding according to RFC 3987

2014-03-02 Thread Django 
#19508: Implement URL decoding according to RFC 3987
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  HTTP handling |  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
--+
Changes (by anubhav9042):

 * cc: anubhav9042@… (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/067.5c2b58cad80da26ce786238c81e96416%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18381: Underscore in CharField primary key breaks the admin "view on site" link

2014-03-02 Thread Django 
#18381: Underscore in CharField primary key breaks the admin "view on site" link
-+-
 Reporter:  dappawit |Owner:  apollo13
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  0|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by mattias):

 * version:  1.4 => 1.6


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

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

Re: [Django] #18381: Underscore in CharField primary key breaks the admin "view on site" link

2014-03-02 Thread Django 
#18381: Underscore in CharField primary key breaks the admin "view on site" link
-+-
 Reporter:  dappawit |Owner:  apollo13
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  0|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by mattias):

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


Comment:

 Although this bug was closed fixed 2 years ago, related issues seem still
 present in the latest stable Django release 1.6.2.

 CharField primary keys with underscores are (un)escaped differently in the
 admin pages, and when reversing admin URLs with
 django.core.urlresolvers.reverse() or the {% url %} template tag.
 The admin pages add "5F" after the underscore in when rendering URLs, but
 reverse() does not. As a result, links from custom pages into the admin
 break when the object's primary key contains underscores.

 Steps to reproduce:
 * Create a model with "id = models.CharField(max_length=100,
 primary_key=True)" or other similar text primary key field,
 * Register the model to the admin site,
 * Create a model instance with test_123 as the primary key,
 * Visit the admin, and observe admin URLs: they are of the format
 "/admin///test_5F123/"
 * Open the shell, and call reverse('admin:app_model_delete',
 args=!['test_123'])
 * The URLs returned are of the format "/admin///test_123/" -
 no 5F
 * As a result, if these links are embedded in pages, they don't work - the
 admin page tries to decode the primary key, expects 5F, and does not find
 the object.

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

Re: [Django] #19508: Implement URL decoding according to RFC 3987

2014-03-02 Thread Django 
#19508: Implement URL decoding according to RFC 3987
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  HTTP handling |  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 anubhav9042):

 I am thinking to work on this.
 I have some idea of what to do, by visiting the links provided in the
 summary.

 Can anyone give me some ideas to begin with...??

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

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

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

 * owner:  nate_b => smeatonj
 * 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/065.4d715509a59900dc19c6315e3d3ac047%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22130: Accelerated deprecation fix_ampersands and clean_html

2014-03-02 Thread Django 
#22130: Accelerated deprecation fix_ampersands and clean_html
-+-
 Reporter:  erikr|Owner:  aaugustin
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Utilities|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  nlsprint14   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * status:  new => assigned
 * owner:  erikr => aaugustin


Comment:

 I'll try to figure out if I can stop template_tests from leaking warning
 state first.

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

Re: [Django] #21680: Stop supporting models in non-installed apps

2014-03-02 Thread Django 
#21680: Stop supporting models in non-installed apps
--+
 Reporter:  aaugustin |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  app-loading 1.9   | 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):

 #22182 was a duplicate (with a long explanation).

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

Re: [Django] #22182: Reverse accessor should not be added for models with `ForeignKey` fields belonging to apps not installed.

2014-03-02 Thread Django 
#22182: Reverse accessor should not be added for models with `ForeignKey` fields
belonging to apps not installed.
-+-
 Reporter:  mrmachine|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:  OperationalError no  |  Unreviewed
  such table |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 There's already a ticket for option (b): #21680.

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

Re: [Django] #22130: Accelerated deprecation fix_ampersands and clean_html

2014-03-02 Thread Django 
#22130: Accelerated deprecation fix_ampersands and clean_html
--+
 Reporter:  erikr |Owner:  erikr
 Type:  Cleanup/optimization  |   Status:  new
Component:  Utilities |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  nlsprint14| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by erikr):

 * has_patch:  0 => 1


Comment:

 Sorry about that - this is the same issue I asked about on the mailing
 list: it turns out the warnings filters across multiple tests interact.
 `template_tests` sets an ignore for these DeprecationWarnings, which means
 `defaultfilters` does not see them anymore, even though it sets filters
 back to `default`. Even an explicit call to `warnings.resetwarnings()` did
 not change this. I fixed this for `utils_tests` by removing that specific
 check, hadn't realised it was an issue here too as the order for my
 locally run tests was different.

 As Aymeric told me it was not really necessary to test for the warning
 actually being issued, the quick fix is:
 https://github.com/django/django/pull/2383

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