date:20140307

Re: [Django] #22006: DRY login_required method should be documented

2014-03-07 Thread Django

#22006: DRY login_required method should be documented
-+-
 Reporter:  django@… |Owner:
 Type:   |  mockforest
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  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:  1|UI/UX:  0
-+-
Changes (by mockforest):

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

Re: [Django] #22006: DRY login_required method should be documented

2014-03-07 Thread Django

Comment (by mockforest):

I didn't see the first line of @dzhibas's comment, sorry. Patch fixed.

And now I'm not so sure about the suggestions I feel like the example
belongs to three separate sections:

* Using mixins (https://docs.djangoproject.com/en/dev/topics/class-based-
views/intro/#using-mixins),
* Decorating class-based views
(https://docs.djangoproject.com/en/dev/topics/class-based-views/intro
/#decorating-class-based-views), and
* Applying permissions to generic views
(https://docs.djangoproject.com/en/dev/topics/auth/default/#applying-
permissions-to-generic-views).

What would be the best way to do 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/078.e0eb19b4b4018558b386bdf950d4a028%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22230: muscle care

2014-03-07 Thread Django

#22230: muscle care
---+---
 Reporter:  anonymous  |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:  Nitric Max Muscle
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+---
 home a half possibility death but the only man or an ass munch KK dull
 same hey this No come some climate shit slipping glass like this favorite
 touches a good carpet the UK on a slide good decided to spelling slow them
 blue lowing there good well good the good this the became a class right
 mom come the donors with me stick to our good just keep look at the this
 on I I'm now this may I there holes curls way good Google has like just
 good at yeah a pushing small affair you want to good go good he good bills
 good yes huh that to Smith plastic school supposed to help slide go good
 this that that year good height there's your good this hole my but you
 know to its leg in your eyes okhepburn's but I so Alistair well good job
 guys he did that work out you should be feel and you have like no yelling
 no strength left you can [http://nitricmaxmusclereal.com/ Nitric Max
 Muscle] calling thing are pushing thing good everything from your biceps
 your triceps and all we're pushing pulling power is professionally
 exhausted plus it's an awesome workout for fat burning endurance work on
 your cardio so hope you like that work out a whole I just gravy my arm up
 it's like are still get 100 so their young guys I have to get up there
 mama even if you just start a workout doesn’t mean you have to do some
 dens workout do the top of the hill effective one just work now is about
 working not about you know just thought that emotion you have not like
 aerobic class you know I mean got to push hard getaway to be on this work
 I guess when man get do it right efforts so hard so very good guys you are
 more workouts that great getters even so he did not get her even here if
 you even hear van flipped their even more capital of you like to see me do
 these workouts and helicopter cell even so to get these work at the very
 effective sup met the beginner or advanced doesn't matter this workout
 kick your butt annual work build muscle and burn fat to get more workouts
 over here right more homework out more get a workout have you got a muscle
 shirt that bad and if you want to learn the fastest way to really build
 muscle and saline at six pack abs year-round to get think that started on
 homework in click the link about right hand corner thanks for watching
 guys and cherry hard see guys like that this ogle got a question from our
 phone calls himself Mizumoto says dear earlier given especial muscle
 building tips for men over 40 summon spirits may have had with your
 clients well so you up yeah I have lots of experience with clients that
 are in there 50s I'll an older and I'm just beginning to experience that
 myself be 35 this year and I never thought I’d say but I'm feeling the
 effects of H its it's inevitable I know are you guys watching videos years
 your 1716 fourteen-years-old it's like I'll never fucking get old well I
 thought the same way for a very long time and of course youth is a state
 of mind but your mind is a byproduct of your but your mind your body is
 one so is your body becomes H he did as a is hi I'm withers the strength
 of your physiology your muscular skeletal system also your mind tends to
 change and then it's you know of course is the chair Inez is it because
 the stories I tell myself%uh age was because my body is actually getting
 older so we go first the situation of getting older and athleticism to
 from a two-pronged approach the very first is of course energetic your
 mind what do you liquor store you tell yourself and most resourceful
 stories that I’ve begun to tell myself an iced CV aldermen that I’ve trait
 tell themselves is that I'm not necessarily getting older and that means I
 lacked vitality what’s happening is I'm becoming more sensitive and my
 body requires that much more attention to detail this is what begins
 happening when you're young beat the fuck out yourself eat whatever you
 want to eat you can be nasty to stay up all night ocean I remember this in
 college I was a tremendous athlete I played football and I was always very
 good not to my own horn but OK enough Saturday night's stay out too 34
 o'clock in the morning go to the diner is in new York city you know likes
 it doesn't close so we go to diners retired as we I water this platter
 with two cheeseburgers a double cheeseburger platter and we get a are both
 great my boys in the middle and we wouldn't do the cheeseburgers in gravy
 in mind you were hammered because we spend all night drinking at bars
 event Sunday more Sunday I we def football practice and

[django/django] 70ec4d: Fixed #22034 -- Added a specific set of relation c...

2014-03-07 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 70ec4d776ef0e68960ccee21476b8654e9399f53
  
https://github.com/django/django/commit/70ec4d776ef0e68960ccee21476b8654e9399f53
  Author: Russell Keith-Magee 
  Date:   2014-03-08 (Sat, 08 Mar 2014)

  Changed paths:
M django/contrib/admin/checks.py
M django/contrib/contenttypes/admin.py
M docs/ref/checks.txt
M tests/admin_checks/models.py
M tests/admin_checks/tests.py

  Log Message:
  ---
  Fixed #22034 -- Added a specific set of relation checks for 
GenericInlineModelAdmin.

Thanks to jwa for the report.


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

Re: [Django] #22034: Checks for ModelAdmin ForeignKeys fail with GenericInlineModelAdmin

2014-03-07 Thread Django

#22034: Checks for ModelAdmin ForeignKeys fail with GenericInlineModelAdmin
-+
 Reporter:  jwa  |Owner:  josven
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  checks   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Russell Keith-Magee ):

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


Comment:

 In [changeset:"70ec4d776ef0e68960ccee21476b8654e9399f53"]:
 {{{
 #!CommitTicketReference repository=""
 revision="70ec4d776ef0e68960ccee21476b8654e9399f53"
 Fixed #22034 -- Added a specific set of relation checks for
 GenericInlineModelAdmin.

 Thanks to jwa for the report.
 }}}

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

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

Re: [Django] #22034: Checks for ModelAdmin ForeignKeys fail with GenericInlineModelAdmin

2014-03-07 Thread Django

#22034: Checks for ModelAdmin ForeignKeys fail with GenericInlineModelAdmin
-+
 Reporter:  jwa  |Owner:  josven
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  checks   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by russellm):

 The problem here is that GenericInlineModelAdmin is using the base
 InlineModelAdmin checks. We just need to make GenericInlineModelAdmin run
 it's own, generic-specific checks of the relation to the parent.

 I'm working on a patch, incoming shortly.

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

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

Re: [Django] #21721: Python 3.4 support

2014-03-07 Thread Django

#21721: Python 3.4 support
-+
 Reporter:  mjtamlyn |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Python 3 |  Version:  master
 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 berkerpeksag):

 * cc: berker.peksag@… (added)


Comment:

 > django.utils.module_loading. module_has_submodule has some issues with
 eggs. sys.meta_path is giving us importlib as a finder.
 importlib.find_module is deferred to importlib.find_spec (new in py3.4),
 which throws an error (ImportError: spec missing loader).

 I didn't get any test failures with the current default branch of CPython
 3.4. Probably related to http://bugs.python.org/issue20763.

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

Re: [Django] #17816: UnicodeEncodeError in Image- and FileFields

2014-03-07 Thread Django

Comment (by clime7@…):

I have encountered a similar problem and I'd like to add some info for
this. Two things can cause unicode errors like this:

1) non-utf8 encoding returned by sys.getdefaultencoding() causes unicode
errors in cases like: str(unicode_string_with_accents), i.e. whenever
there is a conversion from unicode string to byte string without
explicitly specifying encoding like this:
str(unicode_string_with_accents.encode('utf-8')). However, ascii is
default for python 2 and it shouldn't be fiddled with so this is an
expected problem.

2) non-utf8 encoding returned by sys.getfilesystemencoding(). This should
on the other hand really return an utf-8 encoding because otherwise you
get unicode errors in cases like os.stat(unicode_string_with_accents). os
module looks at filesystem encoding when trying to interpret unicode
strings. And on linux file system encoding is inferred from locale of
python interpretter. Specifically there should be LANG=something.utf8 in
the environment.

I have resolved my problem by adding "env = LANG=en_US.utf8" to my
uwsgi.ini. I believe other people with this problem might need to do
something similar.

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

Re: [Django] #9721: DateTimeField does not support all DEFAULT_DATETIME_INPUT_FORMATS when passed a list as input

2014-03-07 Thread Django

#9721: DateTimeField does not support all DEFAULT_DATETIME_INPUT_FORMATS when
passed a list as input
-+-
 Reporter:  uggedal  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  DateTimeFIeld| Triage Stage:  Accepted
  SplitDateTimeWidget|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

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


Comment:

 We've deprecated usage of `SplitDateTimeWidget` with `DateTimeField` in
 0179852d7faf461d55cf3ae69393abb3f3cd2910.

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

Re: [Django] #13339: Date(Time)Field.to_python() fails to parse localized month names

2014-03-07 Thread Django

#13339: Date(Time)Field.to_python() fails to parse localized month names
---+-
 Reporter:  UloPe  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Forms  |  Version:  1.1
 Severity:  Normal |   Resolution:
 Keywords:  i18n l10n  | Triage Stage:  Someday/Maybe
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by claudep):

 * stage:  Accepted => Someday/Maybe


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

Re: [Django] #22224: Non-nullable blank string-based model field validation doesn't prevent or clean `None`

2014-03-07 Thread Django

#4: Non-nullable blank string-based model field validation doesn't prevent 
or
clean `None`
-+-
 Reporter:  charettes|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by charettes):

 As pointed out by Loïc this issue is related to #20205 which propose to
 clean `''` to `None` for fields disallowing empty strings.

 Maybe the correct solution here would be to clean `None` to `''` for non-
 null fields allowing empty strings?

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

Re: [Django] #17922: Add default "required" css classes to form labels

2014-03-07 Thread Django

#17922: Add default "required" css classes to form labels
-+---
 Reporter:  hanson2010   |Owner:  anubhav9042
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  sprint2013   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+---

Comment (by claudep):

 Florian, would adding the `required` attribute on the widget help styling
 the label (common use case) ? Of course, adding the HTML5 `required`
 attribute is a very good idea, but I'm not sure it solves 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/068.813a6a0abf7821201803ffa049e7368c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21179: How-to output CSV from Django should suggest using `StreamingHttpResponse`

2014-03-07 Thread Django

#21179: How-to output CSV from Django should suggest using 
`StreamingHttpResponse`
--+
 Reporter:  charettes |Owner:  zr
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timo):

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

Re: [Django] #13637: Generic Relations don't work correctly on a non-default database alias

2014-03-07 Thread Django

#13637: Generic Relations don't work correctly on a non-default database alias
--+
 Reporter:  andrewgodwin  |Owner:
 Type:  Bug   |   Status:  new
Component:  contrib.contenttypes  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  multi-db, truncation  | 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:  andrewgodwin =>
 * status:  assigned => new


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

Re: [Django] #13528: db_table truncation is applied based on the properties of the default database

2014-03-07 Thread Django

#13528: db_table truncation is applied based on the properties of the default
database
-+-
 Reporter:  russellm |Owner:
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.2-beta
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by andrewgodwin):

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


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

Re: [Django] #21843: Schema migration test_operations explicitly set an identity column with raw sql

2014-03-07 Thread Django

#21843: Schema migration test_operations explicitly set an identity column with 
raw
sql
-+-
 Reporter:  manfre   |Owner:
 Type:  Bug  |  andrewgodwin
Component:  Testing framework|   Status:  assigned
 Severity:  Release blocker  |  Version:  master
 Keywords:  schema migrations|   Resolution:
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by andrewgodwin):

 * owner:  nobody => andrewgodwin
 * 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/064.31d8897f0aa35a6e8b46cda56c05cbe9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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

2014-03-07 Thread Django

#22051: Running `makemigrations` twice in a row fails
-+
 Reporter:  bmispelon|Owner:  andrewgodwin
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  master
 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):

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


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

Re: [Django] #22199: Incorrect handling of max_length in FileField.deconstruct

2014-03-07 Thread Django

#22199: Incorrect handling of max_length in FileField.deconstruct
-+-
 Reporter:  julianbrost  |Owner:
 Type:  Bug  |  andrewgodwin
Component:  Migrations   |   Status:  assigned
 Severity:  Release blocker  |  Version:  master
 Keywords:  FileField,   |   Resolution:
  ImageField, max_length | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by andrewgodwin):

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


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

Re: [Django] #21860: ModelChoiceField documentation doesn't include the `to_field_name` optional argument

2014-03-07 Thread Django

#21860: ModelChoiceField documentation doesn't include the `to_field_name` 
optional
argument
-+-
 Reporter:  Keryn Knight |Owner:
   |  anubhav9042
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   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 timo):

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

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

2014-03-07 Thread Django

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

 * owner:   => andrewgodwin
 * 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/062.cbc53555f90b009f998352988e35776f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22073: Backwards migration on ManyToMany field does not remove intermediary table

2014-03-07 Thread Django

#22073: Backwards migration on ManyToMany field does not remove intermediary 
table
-+
 Reporter:  bendavis78   |Owner:  andrewgodwin
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by andrewgodwin):

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


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

Re: [Django] #22224: Non-nullable blank string-based model field validation doesn't prevent or clean `None`

2014-03-07 Thread Django

#4: Non-nullable blank string-based model field validation doesn't prevent 
or
clean `None`
-+-
 Reporter:  charettes|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

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

[Django] #22229: Invalid data can cause InlineFormSet.is_valid to throw ValueError

2014-03-07 Thread Django

#9: Invalid data can cause InlineFormSet.is_valid to throw ValueError
+---
 Reporter:  anonymous   |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Forms   |Version:  1.6
 Severity:  Normal  |   Keywords:  InlineFormSet
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+---
 The InlineFormSet's foreign key field ("") seems to assume that its data is valid for all of the initial data.
 Thus, if it is altered, the database layer will fail to convert it and
 throw an exception, instead of reporting that the form is invalid. For an
 integer foreign key, this takes form of a ValueError thrown by the int
 function.

 I've created a test demonstrating the issue here:
 https://gist.github.com/ColonelThirtyTwo/edbc575b10b068397dc7

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

Re: [Django] #20935: ePub documentation not valid

2014-03-07 Thread Django

#20935: ePub documentation not valid
---+
 Reporter:  mabdullah  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  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 afuna):

 There are 3000+ validation warnings/errors generated by epubcheck. The
 good news is that these fall into only a dozen or so categories:

  1)1 times   ERROR: value of attribute "href" is invalid; must be a
 URI
  2)1 times   ERROR: attribute "id" not allowed here; expected
 attribute "charset", "defer", "src" or "xml:space"
  3)2 times   ERROR: element "form" not allowed anywhere; expected the
 element end-tag, text or element "a", "abbr", "acronym", "address",
 "applet", "b", "bdo", "big", "blockquote", "br", "cite", "code", "del",
 "dfn", "div", "dl", "em", "h1", "h2", "h3", "h4", "h5", "h6", "hr", "i",
 "iframe", "img", "ins", "kbd", "map", "noscript", "ns:svg", "object",
 "ol", "p", "pre", "q", "samp", "script", "small", "span", "strong", "sub",
 "sup", "table", "tt", "ul" or "var" (with
 xmlns:ns="http://www.w3.org/2000/svg";)
  4)2 times   ERROR: attribute "start" not allowed here; expected
 attribute "dir", "id", "lang", "style", "title" or "xml:lang"
  5)3 times   ERROR: hyperlink to non-standard resource <...> of type
 <...>
  6)3 times   ERROR: element "dc:date" not allowed anywhere; expected
 the element end-tag or text
  7)7 times   ERROR: <...>: referenced resource missing in the package.
  8)  678 times   ERROR: value of attribute "id" is invalid; must be an XML
 name without colons
  9) 2400 times   ERROR: <...>: fragment identifier is not defined in <...>
  10)5 times   HINT: Link attribute with no value
  11)1 times   WARNING: use of non-registered URI scheme type in href:
 irc://irc.freenode.net/django-dev
  12)4 times   WARNING: hyperlink to resource outside spine <...>
  13)8 times   WARNING: use of non-registered URI scheme type in href:
 irc://irc.freenode.net/django
  
  3115 total

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

[Django] #22228: health acre tipa 50000

2014-03-07 Thread Django

#8: health acre tipa 5
---+---
Reporter: anonymous | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized |Version: 1.6
Severity: Normal | Keywords: AKTIVE AM
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
---+---
What's the Island Fiend MMA & enclosure condition conditioning tactic*? So
here's the lie...
The fattest guy I knew came to our soundness sport gym (after going absent
for a gathering) with a rock-hard embody and chiseled six-pack abs...
To acquire his tricks & tips, we hurried at him for an converse like he
was a renown. His appellative at the enclosing soundness lodge is now the
borneo demon because he was so stoutness and now he's an MMA & sport
foetus with an awing body.
[http://aktiveamskincarereview.com/ AKTIVE AM]

So how did the island demon retrograde so untold weight so speeding and
literally cozen his embody? It's because he scholarly the undercover
soundness techniques of professed MMA & envelopment fighters...
Here, I'll let him justify:
"hey guys and gals, to recede weight and/or get super ripped without
having to locomote to tactics that could put you in danger retributive
simply analyze the pros!
I suffered from eudaimonia problems because of my unfruitful shape...So
things had to travel for me quick.
Because of this, I had to find the surreptitious condition tricks of pro
MMA & envelopment fitness trainers...because I pair these guys and gals
get results immobile.
Getting in communication with an real jock MMA & pugilism soundness
trainer, I deciphened the secrets integrated poet artists & boxers use to
get their physiques...And winged! These 5 secrets are plain golden...
1. It's all virtually main workouts that aren't irksome. If you fuck a
deadening workout, you'll create up. We impoverishment arousal, we're not
machines.
2. Also, you require an raging workout that you can do at bag or at the
gym. A elastic workout. Sometimes I would virtuous get up off my computer
and move doing them...In the shelter.
3. It's spatulate to educate that physique you hump always unreal... A
insufficient and toned body that looks redress. All you gotta do is
develop effectively similar MMA & envelopment athletes. Whether you're a
man or oriental - 3 days a hebdomad for 1 minute. Not bad at all...
4. The pro jock undercover for whole embody results - that is - losing
coefficient, exploit ripped, and augmentative your capability is to do
exercises that get your body afoot in a kinetic concatenation. That's why
inclosure suitableness is awful! AKTIVE AM

5. Feature a oblong nutrition thought to ensure that your embody is
getting move alter time you're not working out...A group that works on
purified device.
Plus, if you hold sexy workouts you'll actually aspect progressive to
doing them. So that's the genuine illusion. MMA & inclosure suitability
exercises are major because you'll person a lot of fun and you'll be
learning true skills.
Hence, after my investigate I realized that MMA & enclosing workouts were
1 for fitness and losing unit. Diets uptake! Cartel me, I've proven em
all!
A eager workout that authority fighters use is the 1-arm tripod row:
Involve a dumbell in one crewman. Put your liberal arm out and acquire
something to flex that up against so your body, arm, and reach represent a
trilateral. Deplume the coefficient up to your lats. Here, you're forced
to use your actuation muscles and ngo magnitude.
Try doing 1 set of 50, then mix it up. The succeeding week do 4 sets of
15. Then get hindmost to 3 sets of 10 with many weight.
Equal a big ogre similar me can get the suitability results we've all been
want for... Losing coefficient and effort toned in lightening hurried
dimension...Without taking b.s. supplements."
So there you jazz it. The borneo foetus speaks.
http://aktiveamskincarereview.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.6010814115716f94123d0ab15afdee20%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17922: Add default "required" css classes to form labels

2014-03-07 Thread Django

#17922: Add default "required" css classes to form labels
-+---
 Reporter:  hanson2010   |Owner:  anubhav9042
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  sprint2013   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+---

Comment (by apollo13):

 I think we should use the "required" attribute from HTML5 and don't set
 any css class.

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

Re: [Django] #22124: Expand the Documentation of Custom Lookups for V1.7

2014-03-07 Thread Django

#22124: Expand the Documentation of Custom Lookups for V1.7
--+
 Reporter:  mzaanen   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   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 Marc Tamlyn ):

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


Comment:

 In [changeset:"219d928852c256a81d09dbaa29ed4cec42d2fdfa"]:
 {{{
 #!CommitTicketReference repository=""
 revision="219d928852c256a81d09dbaa29ed4cec42d2fdfa"
 Fixed #21863 -- supplemented get_lookup() with get_transform()

 Also fixed #22124 -- Expanded explanation of exactly what is going on in
 as_sql() methods.
 }}}

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

[django/django] 219d92: Fixed #21863 -- supplemented get_lookup() with get...

2014-03-07 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 219d928852c256a81d09dbaa29ed4cec42d2fdfa
  
https://github.com/django/django/commit/219d928852c256a81d09dbaa29ed4cec42d2fdfa
  Author: Anssi Kääriäinen 
  Date:   2014-03-07 (Fri, 07 Mar 2014)

  Changed paths:
M django/db/models/lookups.py
M django/db/models/sql/datastructures.py
M django/db/models/sql/query.py
M docs/ref/models/custom-lookups.txt
M tests/custom_lookups/tests.py
M tests/lookup/tests.py

  Log Message:
  ---
  Fixed #21863 -- supplemented get_lookup() with get_transform()

Also fixed #22124 -- Expanded explanation of exactly what is going on in
as_sql() methods.


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

Re: [Django] #21863: Consider adding get_transform() to supplement get_lookup()

2014-03-07 Thread Django

#21863: Consider adding get_transform() to supplement get_lookup()
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |  1.7-alpha-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Marc Tamlyn ):

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


Comment:

 In [changeset:"219d928852c256a81d09dbaa29ed4cec42d2fdfa"]:
 {{{
 #!CommitTicketReference repository=""
 revision="219d928852c256a81d09dbaa29ed4cec42d2fdfa"
 Fixed #21863 -- supplemented get_lookup() with get_transform()

 Also fixed #22124 -- Expanded explanation of exactly what is going on in
 as_sql() methods.
 }}}

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

Re: [Django] #22227: save_model in ModelAdmin with "formsets" parameter

2014-03-07 Thread Django

#7: save_model in ModelAdmin with "formsets" parameter
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  contrib.admin|   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 brunato):

 * cc: brunato (added)
 * needs_better_patch:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * needs_tests:   => 0
 * needs_docs:   => 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/067.281622a32461f8e455a5aefc4937cf09%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22141: Add spell checker for documentation

2014-03-07 Thread Django

#22141: Add spell checker for documentation
--+
 Reporter:  beregond  |Owner:  timo
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"a0f252520291924f8fb7cb0d85f1680294508560"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a0f252520291924f8fb7cb0d85f1680294508560"
 Fixed #22141 -- Added a spelling checker for documentation.
 }}}

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

[django/django] a0f252: Fixed #22141 -- Added a spelling checker for docum...

2014-03-07 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a0f252520291924f8fb7cb0d85f1680294508560
  
https://github.com/django/django/commit/a0f252520291924f8fb7cb0d85f1680294508560
  Author: Szczepan Cieślik 
  Date:   2014-03-07 (Fri, 07 Mar 2014)

  Changed paths:
M docs/Makefile
M docs/conf.py
M docs/internals/contributing/writing-documentation.txt
A docs/spelling_wordlist

  Log Message:
  ---
  Fixed #22141 -- Added a spelling checker for 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/5319d7deb746e_3dfb9c3d44560f9%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 8f9c3d: Fixed typo in docs/ref/checks.txt

2014-03-07 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8f9c3d05650cd418c57f2ded49ed1acbb5c05e77
  
https://github.com/django/django/commit/8f9c3d05650cd418c57f2ded49ed1acbb5c05e77
  Author: Tim Graham 
  Date:   2014-03-07 (Fri, 07 Mar 2014)

  Changed paths:
M docs/ref/checks.txt

  Log Message:
  ---
  Fixed typo in docs/ref/checks.txt


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

[Django] #22227: save_model in ModelAdmin with "formsets" parameter

2014-03-07 Thread Django

#7: save_model in ModelAdmin with "formsets" parameter
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  contrib.admin  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Can be useful to add a "formsets" parameter in the definition of the
 method ModelAdmin.save_model, passing it as argument in the save_model
 calls of add_view and change_view? This new parameter, that can be
 defaulted to "None" for backward compatibility, could be useful for model
 admin's customization when a calculated field depends from one or more
 formsets.

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

Re: [Django] #22158: Allow model level custom lookups

2014-03-07 Thread Django

#22158: Allow model level custom lookups
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by mjtamlyn):

 * stage:  Unreviewed => Accepted


Comment:

 It should definitely be able to handle Q objects as well as SQL as this is
 the 90% use case I think. Really nice feature idea though!

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

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

Re: [Django] #21963: makemessages still ignores translations in templates with inline comment tags

2014-03-07 Thread Django

#21963: makemessages still ignores translations in templates with inline comment
tags
-+-
 Reporter:  Ihor Kaharlichenko   |Owner:  dzhibas
|   Status:  assigned
 Type:  Bug  |  Version:  1.6
Component:   |   Resolution:
  Internationalization   | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  makemessages,|  Patch needs improvement:  0
  template, gettext, xgettext|UI/UX:  0
Has patch:  0|
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by dzhibas):

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


Comment:

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

 please review.

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

Re: [Django] #22217: ManyToManyField.through_fields docs mix up description of arguments

2014-03-07 Thread Django

#22217: ManyToManyField.through_fields docs mix up description of arguments
-+--
 Reporter:  dfunckt  |Owner:  dfunckt
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  master
 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
-+--

Comment (by dfunckt):

 Updated the pull request. This patch improves on many areas:

 - Fixes the docs for `through_fields`.
 - Moves validation earlier, in the check() method, as suggested by loic84.
 - Rewords some validation error messages and provides hints for some of
 them.

 All tests pass.

 I've squashed commits to a larger one, let me know if i should create
 separate tickets and/or commits for each issue 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/065.6ee5d5bd5c53d2db4d4323e3b20794cf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #8809: Better error message when can't import url callback

2014-03-07 Thread Django

#8809: Better error message when can't import url callback
---+
 Reporter:  TP |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Core (URLs)|  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  error message  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by anubhav9042):

 Replying to [comment:18 aaugustin]:
 > I'm not convinced that code addresses the request in this ticket. Can
 you at least check that the code is more recent than the latest
 discussions here?
 The issue was to change the message such that we could know which line has
 problem(if there are several url files, it will be difficult.)

 I think when we are specifying which particular {{{view}}} does not exists
 in which {{{module}}}, the user now knows what is missing and where, which
 wasn't there before. I think that very much solves this issue.
 So I closed the ticket.
 Am I wrong??

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

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

[Django] #22226: Reversing admin URLs requires undocumented filter admin_urlquote.

2014-03-07 Thread Django

#6: Reversing admin URLs requires undocumented filter admin_urlquote.
---+
 Reporter:  mattias|  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I have a model with a text primary key:
 {{{
 class CharKey(models.Model):
 id = models.CharField(max_length=20, primary_key=True)
 }}}

 Reversing admin URLs as described in
 https://docs.djangoproject.com/en/dev/ref/contrib/admin/#reversing-admin-
 urls //sometimes// breaks depending on the characters in the key.

 The admin pages call django.contrib.admin.utils.unquote() on the primary
 key received in the URL. Internally, admin templates escape the object
 URLs with for example
 {{{
 {% url opts|admin_urlname:'change' original.pk|admin_urlquote %}
 }}}
 The links obtained from the basic reverse(), as used in the documentation,
 do not work:
 {{{
 reverse('admin:key_charkey_change', args=(c.id,))
 }}}
 as they fail to quote special charcters like the underscore "_". Instead,
 the page linking to the admin has to use
 django.contrib.admin.utils.quote() on the argument to reverse(), or the
 corresponding template filter in a template.

 The issue is surprisingly confusing because it seems that browsers like
 Chrome auto-escape //most//, but not all special characters in a format
 accepted and decoded by unquote(): for example, characters like $%!^&*()
 work just fine without quote() in the code, but for example the underscore
 does not.  As a result the admin URLs without quoting work fine even with
 funny characters in the primary key, unless one of the few exceptional
 characters are used.

 As a workaround, documenting the mandatory use of admin_urlquote template
 filter and updating the examples might be enough.
 However, I wonder if there are more general fixes to reverse() possible?
 This seems like an issue that would come up in custom, non-admin URLs as
 well.

 I originally reported this in the comments of
 https://code.djangoproject.com/ticket/18381, but created a separate issue
 as requested. The behaviour of this ticket is present in the current
 django 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/050.c73fd2fef31fd178d3d971bc20cfe808%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22225: BoundField.as_hidden() is not documented

2014-03-07 Thread Django

#5: BoundField.as_hidden() is not documented
---+--
 Reporter:  anton  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:  duplicate
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by bmispelon):

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


Comment:

 Hi,

 There is an old ticket to add documentation for the attributes and methods
 of `BoundField`: #12856.

 I'll mark this as a duplicate.

 Thanks.

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

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

[Django] #22225: BoundField.as_hidden() is not documented

2014-03-07 Thread Django

#5: BoundField.as_hidden() is not documented
---+
 Reporter:  anton  |  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
---+
 I just found out that this functionality exists
 bacause I had a look at the
 {{{django/contrib/formtools/preview.html}}}
 template file.

 Since this is a useful / needed functionality for creating
 your own preview forms I think it should be documented.

 '''or is this feature deprecated???'''

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

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

Re: [Django] #18731: "makemessages" management command should handle import aliases

2014-03-07 Thread Django

#18731: "makemessages" management command should handle import aliases
-+-
 Reporter:  diabeteman   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:   |   Resolution:
  Internationalization   | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  1
 Keywords:  makemessages i18n|  Patch needs improvement:  1
  gettext|UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by claudep):

 * component:  Core (Management commands) => Internationalization
 * needs_better_patch:  0 => 1
 * version:  1.4 => master
 * type:  New feature => Cleanup/optimization
 * needs_docs:  0 => 1


Comment:

 In my recent commit in `makemessages`
 ([06efeae598c6dafbe56d2ea323a0dccdd5bf2b8e]), I added an options list for
 various gettext commands at the `Command` level.

 Therefore, the new way to solve this issue is to create a custom
 `makemessages` command in one of your project's apps, and complete the
 `Command.xgettext_options` list. I'm keeping this ticket open so as to add
 an example in the documentation.

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

Re: [Django] #22070: Admin index shows mixed lowercase and capitalized app names when using contrib apps and old-style apps

2014-03-07 Thread Django

#22070: Admin index shows mixed lowercase and capitalized app names when using
contrib apps and old-style apps
---+--
 Reporter:  bendavis78 |Owner:  jenkinsbr2
 Type:  Bug|   Status:  new
Component:  Core (Other)   |  Version:  master
 Severity:  Release blocker|   Resolution:
 Keywords:  admin app-loading  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by aaugustin):

 * status:  closed => new
 * component:  contrib.admin => Core (Other)
 * resolution:  fixed =>
 * type:  Cleanup/optimization => Bug
 * severity:  Normal => Release blocker


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

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

Re: [Django] #22070: Admin index shows mixed lowercase and capitalized app names when using contrib apps and old-style apps

2014-03-07 Thread Django

#22070: Admin index shows mixed lowercase and capitalized app names when using
contrib apps and old-style apps
-+-
 Reporter:  bendavis78   |Owner:
 Type:   |  jenkinsbr2
  Cleanup/optimization   |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  admin app-loading| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by aaugustin):

 I disagree with that commit and I think it must be reverted.

 Application names must be lower case for the same reason model names are
 lower case.

 If templates need an title-cased version, they can title-ize or capitalize
 the value.

 I've been working on a patch since last week-end and I hope to complete it
 this week-end.

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

Re: [Django] #18731: "makemessages" management command should handle import aliases

2014-03-07 Thread Django

#18731: "makemessages" management command should handle import aliases
-+-
 Reporter:  diabeteman   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  1.4
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  makemessages i18n|  Needs documentation:  0
  gettext|  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by diabeteman):

 oops sorry :-/

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

Re: [Django] #22217: ManyToManyField.through_fields docs mix up description of arguments

2014-03-07 Thread Django

#22217: ManyToManyField.through_fields docs mix up description of arguments
-+--
 Reporter:  dfunckt  |Owner:  dfunckt
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  master
 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
-+--

Comment (by dfunckt):

 System checks I believe are performed too early -- the relation has not
 been setup at this point -- though it would be great if I'm mistaken, as I
 also prefer for it to be a check.

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

Re: [Django] #22224: Non-nullable blank string-based model field validation doesn't prevent or clean `None`

2014-03-07 Thread Django

#4: Non-nullable blank string-based model field validation doesn't prevent 
or
clean `None`
-+-
 Reporter:  charettes|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by charettes:

Old description:

> Since
> [https://docs.djangoproject.com/en/dev/ref/models/fields/#django.db.models.Field.null
> we discourage the use of NULLable string-based fields] the assumed way of
> holding text that might be empty would be to use the `blank` option.
>
> In this case I would expect `full_clean` to raise a `ValidationError`
> when an empty non-nullable field is assigned `None`:
>
> {{{#!python
> from django.db import models
>
> class A(models.Model):
> b = models.CharField(blank=True)
>
> a = A(b=None)
> a.full_clean()  # Passes
> a.save()  # Integrity error
> }}}
>
> Unfortunately specifying `blank=True` disable all validation against the
> `b` field, leading to database integrity error upon calling `save()`. The
> obvious solution here would be to override `A.clean` to convert `b` to an
> empty string when it equals `None` but it strikes me as a non trivial
> change for a quite common use case: correctly allowing a string-based
> field to be empty.
>
> This is not an issue when cleaning data retrieved from the usual
> `application/form-url-encoded` `request.GET` or `request.POST` since an
> empty value is always represented by the empty string. However, in the
> case of an `application/json` encoded payload one may either provide
> `None` or `''` (`null` or `''`) to express emptiness. Which will trigger
> the issue described above.
>
> Attaching a patch that special case the `empty_values` of non-nullable
> string based fields based on the `empty_strings_allowed` flag. All tests
> pass on Py7/SQLite3.

New description:

 Since
 
[https://docs.djangoproject.com/en/dev/ref/models/fields/#django.db.models.Field.null
 we discourage the use of NULLable string-based fields] the assumed way of
 holding text that might be empty would be to use the `blank` option.

 In this case I would expect `full_clean` to raise a `ValidationError` when
 an empty non-nullable field is assigned `None`:

 {{{#!python
 from django.db import models

 class A(models.Model):
 b = models.CharField(blank=True)

 a = A(b=None)
 a.full_clean()  # Passes
 a.save()  # Integrity error
 }}}

 Unfortunately specifying `blank=True` disable all validation against the
 `b` field, leading to database integrity error upon calling `save()`. The
 obvious solution here would be to override `A.clean` to convert `b` to an
 empty string when it equals `None` but it strikes me as a non trivial
 change for a quite common use case: correctly allowing a string-based
 field to be empty.

 This is not an issue when cleaning data retrieved from the usual
 `application/form-url-encoded` `request.GET` or `request.POST` since an
 empty value is always represented by the empty string. However, in the
 case of an `application/json` encoded payload one may either provide
 `None` or `''` (`null` or `''`) to express emptiness. Which will trigger
 the issue described above.

 Attaching a patch that special case the `empty_values` of non-nullable
 string based fields based on the `empty_strings_allowed` flag. All tests
 pass on Py2.7/SQLite3.

--

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

47 matches

Mail list logo