Re: [Django] #3871: Use custom managers in reverse relations

[Django]

#3871: Use custom managers in reverse relations
-+-
 Reporter:  EspenG   |Owner:  v1v3kn
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  SVN
  (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 aaugustin):

 As explained in the
 [https://docs.djangoproject.com/en/dev/internals/contributing/triaging-
 tickets/#triage-workflow contributing guide], at this point, this ticket
 needs to be reviewed (by anyone) and marked as ready for checkin.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17258: Move threading.local from DatabaseWrapper to connections dictionary

[Django]

#17258: Move threading.local from DatabaseWrapper to connections dictionary
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  SVN
  (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 akaariai):

 It seems your approach is better. I actually don't know what would be the
 good bits to merge from my 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17396: can't access docs

[Django]

#17396: can't access docs
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.3
 Severity:  Normal |   Resolution:  worksforme
 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 carljm):

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


Comment:

 Docs are working here. Please reopen if you can continue to reproduce this
 failure, and can provide the URL of the page the link is on, and the URL
 of the link that is not working. 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #17396: can't access docs

[Django]

#17396: can't access docs
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.3
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Temporarily down?

 I'm clicking forms on the Table of Contents page and getting a 'page not
 available' response.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17257: Comment that contradicts code in django.contrib.syndication.views

[Django]

#17257: Comment that contradicts code in django.contrib.syndication.views
--+
 Reporter:  aaugustin |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.syndication   |  Version:  SVN
 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 krzysiumed):

 * owner:  krzysiumed =>
 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17220: github repo may be no more available behind https

[Django]

#17220: github repo may be no more available behind https
-+-
 Reporter:  fernando+django@…|Owner:
 Type:   |  krzysiumed
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  github git https | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by krzysiumed):

 * cc: krzysiumed@… (removed)


-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #10880: Link to 1.0 docs has two trailing slashes

[Django]

#10880: Link to 1.0 docs has two trailing slashes
-+-
 Reporter:  guettli  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Djangoproject.com|  Version:  1.0
  Web site   |   Resolution:  fixed
 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 ramiro):

 * status:  reopened => closed
 * ui_ux:   => 0
 * resolution:   => fixed
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17258: Move threading.local from DatabaseWrapper to connections dictionary

[Django]

#17258: Move threading.local from DatabaseWrapper to connections dictionary
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  SVN
  (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 julien):

 akaariai: I hadn't realised you had posted a patch as well. It seems like
 we've both used a similar approach. Let's merge the good bits from both
 patches ;)

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17258: Move threading.local from DatabaseWrapper to connections dictionary

[Django]

#17258: Move threading.local from DatabaseWrapper to connections dictionary
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  SVN
  (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 julien):

 I like this idea. Pysqlite by default prevents connections to be passed
 around between multiple threads, unless you explicitly provide the
 'check_same_thread=False' parameter.

 See how this is implemented:
 
http://www.google.com/codesearch#aEvhAxCkZ8U/src/connection.c=check_same_thread%20package:http://pysqlite%5C.googlecode%5C.com=838
 And where this function is called:
 
http://www.google.com/codesearch#search/=pysqlite_check_thread%20package:http://pysqlite%5C.googlecode%5C.com=cs

 I've implemented something similar in the latest patch. Thoughts?

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #3871: Use custom managers in reverse relations

[Django]

#3871: Use custom managers in reverse relations
-+-
 Reporter:  EspenG   |Owner:  v1v3kn
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  SVN
  (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 sebastian):

 What is the current status on this ticket? The deadline for non-trivial
 new features for 1.4 is the upcoming weekend (Dec 17–18). To me, the
 latest patch in this ticket seems essentially complete – it has
 documentation and tests, plus the actual changes to the code are not
 terribly large nor convoluted.

 What is the next step in getting a developer involved into reviewing this
 and check-in to trunk?

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #3011: Allow for extendable auth_user module

[Django]

#3011: Allow for extendable auth_user module
---+
 Reporter:  nowell strite  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.auth   |  Version:
 Severity:  Normal |   Resolution:
 Keywords:  auth_user  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by gonz):

 * cc: gonz (removed)


-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12737: Thread local settings

[Django]

#12737: Thread local settings
-+-
 Reporter:  Kronuz   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Uncategorized|  Version:  SVN
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Alex):

 ^ that was me.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12737: Thread local settings

[Django]

#12737: Thread local settings
-+-
 Reporter:  Kronuz   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Uncategorized|  Version:  SVN
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by anonymous):

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


Comment:

 The appropriate course of action if you disagree with a ticket that was
 wontfixed by a core developer is to bring it up on the mailing list, not
 to reopen the ticket.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17341: Model.save() commits transactions after every parent class save

[Django]

#17341: Model.save() commits transactions after every parent class save
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (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 sebastian):

 * cc: sebastian.goll@… (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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #9154: Cache compiled templates

[Django]

#9154: Cache compiled templates
-+-
 Reporter:  msaelices|Owner:
 Type:  Uncategorized|   Status:  closed
Component:  Template system  |  Version:  SVN
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  templates, cache | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  1|  Needs documentation:  1
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Kronuz):

 * cc: Kronuz (added)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12737: Thread local settings

[Django]

#12737: Thread local settings
-+-
 Reporter:  Kronuz   |Owner:  nobody
 Type:  Uncategorized|   Status:  reopened
Component:  Uncategorized|  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Kronuz):

 * status:  closed => reopened
 * severity:   => Normal
 * type:   => Uncategorized
 * easy:   => 0
 * ui_ux:   => 0
 * resolution:  wontfix =>


Comment:

 I'm taking the liberty to reopen this ticket again, so we can discuss the
 issue a bit further.

 As an extra point for this, having settings be configurable like this, in
 the way this patch allows, would allow us to call `settings.clear()` just
 before (or after) the request begins (or ends), effectively cleaning up
 all settings the user might have messed with during the request. I'm not
 entirely sure of all the benefits of this, I think there are some, and the
 way settings objects are now, this fits perfectly... otherwise, if
 settings are not to be writeable, we could as well rise an error if the
 user tries to write to the settings 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #6422: Support for 'DISTINCT ON' queries with QuerySet.distinct()

[Django]

#6422: Support for 'DISTINCT ON' queries with QuerySet.distinct()
-+-
 Reporter:  Manfred Wassmann |Owner:  jgelens
   |   Status:  assigned
 Type:  New feature  |  Version:  SVN
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  dceu2011 |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by akaariai):

 Final cleanup done & attached. All tests should pass on sqlite, and the
 changed tests do pass on PostgreSQL.

 Changes from the previous version:
   - DRY in complier.py join setup for ordering and distinct
   - `NotImplementedError` for .distinct(fields) + annotate/aggregate.
   - Moved the new tests to modeltests/distinct_on_fields

 There are a couple of test-fixes combined in the patch. Create 2500
 objects -> bulk create 2500 objects, one expected failure is no more, and
 one test was testing how executing a query alters the query instance (it
 should not alter it). It now tests the created SQL instead.

 As far as I understand this is now ready for checkin. The only minor thing
 missing is a check for order_by prefix matching distinct_fields prefix.
 The DB will complain if that is broken, so that really isn't a big deal.

 Please review & mark ready for checkin if no problems found. Please check
 extra-carefully added comments. My English isn't that good...

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12738: CSRF token name should be a configurable setting

[Django]

#12738: CSRF token name should be a configurable setting
---+--
 Reporter:  Kronuz |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:
 Severity:  Normal |   Resolution:  wontfix
 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 Kronuz):

 * cc: Kronuz (added)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12809: Add returning of parameters for get_from_clause()

[Django]

#12809: Add returning of parameters for get_from_clause()
-+-
 Reporter:  Kronuz   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:  dynamic queries, |  Unreviewed
  from   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Kronuz):

 * cc: Kronuz (added)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13624: Hide signatures from the debug pages

[Django]

#13624: Hide signatures from the debug pages
-+-
 Reporter:  Kronuz   |Owner:  erikr
 Type:  Uncategorized|   Status:  closed
Component:  Documentation|  Version:  SVN
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Kronuz):

 * cc: Kronuz (added)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #638: changelist table is too wide on pages with filter sidebar

[Django]

#638: changelist table is too wide on pages with filter sidebar
-+-
 Reporter:  wilson   |Owner:  wilson
 Type:  defect   |   Status:  closed
Component:  contrib.admin|  Version:
 Severity:  normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Kronuz):

 * cc: Kronuz (added)
 * ui_ux:   => 0
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14170: Issue in get_language_from_request() if LANGUAGES setting is changed at runtime

[Django]

#14170: Issue in get_language_from_request() if LANGUAGES setting is changed at
runtime
--+-
 Reporter:  Kronuz|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  1.2
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Someday/Maybe
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-
Changes (by Kronuz):

 * cc: Kronuz (added)
 * ui_ux:   => 0
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14399: Site's get_current() not thread safe?

[Django]

#14399: Site's get_current() not thread safe?
---+--
 Reporter:  Kronuz |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.2
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Kronuz):

 * cc: Kronuz (added)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15948: Regarding find_template_source()

[Django]

#15948: Regarding find_template_source()
-+-
 Reporter:  Kronuz   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.3
Component:  Template system  |   Resolution:  duplicate
 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 Kronuz):

 * cc: Kronuz (added)
 * ui_ux:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15562: include_patterns in staticfiles finder

[Django]

#15562: include_patterns in staticfiles finder
-+-
 Reporter:  Kronuz   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  contrib.staticfiles  |  Version:  1.3-rc1
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Kronuz):

 * cc: Kronuz (added)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15716: The has_perm() method of authorization backends should be able to explicitly deny permission

[Django]

#15716: The has_perm() method of authorization backends should be able to
explicitly deny permission
--+
 Reporter:  Kronuz|Owner:  nobody
 Type:  New feature   |   Status:  reopened
Component:  contrib.auth  |  Version:
 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 Kronuz):

 * cc: Kronuz (added)
 * ui_ux:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15793: Filebased email backend should save emails using the ".eml" standard extension

[Django]

#15793: Filebased email backend should save emails using the ".eml" standard
extension
--+
 Reporter:  Kronuz|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Mail)   |  Version:
 Severity:  Normal|   Resolution:  wontfix
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Kronuz):

 * cc: Kronuz (added)
 * ui_ux:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #3011: Allow for extendable auth_user module

[Django]

#3011: Allow for extendable auth_user module
---+
 Reporter:  nowell strite  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.auth   |  Version:
 Severity:  Normal |   Resolution:
 Keywords:  auth_user  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Kronuz):

 * cc: Kronuz (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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15102: find_template returns compiled Template object instead of template source

[Django]

#15102: find_template returns compiled Template object instead of template 
source
-+-
 Reporter:  vmanchev |Owner:  vmanchev
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:  find_template| Triage Stage:  Design
  template source|  decision needed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Kronuz):

 * cc: Kronuz (added)
 * ui_ux:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16781: Wrong SQL for a query-set

[Django]

#16781: Wrong SQL for a query-set
-+-
 Reporter:  Kronuz   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (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 Kronuz):

 * cc: Kronuz (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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #6422: Support for 'DISTINCT ON' queries with QuerySet.distinct()

[Django]

#6422: Support for 'DISTINCT ON' queries with QuerySet.distinct()
-+-
 Reporter:  Manfred Wassmann |Owner:  jgelens
   |   Status:  assigned
 Type:  New feature  |  Version:  SVN
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  dceu2011 |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by Kronuz):

 * cc: Kronuz (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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17385: Make sure the documentation search version field honor the browsed version.

[Django]

#17385: Make sure the documentation search version field honor the browsed 
version.
-+-
 Reporter:  charettes|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Djangoproject.com|  Version:
  Web site   |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  search   |  Needs documentation:  0
  documentation version  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by jezdez):

 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #5763: Queryset doesn't have a "not equal" filter operator

[Django]

#5763: Queryset doesn't have a "not equal" filter operator
-+-
 Reporter:  jdetaeye |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  SVN
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:  Design
 Keywords:  qs-rf|  decision needed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Kronuz):

 * cc: Kronuz (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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17386: Validation & Unicode Character 'ZERO WIDTH SPACE' (U+200B)

[Django]

#17386: Validation & Unicode Character 'ZERO WIDTH SPACE' (U+200B)
---+--
 Reporter:  pennersr   |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Forms  |  Version:  1.3
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by aaugustin):

 Per [http://tools.ietf.org/html/rfc3696#section-2 RFC 3696], email
 addresses can use non-ASCII characters:
 > Any characters, or combination of bits (as octets), are permitted in DNS
 names.

 Names will be encoded with IDNA when an ASCII representation is required.

 The `EmailValidator` takes this into account:

 {{{
 class EmailValidator(RegexValidator):

 def __call__(self, value):
 try:
 super(EmailValidator, self).__call__(value)
 except ValidationError, e:
 # Trivial case failed. Try for possible IDN domain-part
 if value and u'@' in value:
 parts = value.split(u'@')
 try:
 parts[-1] = parts[-1].encode('idna')
 except UnicodeError:
 raise e
 super(EmailValidator, self).__call__(u'@'.join(parts))
 else:
 raise
 }}}

 However, `\u200b` encodes to nothing with IDNA:
 {{{
 >>> u'-\u200b-'.encode('idna') == '--'
 True
 >>> len(u'-\u200b-'.encode('idna'))
 2
 }}}

 I spent some time fighting with various online encoders and couldn't
 confirm or infirm whether this is a valid result.

 Anyway, that's the reason why the email address is valid, after IDNA
 encoding of the domain part.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17037: Add management command to print active project settings

[Django]

#17037: Add management command to print active project settings
-+-
 Reporter:  msabramo |Owner:  msabramo
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  1.3
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  printsettings|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by msabramo):

 Replying to [comment:11 poirier]:
 > Instead of using "===" to mark default settings, how about instead
 prefixing those lines with "# "?  Then the output will be a valid settings
 file, with the settings not changed from the defaults commented out, which
 might be useful.

 That's a great idea! OK, see
 attachment:django_manage_py_diffsettings_all_v2.diff

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17389: Filtering by forkeign keys add unnecessary table joins

[Django]

#17389: Filtering by forkeign keys add unnecessary table joins
-+-
 Reporter:  TwelveSixty  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by akaariai):

 The double NOT is what you get in the current ORM implementation. I assume
 you get WHERE NOT (fk_id IS NOT NULL). Correcting this is not trivial, but
 I think there is some interest in the community to fix this.

 As I haven't actually tested anything, and I think this is a known
 problem, I will leave this as closed.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17037: Add management command to print active project settings

[Django]

#17037: Add management command to print active project settings
-+-
 Reporter:  msabramo |Owner:  msabramo
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  1.3
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  printsettings|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by msabramo):

 * owner:  nobody => msabramo


Comment:

 Assigning to myself so I can work on 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17258: Move threading.local from DatabaseWrapper to connections dictionary

[Django]

#17258: Move threading.local from DatabaseWrapper to connections dictionary
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  SVN
  (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 akaariai):

 I am afraid there is no easy way for connection to be `DBWrapper` instance
 instead of the proxy. If you do in your code:
 {{{
 from django.db import connection
 }}}
 on module level, and the `DBWrapper` isn't threading.local, then that
 connection must be a proxy. BTW this also means that if somebody does this
 for example:
 {{{
 def somefunc(connection=connections['some_alias']):
 # use connection in some way
 }}}
 that would break if used in multithreaded fashion. You are now sharing a
 single connection instead of a threading.local object.

 Would there be any point in making an assert in some proper place of
 `BaseDatabaseWrapper` that a single connection is not shared between
 threads (unless explicitly allowed). That would be really helpful for
 those who would hit multithread-bugs due to this change. I haven't looked
 where that check could be made so that it is checked often enough to
 actually catch something, but seldom enough to not cause performance
 regressions. Maybe ._cursor() for each backend could do this check?

 In short, this change can cause connections to be shared when not actually
 wanted. Before you would be sharing a threading.local, and thus get
 different connections, now you would be sharing the actual connection.
 Allowing this is actually one of the aims of this patch, but this might
 break user code in hard-to-debug ways. So, a guard against this and a way
 to explicitly tell that "I am sharing this connection" would be a good
 thing IMHO.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17394: Models in a package breaks model validation

[Django]

#17394: Models in a package breaks model validation
-+-
 Reporter:  Wilfred Hughes   |Owner:  nobody
  |   Status:  closed
 Type:  Uncategorized|  Version:  1.3
Component:  Database layer   |   Resolution:  invalid
  (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:  0|
-+-
Changes (by aaugustin):

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


Comment:

 As pointed out in charettes' latest comment, the problem is that your
 model isn't detected by validate, because it isn't imported in the
 `test_app.models` package.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #6630: Fieldsets for newforms

[Django]

#6630: Fieldsets for newforms
-+-
 Reporter:  Petr Marhoun |Owner:  nobody
     |   Status:  new
 Type:  New feature  |  Version:  SVN
Component:  Forms|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  feature  |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  1
Easy pickings:  0|
-+-
Changes (by Helot):

 * cc: django@… (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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17393: Test runner should exclude __pycache__ directories

[Django]

#17393: Test runner should exclude __pycache__ directories
-+-
 Reporter:  clelland |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:  Testing Python3  | Triage Stage:  Accepted
  pycache|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by clelland):

 Agreed; I figured it would sit here until 1.4 was released, at least; I
 just didn't want to have it forgotten. I'll see about pushing this up to
 bitbucket as well.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17393: Test runner should exclude __pycache__ directories

[Django]

#17393: Test runner should exclude __pycache__ directories
-+-
 Reporter:  clelland |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:  Testing Python3  | Triage Stage:  Accepted
  pycache|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by lukeplant):

 * stage:  Unreviewed => Accepted


Comment:

 This could be filed against the py3k branch on bitbucket, or we could just
 apply it after that work has been merged. I don't see a need to apply it
 before we have any support for Python 3 in trunk.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17394: Models in a package breaks model validation

[Django]

#17394: Models in a package breaks model validation
-+-
 Reporter:  Wilfred Hughes   |Owner:  nobody
  |   Status:  reopened
 Type:  Uncategorized|  Version:  1.3
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:  0|
-+-

Comment (by charettes):

 What happens if you put {{{from bar import *}}} in your
 {{{models/__init__.py}}} file?

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17394: Models in a package breaks model validation

[Django]

#17394: Models in a package breaks model validation
-+-
 Reporter:  Wilfred Hughes   |Owner:  nobody
  |   Status:  reopened
 Type:  Uncategorized|  Version:  1.3
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:  0|
-+-

Comment (by Wilfred Hughes ):

 I did, but the behaviour is the same both with and without
 test_app/models.py.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17395: runserver should print POST parameters

[Django]

#17395: runserver should print POST parameters
---+--
 Reporter:  RoySmith   |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Uncategorized  |  Version:  1.3
 Severity:  Normal |   Resolution:  wontfix
 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 aaugustin):

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


Comment:

 POST data can be large (think uploaded files), and it's usually not
 included in server logs.

 Typical debug techniques include:
 - adding a `print request.POST` statement in the view function you're
 debugging,
 - adding an `import pdb; pdb.set_trace()` statement in the code you're
 debugging,
 - using the [http://pypi.python.org/pypi/django-debug-toolbar Django debug
 toolbar], which displays lots of things, including POST data.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17394: Models in a package breaks model validation

[Django]

#17394: Models in a package breaks model validation
-+-
 Reporter:  Wilfred Hughes   |Owner:  nobody
  |   Status:  reopened
 Type:  Uncategorized|  Version:  1.3
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:  0|
-+-

Comment (by charettes):

 Did you remove the models.py file created by the startapp command?

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #17395: runserver should print POST parameters

[Django]

#17395: runserver should print POST parameters
---+
 Reporter:  RoySmith   |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  Uncategorized  |Version:  1.3
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 When you run "manage.py runserver", it prints all the GET and POST
 requests it gets.  It would be useful for application debugging if it
 printed the POST parameters as well.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17394: Models in a package breaks model validation

[Django]

#17394: Models in a package breaks model validation
-+-
 Reporter:  Wilfred Hughes   |Owner:  nobody
  |   Status:  reopened
 Type:  Uncategorized|  Version:  1.3
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:  0|
-+-
Changes (by Wilfred Hughes ):

 * status:  closed => reopened
 * resolution:  needsinfo =>


Comment:

 Ah, sorry. Behaviour is exactly the same with the correct value for
 app_label.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17393: Test runner should exclude __pycache__ directories

[Django]

#17393: Test runner should exclude __pycache__ directories
-+-
 Reporter:  clelland |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:  Testing Python3  | Triage Stage:
  pycache|  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by clelland):

 * needs_better_patch:   => 0
 * has_patch:  0 => 1
 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17183: i18n documentation: middleware not mentioned until very late

[Django]

#17183: i18n documentation: middleware not mentioned until very late
-+-
 Reporter:  anonymous|Owner:
 Type:   |  krzysiumed
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.3
 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 krzysiumed):

 * owner:  nobody => krzysiumed
 * status:  new => assigned
 * has_patch:  0 => 1


Comment:

 Note that first link in description of the ticket is broken. The correct
 one is https://docs.djangoproject.com/en/1.3/topics/i18n/deployment/ for
 1.3 and https://docs.djangoproject.com/en/dev/topics/i18n/translation
 /#how-django-discovers-language-preference for dev version.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17257: Comment that contradicts code in django.contrib.syndication.views

[Django]

#17257: Comment that contradicts code in django.contrib.syndication.views
-+-
 Reporter:  aaugustin|Owner:
 Type:   |  krzysiumed
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.syndication  |  Version:  SVN
 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
-+-

Comment (by krzysiumed):

 No, I have not. I thought you '''are''' sure, but you didn't commit the
 fix because you want to leave this easy ticket for newcomers.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17394: Models in a package breaks model validation

[Django]

#17394: Models in a package breaks model validation
-+-
 Reporter:  Wilfred Hughes   |Owner:  nobody
  |   Status:  closed
 Type:  Uncategorized|  Version:  1.3
Component:  Database layer   |   Resolution:  needsinfo
  (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:  0|
-+-
Changes (by anonymous):

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


Comment:

 What happens when you use a correct value for app_label?:

 {{{
 class Foo(models.Model):
 class Meta:
 app_label = 'test_app'
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17257: Comment that contradicts code in django.contrib.syndication.views

[Django]

#17257: Comment that contradicts code in django.contrib.syndication.views
-+-
 Reporter:  aaugustin|Owner:
 Type:   |  krzysiumed
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.syndication  |  Version:  SVN
 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
-+-

Comment (by aaugustin):

 Do you have some evidence that removing the comment is actually the right
 thing to do?

 I didn't commit the fix right away because I wasn't sure of that.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17257: Comment that contradicts code in django.contrib.syndication.views

[Django]

#17257: Comment that contradicts code in django.contrib.syndication.views
-+-
 Reporter:  aaugustin|Owner:
 Type:   |  krzysiumed
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.syndication  |  Version:  SVN
 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 krzysiumed):

 * owner:  nobody => krzysiumed
 * status:  new => assigned
 * has_patch:  0 => 1


Comment:

 Note that file `django/contrib/syndication/feeds.py` was removed. I edited
 file `django/contrib/syndication/views.py`.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #17394: Models in a package breaks model validation

[Django]

#17394: Models in a package breaks model validation
--+
 Reporter:  Wilfred Hughes |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.3
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 If I create an app:

 {{{
 $ ./manage.py startapp test_app
 }}}

 I then create a package for my models:

 {{{
 $ cd test_app
 $ mkdir models
 $ cd models
 $ touch __init__.py
 }}}

 I then create an invalid model in test_app/models/bar.py:

 {{{
 from django.db import models

 class Foo(models.Model):
 class Meta:
 app_label = 'test_app.models'

 invalid_char_field = models.CharField() # should have max_length
 }}}

 Finally, I import this in my tests, I chose test_app/tests.py:

 {{{
 from django.test import TestCase
 from models.bar import Bar

 class SimpleTest(TestCase):
 def test_basic_addition(self):
 """
 Tests that 1 + 1 always equals 2.
 """
 self.assertEqual(1 + 1, 2)
 }}}

 This has a really weird effect on model validation. Calling validate
 works:

 {{{
 $ ./manage.py validate
 0 errors found
 }}}

 But tests seem to have a different validation path, and fail as expected:

 {{{
 $ ./manage.py test test_app
 Creating test database for alias 'default'...
 Error: One or more models did not validate:
 test_app.foo: "invalid_char_field": CharFields require a "max_length"
 attribute that is a positive integer.
 }}}

 I know this isn't a common use case, but I have an old project that has
 models like this. #2289 suggests I should be able to do this. I can work
 around it by adding an import for every single model in
 {{{test_app/models/*.py}}} inside of {{{test_app/__init__.py}}} but that
 introduces name clashes.

 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #17393: Test runner should exclude __pycache__ directories

[Django]

#17393: Test runner should exclude __pycache__ directories
---+-
 Reporter:  clelland   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Testing framework  |Version:  SVN
 Severity:  Normal |   Keywords:  Testing Python3 pycache
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+-
 Beginning with Python 3.2, the Python runtime now stores .pyc files in a
 subdirectory named `__pycache__`, rather than alongside their counterpart
 .py sources. These directories are created automatically any time that the
 code is imported in a Python3.2+ environment.

 The test runner needs to explicitly ignore those directories when
 searching for tests, as it does with hidden files and directories,
 __init__.py files, and dirs named 'sql'. Currently, the full (auto-
 discovered) test suite will not run after tests have been run with Python
 3.

 This may have implications for other auto discovery mechanisms as well.

 Reference: http://www.python.org/dev/peps/pep-3147/

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17384: Bug in tutorial part 4 code: polls/detail.html

[Django]

#17384: Bug in tutorial part 4 code: polls/detail.html
-+-
 Reporter:  dan_coffey@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.3
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  tutorial,| Triage Stage:
  csrf_token |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by kmtracey):

 I strongly suggest updating your code level. 1.1.1 is very old, there have
 been many very significant features and bug fixes made since then.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17381: TemplateView get method passes kwargs into context

[Django]

#17381: TemplateView get method passes kwargs into context
---+--
 Reporter:  ptone  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Generic views  |  Version:  SVN
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by anonymous):

 ptone posted in [https://code.djangoproject.com/ticket/17228#comment:4
 #17228] what I believe should have been the proper way for TemplateView to
 mimic the direct_to_template behavior.

 The current call to `get_context_data` in TemplateView breaks the pattern
 below which I believe is the only way to have multiple inheritance working
 properly especially now that the idea of having a`context_data` dictionary
 have been dismissed in [https://code.djangoproject.com/ticket/16074
 #16074].

 {{{
 def get_context_data(self, **kwargs):
 context = super(MyClass)(kwargs)
 context['foo'] = 'bar'
 return context
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17386: Validation & Unicode Character 'ZERO WIDTH SPACE' (U+200B)

[Django]

#17386: Validation & Unicode Character 'ZERO WIDTH SPACE' (U+200B)
---+--
 Reporter:  pennersr   |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Forms  |  Version:  1.3
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by aaugustin):

 I suppose this character is inserted as an anti-spam mechanism, precisely
 to defeat copy-paste.

 Django won't alter user input silently — it's a bad practice that can
 backfire in interesting ways. And I'm not in favor of defeating a
 purposeful (although debatable) anti-spam mechanism.

 Are non-ASCII characters acceptable in email addresses? If not Django
 should raise a !ValidationError when an email address contains one, which
 would resolve this problem.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #17392: phlebotomy training|phlebotomy certification|phlebotomy classes

[Django]

#17392: phlebotomy training|phlebotomy certification|phlebotomy classes
-+-
 Reporter:   |  Owner:  nobody
  anonymous  | Status:  new
 Type:   |Version:  1.3
  Uncategorized  |   Keywords:  phlebotomy training,phlebotomy
Component:   |  certification,phlebotomy classes
  Uncategorized  |  Has patch:  0
 Severity:  Normal   |  UI/UX:  0
 Triage Stage:   |
  Unreviewed |
Easy pickings:  0|
-+-
 For this reason you have to have a stop profound preparation prior to
 committing your time and effort and cash over a
 [http://phlebotomycoursesinfo.com/phlebotomy-training/#phlebotomy_training
 phlebotomy training] program.An outstanding phlebotomy training school
 will need to assurance that you would possess a comprehensive training
 while in the most significant popular features of phlebotomy, these kinds
 of because human body, blood circulation method, conversation,
 administrative extramarital liasons etcetera. Moreover, the teachers ought
 to have an amazing good name for it has the remarkable exercising, for the
 teachers giving the software programs, as well as the certification
 corporation it is actually linked to. A person's mentoring is exactly what
 issues essentially the most while looking for a career. It truly is within
 the company's attention to engage a effectively-educated phlebotomist who
 seem to continues your phlebotomy accreditation.The
 [http://phlebotomycoursesinfo.com/#phlebotomy_classes phlebotomy classes]
 goods given by a lot of colleges and universities include different time
 frame spans that will trust in the degree which they supply. Intended for
 great example, a documentation stage technique lasts solely a while.
 Whilst the bachelor's degree procedure can last also 4 decades, without
 the need of checking the particular internship period of time that is
 obligatory irrespective of the technique you're looking at.The job are not
 entertained along with deemed by way of medical centers or perhaps every
 wellness relevant features if you have not attained any
 [http://phlebotomycoursesinfo.com/phlebotomy-
 certification/#phlebotomy_certification phlebotomy certification]. That's
 the reason it is very vital that you show up in Phlebotomy training and
 get your unique Phlebotomy documentation. On the other hand, solely two of
 the particular Suggests in the us essentially call for serious
 certification however it's ordinarily safer to get ahead of everyone and
 become experienced at a man or women of the accredited colleges and also
 coaching centers regarding Phlebotomy.Normally, check-ups pertaining to
 Phlebotomy certification tend to be done using a pc within the world-wide-
 web. Now you have an simplicity for many these types of will be using the
 evaluation and there's a even bigger option in which nobody will probably
 omit the actual Phlebotomy examination. Your evaluation with standard is
 definitely arranged in a way that it can be positive that each of the
 Phlebotomy prospects employ a thorough along with substantial being aware
 of all of the themes and also subjects involved to Phlebotomy which is
 finished because they build an examination which happens to be associated
 collected from one of distinct portion towards the up coming.If you have
 not utilized every advanced schooling study system, you need not
 necessarily be anxious.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.