date:20151108

Re: [Django] #25714: DatabaseError: DatabaseWrapper objects created in a thread can only be used in that same thread.

2015-11-08 Thread Django

#25714: DatabaseError: DatabaseWrapper objects created in a thread can only be 
used
in that same thread.
-+-
 Reporter:  brian|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 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):

 Closing the Debian bug and forwarding here was the right thing to do. The
 discussion about single-core / multi-core is irrelevant -- of course you
 can't reproduce an issue that's obviously related to threads when running
 single-threaded.

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

Re: [Django] #25714: DatabaseError: DatabaseWrapper objects created in a thread can only be used in that same thread.

2015-11-08 Thread Django

#25714: DatabaseError: DatabaseWrapper objects created in a thread can only be 
used
in that same thread.
-+-
 Reporter:  brian|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 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 can't tell from the original report which database the person is using
 as the PostgreSQL, MySQL and SQLite adapters are installed. Django allows
 sharing SQLite connections across threads but not PostgreSQL and MySQL
 connections.

 Generally speaking database connections should only be accessed through
 `from django.db import connection` or `from django.db import connections;
 connections[alias]`. This returns thread local objects and avoids this
 problem.

 The TinycryptoPOS application appears to run a daemon; I'm not sure what
 it does exactly but I suspect that's how a connection ends up being
 accessed incorrectly. If every Django user saw that error, we'd probably
 have heard about it by now, so I suspect the bug is in TinycryptoPOS.

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

Re: [Django] #25684: Runserver doesn't use `LOGGING` configuration

2015-11-08 Thread Django

#25684: Runserver doesn't use `LOGGING` configuration
---+
 Reporter:  fcurella   |Owner:  fcurella
 Type:  New feature|   Status:  assigned
Component:  Error reporting|  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  runserver logging  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by andreif):

 My changes are merged now and the log message is not changed with this PR,
 so the behavior is preserved and I think it's time to merge it as soon as
 we agree on the logger name.

 I will play with the log message order and parts in #25704

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

[Django] #25716: Women are Libido Pills - Increase Libido and Enjoy Better Sex Naturally!

2015-11-08 Thread Django

#25716: Women are Libido Pills - Increase Libido and Enjoy Better Sex Naturally!
---+
 Reporter:  nareesmann31   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 We live in a tradition and culture where intercourse performs a crucial
 part to be able to keep well balanced the circumstance. The pills work
 seriously enhances your health and libido degrees, so that you can take
 pleasure in a fit and active and pleasurable sexual intercourse life.
 We've been very pleased to announce that Potenga at any time has no aspect
 results. Using this pill does not increase to numerical way but
 mathematically. Unlike all other products Potenga has skilled a very good
 reaction from each and every one who employs it. We've got taken under
 consideration your actual physical and mental affliction making sure that
 we are able to provide you better and so is Erozon max Libido tablets is
 devoid of affect, but successful. Erozon max Libido pills tend to be the
 greatest simply because it cares not just about your libido amount, but in
 addition impacts the blood flow into the genitals. Medical doctors
 prescribe Erozon max Libido pills regarded the best since it can help you
 to get your intercourse travel again; it boosts the chemical compounds by
 values in the mind. Yu can get all Review of Potenga and Erozon max Libido
 pills from http://liebeslebenonline.com/. In today's environment it can be
 an exceptionally common phenomenon that lots of people today of their
 enjoy lives have complications. One particular finds typically that the
 male companion from complications or diseases suffered as premature
 ejaculation, erectile dysfunction and loss of libido and will cause the
 couples have problems in their adore life. There appeared some medications
 and many chemical-based brokers are available in the market that promises
 to increase sexual motivation, but a lot of them have severe facet results
 and therefore are not powerful. The most effective technique to enhance
 libido, consisting of organic components, is the Erozon max Libido
 tablets. Using Erozon max Libido supplements has several benefits above
 other indicates. Let us check out it.





 The best profit of utilizing Potenga and Erozon max Libido products is the
 fact that it truly is created with the greatest natural ingredients. So,
 eliminate the chance of any type of facet effects. Your like everyday
 living may even be improved due to the fact it could provide you difficult
 erections about a longer time period, which also your lover is well-liked.
 In addition, you contain the choice to decide on time of ejaculation and
 can go on to make appreciate even soon after ejaculation. Now, it can be
 also productive and is also included in many consumers 30 minutes after
 using the capsule. Now which is really astounding. Also, the outcome lasts
 really prolonged. The truth is, it can final approximately forty eight
 hours following taking the pill. What much more could you check with? In
 addition, it lowers time concerning two consecutive orgasms. This is
 certainly also pretty practical for those who are on the lookout ahead to
 possess a extensive evening of love with the companion. In the party you
 are afflicted by illnesses this kind of as erectile dysfunction or
 difficulties in link while using the erection or untimely ejaculation,
 about your adore lifestyle, this will likely be fixed with Potenga and
 Erozon max Libido drugs by improved libido. Therefore if your adore daily
 life was afflicted by this complexity, it is going to aid you to study
 that it creates a long lasting remedy. Review of Potenga and Erozon max
 Libido pills at the moment are offered from
 http://www.testosterontest.com/. Some males have trouble generating enjoy
 because of to an unidentified worry or panic. The truth is, they cannot
 take it easy or are usually not self-assured regarding the complete
 detail. Potenga will definitely enhance your self-confidence and give you
 a cheerful sexual intercourse daily life. You may also have the practice
 to consume in advance of sex and can also have an effect on your
 appreciate lifestyle. There will also be solved by Potenga simply because
 you may make like even following ingesting. Should you have sexual
 intercourse almost never or significantly less commonly, you may as well
 delight in the advantages of Erozon max Libido products.



 Erozon max Libido drugs retains the serotonin ranges during the physique
 at a particular stage, and that is answerable for erection. So that you
 can have actually long love, even up to 45 minutes. Erozon max Libido
 capsules are among the finest all-natural sexual

[Django] #25715: refresh_from_db fails to update null'ed ForeignKeys

2015-11-08 Thread Django

#25715: refresh_from_db fails to update null'ed ForeignKeys
---+
 Reporter:  joshkel|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I have User and Org models, with User having a ForeignKey to Org:

 {{{#!python
 org = models.ForeignKey('Org', null=True, blank=True,
 on_delete=models.SET_NULL)
 }}}

 If I delete an Org instance then refresh the User instance, then
 user.org_id is cleared as expected, but user.org still references the
 deleted instance:

 {{{#!python
 org = create_org()
 user = create_user(org)
 org.delete()

 user.refresh_from_db()
 self.assertIsNone(user.org_id)   # Works!
 self.assertIsNone(user.org)  # Fails!
 }}}

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

Re: [Django] #25544: prefetch_related sends duplicate ids to database

2015-11-08 Thread Django

#25544: prefetch_related sends duplicate ids to database
-+-
 Reporter:  spectras |Owner:  Ian-Foote
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  prefetch duplicate   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by charettes):

 Might be worth pinging Mark about 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/066.6638ffcdf43bf0d61415e0974aecb33d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25714: DatabaseError: DatabaseWrapper objects created in a thread can only be used in that same thread.

2015-11-08 Thread Django

#25714: DatabaseError: DatabaseWrapper objects created in a thread can only be 
used
in that same thread.
-+-
 Reporter:  brian|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 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
-+-
Changes (by brian):

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


Comment:

 Forgot to clarify - The Debian bug report is against Django 1.7.7, however
 I reproduced the above with Django 1.8.4

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

[Django] #25714: DatabaseError: DatabaseWrapper objects created in a thread can only be used in that same thread.

2015-11-08 Thread Django

#25714: DatabaseError: DatabaseWrapper objects created in a thread can only be 
used
in that same thread.
--+
 Reporter:  brian |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.8
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 {{{
 Traceback (most recent call last):
   File "/usr/lib/python2.7/wsgiref/handlers.py", line 85, in run
 self.result = application(self.environ, self.start_response)
   File "/usr/lib/python2.7/dist-
 packages/django/contrib/staticfiles/handlers.py", line 64, in __call__
 return super(StaticFilesHandler, self).__call__(environ,
 start_response)
   File "/usr/lib/python2.7/dist-packages/django/core/handlers/wsgi.py",
 line 177, in __call__
 signals.request_started.send(sender=self.__class__, environ=environ)
   File "/usr/lib/python2.7/dist-packages/django/dispatch/dispatcher.py",
 line 201, in send
 response = receiver(signal=self, sender=sender, **named)
   File "/usr/lib/python2.7/dist-packages/django/db/__init__.py", line 64,
 in close_old_connections
 conn.close_if_unusable_or_obsolete()
   File "/usr/lib/python2.7/dist-packages/django/db/backends/base/base.py",
 line 403, in close_if_unusable_or_obsolete
 self.close()
   File "/usr/lib/python2.7/dist-
 packages/django/db/backends/sqlite3/base.py", line 221, in close
 self.validate_thread_sharing()
   File "/usr/lib/python2.7/dist-packages/django/db/backends/base/base.py",
 line 421, in validate_thread_sharing
 % (self.alias, self._thread_ident, thread.get_ident()))
 DatabaseError: DatabaseWrapper objects created in a thread can only be
 used in that same thread. The object with alias 'default' was created in
 thread id 14020500544 and this is thread id 140201088387984.
 }}}

 Using instructions found in Debian bug report:
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804340

 This looks like a database issue to me, however the reporter of the Debian
 bug thinks it is something to do with the capital-letter-named django
 application. Which seems weird to me.

 A search for similar bugs found #17998 - not idea if this is related or
 not.

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

Re: [Django] #25711: The project template's URLconf doesn't follow the docs' convention for include()

2015-11-08 Thread Django

#25711: The project template's URLconf doesn't follow the docs' convention for
include()
---+
 Reporter:  EvilDMP|Owner:  EvilDMP
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  1.8
 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 EvilDMP):

 You're right, it is consistent when it comes to the docs (at least I can't
 find the example I thought I was looking at, or I just misread it in the
 first place).

 It should be explained though:

 * ''why'' the dotted string is preferred over e.g. `from polls import
 urls; include(urls)`
 * when if ever it would be better to use an imported module rather than a
 dotted string

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

Re: [Django] #25713: Create a new tutorial

2015-11-08 Thread Django

#25713: Create a new tutorial
---+
 Reporter:  EvilDMP|Owner:  nobody
 Type:  New feature|   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
---+
Changes (by carljm):

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

Re: [Django] #8851: Please add a default option to list_filter in the admin interface

2015-11-08 Thread Django

#8851: Please add a default option to list_filter in the admin interface
-+-
 Reporter:  Riskable |Owner:  hvdklauw
     |
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin, list_filter,  | Triage Stage:  Accepted
  default|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by avorio):

 I'm willing to test this out once a patch has been committed.

 Implemented simply, as originally described, this would be a very useful
 feature indeed.

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

Re: [Django] #8851: Please add a default option to list_filter in the admin interface

2015-11-08 Thread Django

#8851: Please add a default option to list_filter in the admin interface
-+-
 Reporter:  Riskable |Owner:  hvdklauw
     |
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin, list_filter,  | Triage Stage:  Accepted
  default|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by avorio):

 * cc: a@… (added)


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

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

Re: [Django] #25711: The project template's URLconf doesn't follow the docs' convention for include() (was: django.conf.urls.include() documentation should be more consistent)

2015-11-08 Thread Django

#25711: The project template's URLconf doesn't follow the docs' convention for
include()
---+
Reporter: EvilDMP|Owner: EvilDMP
Type: Bug| Status: assigned
Component: Documentation | Version: 1.8
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 knbk):

* type: Uncategorized => Bug
* stage: Unreviewed => Accepted

Comment:

Consistency is good, but keep in mind that there are actually three ways
to include urls:

1. A dotted string: `include('polls.urls')`
2. A module containing an `url_patterns` attribute: `from polls import
urls; include(urls)`
3. A list containing patterns: `from polls.urls import url_patterns;
include(url_patterns)`

Method 3 is only ever used to include a list of patterns that's defined in
the same file. Other than that, method 1 is used consistently in all but
the default project template, where it was added in #24635. The ticket
only mentions the dotted view path, but the patch also changes the example
for include.

The convention in the docs is to use a dotted path to include other
URLconf files. In that light, the change in #24635 is simply overzealous
and the current description in the project template is a bug.

I don't think the convention should be changed from method 1 to method 2.
If you'd like to discuss this, I think we should do so on the mailing
list.

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

[Django] #25713: Create a new tutorial

2015-11-08 Thread Django

#25713: Create a new tutorial
---+
Reporter: EvilDMP| Owner: nobody
Type: New feature| Status: new
Component: Documentation |Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
---+
Our tutorial is excellent, but I think we need to be able to address a
wider audience with it.

Our tutorial works much better for people who have some programming
experience than for those who are coming from a web design background.

I want it to be an entry point for someone who knows HTML and CSS (but not
Python, or even programming in general), and wants to move on from static
sites or using other people's applications to building their own
applications.

Part of PHP's success has been the ease with which it allows HTML/CSS
developers to enter into programming by starting with the things that they
are already familiar and comfortable with. We'll never be able to match
that with Python, but I think we can get much closer to it.

At the same time I want to make the effort/result cycle in the tutorial
much tighter than it is now, particularly from the point of view of the
very novice or non-programmer.

== Proposed approach ==

'''I don't propose to replace the existing tutorial''', but will add to it
- in fact, creating an ''alternative'' entry-point that takes a different
approach, and converges on the same outcome, rejoining the flow of the
existing tutorial at a later point.

The tutorial will diverge from the existing tutorial after
https://docs.djangoproject.com/en/dev/intro/tutorial01/#creating-the-
polls-app, and rejoin it at
https://docs.djangoproject.com/en/dev/intro/tutorial05/ (with some minor
reshuffling to make it all work together properly).

I'll do the work in two tranches

* some changes to the application that the existing tutorial creates, to
make it more suited to the new tutorial
* the addition of the new material

For the future I envisage the possibility of adding further entry-points
or paths through the tutorial (for example, a path aimed at PHP
programmers, or one for JavaScript developers who want learn how they
might add Django backend applications to their JS projects), so part of
the work will be to open up the tutorial to this sort of extension.

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

Re: [Django] #25709: Template tag get_available_languages si doing unwanted translation

2015-11-08 Thread Django

#25709: Template tag get_available_languages si doing unwanted translation
-+--
 Reporter:  azurit   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.8
 Severity:  Normal   |   Resolution:  worksforme
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by claudep):

 Replying to [comment:10 azurit]:
 > By the way, slovak local language name returned by get_language_info is
 grammatically incorrect.

 Could you please open a separate ticket for 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 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.98a743ade39584c408d4a887d2f4066e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25452: Email validation for domain `gmail.-com` is considered valid

2015-11-08 Thread Django

* has_patch: 0 => 1

Comment:

[https://github.com/django/django/pull/5612 The pull request]

Unfortunately I have not found a good way to merge URLValidator and
EmailValidator since there are tons of small differences.

So I decided to fix EmailValidator instead. I tried to be as accurate as
possible (actual regex changes are just few characters long).

During reading various RFCs and articles I've found some other easy-
fixable issues (like allowing quoted '@', space or backslash for dot atom
local part, allowing spaces inside quoted local part, etc) those are
included in above PR as well.

Proper RFC-based email validation is a
[http://haacked.com/archive/2007/08/21/i-knew-how-to-validate-an-email-
address-until-i.aspx/ surprisingly hard task] and definitely no one wants
to have [http://www.ex-parrot.com/~pdw/Mail-RFC822-Address.html few pages
long regex] in Django.

So updated validator is still not fully RFC compliant but few issues are
fixed now (or covered with test cases).

Commit messages includes detailed description of all changes that were
made.

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

[Django] #25712: Template overview documentation is not very approachable

2015-11-08 Thread Django

#25712: Template overview documentation is not very approachable
---+
Reporter: jbzdak | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation |Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
---+
Template overview documentation is not very approachable for new people as
it starts with multiple pages of text, that is really about new plug-in
templates. I'm doing a course on Django (in Warsaw University Of
Technology), and I was browsing for some document that I can point
students to and say: "If you have more time before classes read that".

Pluggable template engines (and template engine configuration) are pretty
advanced subjects so ideally they should be on their own page.

I'd suggest the flowing:

* "Overview" that assumes default Django configuration, and mentions
``CONTEXT_PROCESSORS``. Also has some very brief introduction to with
something along the lines: "Engine templates are now pluggable
configuration is there" (and link to other page)
* Add page about template engine configuration and so on.
* Move information about create your own backend to it's own page (as it
is a very advanced subject --- that in dev tree covers also how to create
debug pages for not-built in engines).

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

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

Re: [Django] #25709: Template tag get_available_languages si doing unwanted translation

2015-11-08 Thread Django

#25709: Template tag get_available_languages si doing unwanted translation
-+--
 Reporter:  azurit   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.8
 Severity:  Normal   |   Resolution:  worksforme
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by azurit):

 I know there are lots of other solutions but i wanted a simple and nice
 one - for a gods sake, i just want to show untranslated langauge name of
 my choice! :) By the way, slovak local language name returned by
 get_language_info is grammatically incorrect.

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

Re: [Django] #25701: Add warning to an admin list_view if too many queries are being used

2015-11-08 Thread Django

Comment (by aaugustin):

We discussed this at Django under the Hood. There aren't that many ways to
detect and report the problem at runtime. I think a check when `DEBUG =
True` is a good idea.

I've had this issue on sites where I use the admin and where I have the
debug toolbar installed in dev. I only discovered and fixed in when I
wondered "doesn't this page feel a bit slow?" I wasn't obvious — just the
difference between 50 and 250 ms.

In my opinion this feature would achieve two results:

1. educate newcomers to Django about the N + 1 queries problem in a
textbook example
2. quickly alert more experienced developers when the accidentally create
such a problem

It would need a way to turn it off on with a ModelAdmin option.

I agree that it feels weird to use `django.contrib.messages` to relay
messages to the developer at runtime. Furthermore, I just realized we have
an ordering problem: the admin templates renders messages before iterating
on the queryset to render the changelist. I can't see how we'd implement
that.

I suppose the more traditional alternative to relay that information to
the developer is through logging.

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

Re: [Django] #25709: Template tag get_available_languages si doing unwanted translation

2015-11-08 Thread Django

#25709: Template tag get_available_languages si doing unwanted translation
-+--
 Reporter:  azurit   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.8
 Severity:  Normal   |   Resolution:  worksforme
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by claudep):

 Note that language names in the default `settings.LANGUAGES` are in
 English. `get_language_info` uses the `django.conf.locale.LANG_INFO`
 dictionary which already contains untranslated language name for all
 supported locales.

 If you have specific needs not covered by the utilities from Django, it
 should not be hard to provide your own piece of code for that (view
 context if this is for a specific page, context processor or custom tag if
 you need it more globally).

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

Re: [Django] #25709: Template tag get_available_languages si doing unwanted translation

2015-11-08 Thread Django

#25709: Template tag get_available_languages si doing unwanted translation
-+--
 Reporter:  azurit   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.8
 Severity:  Normal   |   Resolution:  worksforme
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by azurit):

 As i stated before, get_language_info is NOT reading language names from
 settings.py so it won't fix my problem. Currently, i workarounded the
 unwanted translation by suffixing language names with a space, which is
 REALLY ugly hack but there's no other simple solution :(

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

Re: [Django] #25709: Template tag get_available_languages si doing unwanted translation

2015-11-08 Thread Django

#25709: Template tag get_available_languages si doing unwanted translation
-+--
 Reporter:  azurit   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.8
 Severity:  Normal   |   Resolution:  worksforme
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by claudep):

 In the use case of a user having to switch into her own language, you are
 right. But there are also other valid use cases where you want to present
 language names with the current language. That's why Django offers both
 possibilities either through `get_available_languages` or
 `get_language_info`.

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

Re: [Django] #25709: Template tag get_available_languages si doing unwanted translation

2015-11-08 Thread Django

#25709: Template tag get_available_languages si doing unwanted translation
-+--
 Reporter:  azurit   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.8
 Severity:  Normal   |   Resolution:  worksforme
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by azurit):

 What is the point in translating language names into current language?
 Language names should always be in the local translation so everyone will
 understand them. This seems to me like an old Nokia mobile joke where you
 just switched a language of friends phone to Chinese and Nokia was
 displaying also language names in Chinese so he/she was unable to switch
 it back without trying all languages and finding the correct one.

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

Re: [Django] #25709: Template tag get_available_languages si doing unwanted translation

2015-11-08 Thread Django

#25709: Template tag get_available_languages si doing unwanted translation
-+--
 Reporter:  azurit   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.8
 Severity:  Normal   |   Resolution:  worksforme
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by azurit):

 Using get_language_info is not the solution as it is NOT reading langauge
 names from settings.py - it is simply not using my own names but some kind
 of Django defined names (which it generates based on country code). I
 don't understand why get_available_languages is translating langauge
 names, if someone wants translated names, he/she can use _() in
 settings.py (which also documentation suggests).

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

Re: [Django] #25709: Template tag get_available_languages si doing unwanted translation

2015-11-08 Thread Django

#25709: Template tag get_available_languages si doing unwanted translation
-+--
 Reporter:  azurit   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.8
 Severity:  Normal   |   Resolution:  worksforme
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by claudep):

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


Comment:

 The fact that the language name is translated is documented:
 https://docs.djangoproject.com/en/1.8/topics/i18n/translation/#get-
 available-languages

 If you want to get the untranslated language name, you can access it
 through `get_language_info`:
 https://docs.djangoproject.com/en/1.8/topics/i18n/translation/#get-
 language-info

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

Re: [Django] #25701: Add warning to an admin list_view if too many queries are being used

2015-11-08 Thread Django

Comment (by jacinda):

I don't think this would be a replacement for django-debug-toolbar. I
think it's actually most useful if the warning suggests to the user that
they use django-debug-toolbar or a similar tool to diagnose the cause of
the high number of queries. This just lets them know that there's
something that should be investigated.

I think the checks framework suggestion is good, but wouldn’t help people
detect if they had a poorly constructed callable in list_display since it
would be the callable name in list_select_related and not a field name.

Yep, I was assuming this feature would only work in DEBUG mode. I don't
think this is something most people would want to show up in production.

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

Re: [Django] #25684: Runserver doesn't use `LOGGING` configuration

2015-11-08 Thread Django

#25684: Runserver doesn't use `LOGGING` configuration
---+
 Reporter:  fcurella   |Owner:  fcurella
 Type:  New feature|   Status:  assigned
Component:  Error reporting|  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  runserver logging  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by fcurella):

 > As far as I see, django.request is used for application and we probably
 want to distinguish between those log messages and the ones made by server

 That's the reason why I went with `django.request.runserver` instead of
 just `django.request`.

 That said, we can pick a new namespace and update the docs accordingly.
 I'd like more consensus on which one to use.

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

Re: [Django] #25544: prefetch_related sends duplicate ids to database

2015-11-08 Thread Django

#25544: prefetch_related sends duplicate ids to database
-+-
 Reporter:  spectras |Owner:  Ian-Foote
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  prefetch duplicate   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by spectras):

 I do not know if it is related, but  ̀ArrayField.get_db_prep_value` always
 converts tuples to lists.

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

Re: [Django] #25709: Template tag get_available_languages si doing unwanted translation

2015-11-08 Thread Django

#25709: Template tag get_available_languages si doing unwanted translation
-+
 Reporter:  azurit   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by azurit):

 Can i ask which Django version will include this fix and approximately
 when it will be released? Thank you.

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

Re: [Django] #25711: django.conf.urls.include() documentation should be more consistent

2015-11-08 Thread Django

#25711: django.conf.urls.include() documentation should be more consistent
---+--
 Reporter:  EvilDMP|Owner:  EvilDMP
 Type:  Uncategorized  |   Status:  assigned
Component:  Documentation  |  Version:  1.8
 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 bpeschier):

 For reference: https://docs.djangoproject.com/en/1.8/releases/1.8/#django-
 conf-urls-patterns

 This is the argument made in 1.8 encouraging people to import **views**.
 Unless there is a strong argument (or multiple!) against advising people
 to do the same for includes, I think it would be consistent to advise
 importing over dotted 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/065.2f1e292abeeabe460570c7e042beb115%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25686: Database router without "allow_migrate" method raises exception

2015-11-08 Thread Django

#25686: Database router without "allow_migrate" method raises exception
-+-
 Reporter:  jcugat   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  allow_migrate| Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * stage:  Accepted => Ready for checkin


Comment:

 Only the release note will need to be backported to stable/1.9.x and the
 master branch since `allow_syncdb`  support has been dropped in 1.9

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

[Django] #25711: django.conf.urls.include() documentation should be more consistent

2015-11-08 Thread Django

#25711: django.conf.urls.include() documentation should be more consistent
---+
Reporter: EvilDMP| Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation |Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
---+
* in the tutorial https://docs.djangoproject.com/en/dev/intro/tutorial01
/#write-your-first-view we advise to use `include('polls.urls'))`
* in the default project template

https://github.com/django/django/blob/master/django/conf/project_template/project_name/urls.py#L12-L15
we advise to import the module and use `url(r'^blog/',
include(blog_urls))`
* in https://docs.djangoproject.com/en/dev/topics/http/urls/#including-
other-urlconfs we have examples of both - even in the same file

I think that we need to be more consistent and clearer about this.

For the tutorial and the default `urls.py` I like the use of a dotted
string rather than an import; it's one less thing to do.

Other than that, should we generally prefer one style over another? I can
imagine that a dotted string might sometimes help avoid a circular import
or have related advantages, but otherwise they seem to behave in just the
same way.

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

Re: [Django] #25711: django.conf.urls.include() documentation should be more consistent

2015-11-08 Thread Django

#25711: django.conf.urls.include() documentation should be more consistent
---+--
 Reporter:  EvilDMP|Owner:  EvilDMP
 Type:  Uncategorized  |   Status:  assigned
Component:  Documentation  |  Version:  1.8
 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
---+--
Changes (by EvilDMP):

 * status:  new => assigned
 * needs_docs:   => 0
 * owner:  nobody => EvilDMP
 * needs_tests:   => 0
 * needs_better_patch:   => 0


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

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

Re: [Django] #25693: Data loss if a ManyToManyField is shadowed by Prefetch

2015-11-08 Thread Django

#25693: Data loss if a ManyToManyField is shadowed by Prefetch
-+-
 Reporter:  Ian-Foote|Owner:  Ian-Foote
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * needs_better_patch:  0 => 1
 * version:  master => 1.7
 * needs_docs:  0 => 1


Comment:

 The patch is looking good. It's only missing a release note for the 1.8
 and 1.7 series.

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

Re: [Django] #25709: Template tag get_available_languages si doing unwanted translation

2015-11-08 Thread Django

#25709: Template tag get_available_languages si doing unwanted translation
-+
 Reporter:  azurit   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by iljamaas):

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

[Django] #25710: Document what INTERNAL_IPS does

2015-11-08 Thread Django

#25710: Document what INTERNAL_IPS does
--+
 Reporter:  knbk  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.8
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 The [https://docs.djangoproject.com/en/1.8/ref/settings/#internal-ips
 current documentation] says:

 > A tuple of IP addresses, as strings, that:
 > * See debug comments, when DEBUG is True
 > * Receive X headers in admindocs if the XViewMiddleware is installed
 (see The Django admin documentation generator)

 The documentation of `DEBUG` doesn't mention `INTERNAL_IPS` at all, and
 the documentation of the admindocs only briefly mentions it in the last
 line.

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

Re: [Django] #25544: prefetch_related sends duplicate ids to database

2015-11-08 Thread Django

#25544: prefetch_related sends duplicate ids to database
-+-
 Reporter:  spectras |Owner:  Ian-Foote
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  prefetch duplicate   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by akaariai):

 A possibility is to try-except the deduping of the values. If it doesn't
 succeed, just use the original values.

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

Re: [Django] #25696: Add sphinx extension to django.contrib

2015-11-08 Thread Django

#25696: Add sphinx extension to django.contrib
---+--
 Reporter:  codingjoe  |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  1.8
 Severity:  Normal |   Resolution:  wontfix
 Keywords:  sphinx, docs   | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by codingjoe):

 Thanks, will do.

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

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

Re: [Django] #14370: Adding support for Autocomplete in contrib.admin

2015-11-08 Thread Django

#14370: Adding support for Autocomplete in contrib.admin
-+-
 Reporter:  tyrion   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  autocomplete,| Triage Stage:  Accepted
  jquery, javascript, widgets,   |
  admin  |
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-
Changes (by RamezIssac):

 * cc: ramezashraf@… (added)


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

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

Re: [Django] #25684: Runserver doesn't use `LOGGING` configuration

2015-11-08 Thread Django

#25684: Runserver doesn't use `LOGGING` configuration
---+
 Reporter:  fcurella   |Owner:  fcurella
 Type:  New feature|   Status:  assigned
Component:  Error reporting|  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  runserver logging  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by andreif):

 I have moved server time in https://github.com/fcurella/django/pull/3 so
 it's not hardcoded in message and used in formatters format.

 Discard my comment about global_settings, `DEFAULT_LOGGING` is the right
 place :)

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

Re: [Django] #14370: Adding support for Autocomplete in contrib.admin

2015-11-08 Thread Django

Comment (by carljm):

And a third argument for not using a CDN -- we'd be quietly introducing
another point of failure into people's projects.

That said, the "or some build method" idea is probably a better one. It
might be nice if we used bower or something similar to automate pulling in
the outside JS dependencies, instead of manually vendoring them. But it's
also not really a big deal. Vendored dependencies are more easily
auditable, and everyone can figure out how to upgrade them when necessary.

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

Re: [Django] #14370: Adding support for Autocomplete in contrib.admin

2015-11-08 Thread Django

Comment (by aaugustin):

Not using a CDN is a conscious choice.

There are at least two reasons for this:

* privacy (avoid leaking info through the Referer header)
* offline use (download the tar.gz and the docs once and use them for
local development: not everyone on Earth has convenient access to a high-
speed, permanent Internet connection, in doubt we'd rather favor the use
case of the least privileged people)

I'm aware that these are social arguments, not technical ones, and I stand
by them.

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

Re: [Django] #25544: prefetch_related sends duplicate ids to database

2015-11-08 Thread Django

#25544: prefetch_related sends duplicate ids to database
-+-
 Reporter:  spectras |Owner:  Ian-Foote
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  prefetch duplicate   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by carljm):

 @charettes I think that's a good idea! As long as we're confident that a)
 there are no other valid cases outside ArrayField where an unhashable
 value might be passed in an `__in` lookup rhs, and b) every value passed
 to an ArrayField lookup should always be iterable. But I can't come up
 with any counter-examples to either of those.

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

Re: [Django] #14370: Adding support for Autocomplete in contrib.admin

2015-11-08 Thread Django

#14370: Adding support for Autocomplete in contrib.admin
-+-
 Reporter:  tyrion   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  autocomplete,| Triage Stage:  Accepted
  jquery, javascript, widgets,   |
  admin  |
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-

Comment (by codingjoe):

 I don't know, this is `django.contrib.admin` not `core` were're talking
 about. I don't see why we should improve it using more javascript
 libraries.
 I don't like the fact tho, that it is being distributed within our repo. I
 would go for a CDN or some build method.

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

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

Re: [Django] #23251: Use a temporary folder to store uploaded files during tests

2015-11-08 Thread Django

#23251: Use a temporary folder to store uploaded files during tests
-+
 Reporter:  shai |Owner:
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  file storage upload  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by carljm):

 FWIW, there's also [https://pypi.python.org/pypi/django-inmemorystorage
 django-inmemorystorage], which is even simpler/faster. But it wouldn't
 allow leaving the files around after a failed test run for inspection.

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

Re: [Django] #25709: Template tag get_available_languages si doing unwanted translation

2015-11-08 Thread Django

#25709: Template tag get_available_languages si doing unwanted translation
-+--
 Reporter:  azurit   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by azurit):

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

Re: [Django] #25709: Template tag get_available_languages si doing unwanted translation

2015-11-08 Thread Django

#25709: Template tag get_available_languages si doing unwanted translation
-+
 Reporter:  azurit   |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Template system  |Version:  1.8
 Severity:  Normal   | Resolution:
 Keywords:   |   Triage Stage:  Unreviewed
Has patch:  0|  Easy pickings:  0
UI/UX:  0|
-+
Changes (by azurit):

 * Attachment "patchfile" added.


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

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

Re: [Django] #25526: Document how to output color from custom management commands

2015-11-08 Thread Django

#25526: Document how to output color from custom management commands
--+
 Reporter:  bmispelon |Owner:  elenaoat
 Type:  Cleanup/optimization  |   Status:  assigned
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:  1 |UI/UX:  0
--+
Changes (by elenaoat):

 * owner:  Anagha22 => elenaoat


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

[Django] #25709: Template tag get_available_languages si doing unwanted translation

2015-11-08 Thread Django

#25709: Template tag get_available_languages si doing unwanted translation
-+
 Reporter:  azurit   |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Template system  |Version:  1.8
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 I have this defined in my settings.py:


 {{{
 LANGUAGES = (
 ('sk', u'Slovenčina'),
 ('en', u'English'),
 )
 }}}


 I don't want the language names to be translated and this is why i don't
 used _(). While using template tag get_available_languages to get list of
 available langauges, the language names are getting translated anyway.

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

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

Re: [Django] #25469: Add an auto escape setting to the Django template engine

2015-11-08 Thread Django

#25469: Add an auto escape setting to the Django template engine
-+
 Reporter:  aidanlister  |Owner:  jgeskens
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  templates| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by aaronelliotross):

 * cc: aaronelliotross@… (added)


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

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

Re: [Django] #25469: Add an auto escape setting to the Django template engine

2015-11-08 Thread Django

#25469: Add an auto escape setting to the Django template engine
-+
 Reporter:  aidanlister  |Owner:  jgeskens
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  templates| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+

Comment (by aaronelliotross):

 OK, pull request added (https://github.com/django/django/pull/5610).

 Jef, want to take a look and see what you think? Sorry I didn't get in
 touch earlier, I will add myself to the CC here!

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

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

Re: [Django] #14370: Adding support for Autocomplete in contrib.admin

2015-11-08 Thread Django

#14370: Adding support for Autocomplete in contrib.admin
-+-
 Reporter:  tyrion   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  autocomplete,| Triage Stage:  Accepted
  jquery, javascript, widgets,   |
  admin  |
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-

Comment (by RamezIssac):

 May i ask why select2 ?!

 Can this patch be done in a way that ease 3rd party integration , (or make
 it optional to use select2) rather then changing the default ?!

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

Re: [Django] #25684: Runserver doesn't use `LOGGING` configuration

2015-11-08 Thread Django

#25684: Runserver doesn't use `LOGGING` configuration
---+
 Reporter:  fcurella   |Owner:  fcurella
 Type:  New feature|   Status:  assigned
Component:  Error reporting|  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  runserver logging  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by andreif):

 As far as I see, `django.request` is used for application and we probably
 want to distinguish between those log messages and the ones made by
 server...

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

Re: [Django] #25616: Add note regarding missing dependencies on LookupError for migrations

2015-11-08 Thread Django

#25616: Add note regarding missing dependencies on LookupError for migrations
--+
 Reporter:  mcfletch  |Owner:  tmilan81
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by MarkusH):

 * needs_better_patch:  0 => 1
 * needs_tests:  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/066.7b854484f71430b8e47f05e838db3268%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

54 matches

Mail list logo