Re: [Django] #10825: Template filter date 'U' raises an AttributeError under certain circumstances

[Django]

#10825: Template filter date 'U' raises an AttributeError under certain
circumstances
--+-
  Reporter:  mk   | Owner:  gsong
Status:  assigned | Milestone:  1.1  
 Component:  Template system  |   Version:  SVN  
Resolution:   |  Keywords:  template date
 Stage:  Accepted | Has_patch:  0
Needs_docs:  0|   Needs_tests:  0
Needs_better_patch:  0|  
--+-
Changes (by gsong):

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

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #10931: truncate_html_words doen't handle multi-line tags properly

[Django]

#10931: truncate_html_words doen't handle multi-line tags properly
--+-
  Reporter:  gsong| Owner:  gsong 
Status:  assigned | Milestone:
 Component:  Template system  |   Version:  SVN   
Resolution:   |  Keywords:  truncatewords_html
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by gsong):

  * needs_tests:  1 => 0

Comment:

 I've updated the patch with tests that are pretty comprehensive.

-- 
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] #10977: In some cases, the intersection of two QuerySets is empty when it shouldn't be

[Django]

#10977: In some cases, the intersection of two QuerySets is empty when it 
shouldn't
be
--+-
 Reporter:  zain  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.0   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 This bug is best demonstrated by an example with two querysets, qs and
 other_qs:

 {{{
 >>> qs
 [, ]
 >>> other_qs
 []
 >>> qs[0] == other_qs[0]
 True
 >>> qs & other_qs
 []
 }}}

 I'm attaching a test case to demonstrate the conditions for this to
 happen.

-- 
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] #10975: Accessing derived block doesn't work within ifequal tag

[Django]

#10975: Accessing derived block doesn't work within ifequal tag
---+
  Reporter:  libwill...@gmail.com  | Owner:  nobody
Status:  closed| Milestone:
 Component:  Uncategorized |   Version:  SVN   
Resolution:  invalid   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

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

Comment:

 A block cannot be defined conditionally within any sort of "if" construct,
 and this is by design; the structure of the template is the structure of
 the template.

-- 
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] #10061: incorrect logout link in admin

[Django]

#10061: incorrect logout link in admin
---+
  Reporter:  lashni| Owner:  mtredinnick
Status:  new   | Milestone:  1.1
 Component:  django.contrib.admin  |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  1 |   Needs_tests:  1  
Needs_better_patch:  1 |  
---+
Comment (by Alex):

 We also didn't lose any docs, jacob just committed them separately(which
 was really the right way to handle it in the first 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 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] #10061: incorrect logout link in admin

[Django]

#10061: incorrect logout link in admin
---+
  Reporter:  lashni| Owner:  mtredinnick
Status:  new   | Milestone:  1.1
 Component:  django.contrib.admin  |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  1 |   Needs_tests:  1  
Needs_better_patch:  1 |  
---+
Comment (by dc):

 Have misunderstood you. I have nothing against namespaces but I just do
 not like this particular implementation. That was my point. I believe that
 you will solve problem in more elegant way. I'm sorry for disturbance.

-- 
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] #10061: incorrect logout link in admin

[Django]

#10061: incorrect logout link in admin
---+
  Reporter:  lashni| Owner:  mtredinnick
Status:  new   | Milestone:  1.1
 Component:  django.contrib.admin  |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  1 |   Needs_tests:  1  
Needs_better_patch:  1 |  
---+
Comment (by mtredinnick):

 *sigh* Please let's not have design discussions in tickets. Also, give us,
 the core commiters, some credit. We don't want to make things more
 implicit and fragile. That's simply a ridiculous assertion. We go for
 solid code, as well as neatness and usability.

 As I noted in my original comment, the replacing of colons by nothing is
 simply a bug in the patch. It actually leads to ambiguous situations. I
 doubt that I'll be committing that particular line, for example. That's
 why patches are uploaded and reviewed with great care and why this ticket
 has not yet been closed. It's a very subtle area (before you post a
 comment pointing out that jacob moved it to "ready for checkin" .. yes, I
 noticed. Reasonable people can disagree on the state and timing of things
 and I'm sure Jacob would have carefully examined things before finally
 committing as well.)

 Just wait a little bit and this will be resolved, please. There's a long
 history of the development of this. Search the django-dev archives for a
 lot fo the design discussion if you really care to look at it.

-- 
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] #10061: incorrect logout link in admin

[Django]

#10061: incorrect logout link in admin
---+
  Reporter:  lashni| Owner:  mtredinnick
Status:  new   | Milestone:  1.1
 Component:  django.contrib.admin  |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  1 |   Needs_tests:  1  
Needs_better_patch:  1 |  
---+
Comment (by dc):

 ok but how "namespaces" in admin-urls.12.diff differ from for e.g. {% url
 var1|concat:var2|concat:var3 %} Why do you want to make all this more
 implicit and fragile?

-- 
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] #10061: incorrect logout link in admin

[Django]

#10061: incorrect logout link in admin
---+
  Reporter:  lashni| Owner:  mtredinnick
Status:  new   | Milestone:  1.1
 Component:  django.contrib.admin  |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  1 |   Needs_tests:  1  
Needs_better_patch:  1 |  
---+
Changes (by mtredinnick):

  * owner:  Alex => mtredinnick
  * status:  reopened => new

Comment:

 @dc, you're missing a whole bunch of context here, I suspect. Yes, it will
 be slightly backwards-incompatible and the colon was chosen for precisely
 that reason. We need namespaces in URL reversing now. it's basically a bug
 that it isn't there at the moment. We've chosen a character that is both
 readable, common to the majority of keyboards and relatively unlikely to
 appear in names (as opposed to, say, dashes or underscores, which are more
 commonly used or commas, which are going to be a readability hassle). The
 infrastructure in place here is designed to handle things a bit more broad
 than just the admin case.

 So, yes, this approach is necessary. The particular line you point at is
 indeed a bug in the patch.

 Since I'm in the neighbourhood now, assigning to me so that I remember to
 commit this darn thing over the weekend.

-- 
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] #10976: missing template files for correctly executing test cases on django.contrib.auth

[Django]

#10976: missing template files for correctly executing test cases on
django.contrib.auth
+---
  Reporter:  aarond10   | Owner:  nobody
Status:  new| Milestone:  1.1   
 Component:  Testing framework  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by aarond10):

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

Comment:

 Sorry, I havent had time to put these in patch format but the changes are
 trivial.

 django/contrib/auth/tests/views.py:
 Remove the setUp() and tearDown() functions in the PasswordResetTest
 class.

 django/contrib/auth/tests/templates/registration/password_reset_form.html
 {{ form }}

 django/contrib/auth/tests/templates/registration/password_reset_email.html
 {{ protocol }}://{{ domain }}/reset/{{ uid }}-{{ token }}/

 django/contrib/auth/tests/templates/registration/password_reset_confirm.html
 {% if validlink %}
 Please enter your new password:
 {{ form }}
 {% else %}
 The password reset link was invalid
 {% endif %}

 django/contrib/auth/tests/templates/registration/password_reset_done.html
 django/contrib/auth/tests/templates/registration/password_reset_complete.html
 Empty file will do fine.

-- 
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] #10061: incorrect logout link in admin

[Django]

#10061: incorrect logout link in admin
---+
  Reporter:  lashni| Owner:  Alex
Status:  reopened  | Milestone:  1.1 
 Component:  django.contrib.admin  |   Version:  SVN 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  1 |   Needs_tests:  1   
Needs_better_patch:  1 |  
---+
Changes (by dc):

  * needs_better_patch:  0 => 1
  * stage:  Ready for checkin => Accepted
  * needs_tests:  0 => 1
  * needs_docs:  0 => 1

Comment:

 admin-urls.12.diff has lost all documentation.
 Changes in core/urlresolvers.py and url template tag are not documented
 and do not have tests.

 {{{
 viewname = ''.join(viewname.split(':'))
 }}}
 is especially ugly. Whole thing looks like dirty hack and this line can be
 replaced by
 {{{
 viewname = viewname.replace(':', '')
 }}}
 anyway.

 Is this ticket really so complicated that it needs special infrastructure
 in resolvers?

-- 
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] #10061: incorrect logout link in admin

[Django]

#10061: incorrect logout link in admin
---+
  Reporter:  lashni| Owner:  mtredinnick
Status:  new   | Milestone:  1.1
 Component:  django.contrib.admin  |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  1 |   Needs_tests:  1  
Needs_better_patch:  1 |  
---+
Comment (by mtredinnick):

 Yes, you are mistaken. That's not why we're using namespaces.
 Unsurprisingly, it will be documented.

-- 
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] #10225: Cache middleware does not honor "Cache-Control: no-cache" in request headers

[Django]

#10225: Cache middleware does not honor "Cache-Control: no-cache" in request
headers
---+
  Reporter:  erny  | Owner:  nobody
Status:  closed| Milestone:
 Component:  Cache system  |   Version:  1.0   
Resolution:  invalid   |  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by JohnMoylan):

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

Comment:

 I think this ticket confuses HTTP caching with application caching. The
 no-cache directive sets HTTP headers that are used to validate content on
 a HTTP proxy cache or web browser cache. The documentation also makes a
 clear distinction between these types of caching.

 This ticket should be marked as invalid.

-- 
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] #10061: incorrect logout link in admin

[Django]

#10061: incorrect logout link in admin
---+
  Reporter:  lashni| Owner:  mtredinnick
Status:  new   | Milestone:  1.1
 Component:  django.contrib.admin  |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  1 |   Needs_tests:  1  
Needs_better_patch:  1 |  
---+
Comment (by dc):

 Maybe i'm wrong, but it looks like that you are inventing namespaces as
 workaround for url tag inability to work with template variables. I still
 think that you are breaking butterfly on the wheel (and "just strip colon
 and reverse" is not a very good thing IMHO). But if core developers really
 think that this is the best way...[[BR]]At least document it please.

-- 
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] #10061: incorrect logout link in admin

[Django]

#10061: incorrect logout link in admin
---+
  Reporter:  lashni| Owner:  Alex
Status:  reopened  | Milestone:  1.1 
 Component:  django.contrib.admin  |   Version:  SVN 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  1 |   Needs_tests:  1   
Needs_better_patch:  1 |  
---+
Comment (by dc):

 Also change in core/urlresolvers.py is backwards-incompatible as someone
 can use ':' in view names.

-- 
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] #10976: missing template files for correctly executing test cases on django.contrib.auth

[Django]

#10976: missing template files for correctly executing test cases on
django.contrib.auth
---+
 Reporter:  aarond10   |   Owner:  nobody
   Status:  new|   Milestone:  1.1   
Component:  Testing framework  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 This has taken me a while to wrap my head around. I hope I have it right.

 When the test cases for django.contrib.auth run, they reassign
 settings.TEMPLATE_DIRS to use a local set of templates. This works fine
 for login purposes but the password reset pages don't exist in the current
 SVN repository so application paths are searched and if
 password_reset_email.html can be found elsewhere, its loaded and rendered.
 Unfortunately, since the test cases also use their own URLs, any
 references to named {% url %} tags in password_reset_email.html lead to
 NoReverseMatch exceptions.

 Could someone please put some basic templates in the
 contrib/auth/tests/templates/ folder to avoid these errors?

-- 
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] #10970: auto_now_add for DateField evaluetes to datetime.datetime instance

[Django]

#10970: auto_now_add for DateField evaluetes to datetime.datetime instance
---+
  Reporter:  summerisgone  | Owner:  nobody 

Status:  new   | Milestone: 

 Component:  Database layer (models, ORM)  |   Version:  1.0

Resolution:|  Keywords:  DateField, 
auto_now_add
 Stage:  Unreviewed| Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  1  

Needs_better_patch:  1 |  
---+
Changes (by ramiro):

  * has_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 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] #10936: Detailed instructions for getting Django and MySQL and MySQLdb working on various OS X versions

[Django]

#10936: Detailed instructions for getting Django and MySQL and MySQLdb working 
on
various OS X versions
-+--
  Reporter:  simon   | Owner:  nobody 
Status:  new | Milestone: 
 Component:  Documentation   |   Version:  SVN
Resolution:  |  Keywords:  mysqldb
 Stage:  Design decision needed  | Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Comment (by adamnelson):

 Anyway, at least a strong statement on the wiki telling people that,
 unlike PHP/Perl (where most future Django people will be coming from, i.e.
 the audience for this wiki page), that Sqlite3 really is the way to go for
 desktop development.

 Not one person I've introduced to Django knew that on their own.  Each one
 struggled to install MySQL and MySQLdb on their Mac (since that's about
 what they would have done for PHP) before I told them it's a waste of time
 and they should just use Sqlite3 which works by default.

 That isn't clear from the docs and I'm confident that many people are
 trying in vain to install MySQL and associated libraries for only minimal
 benefit.

-- 
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] #10936: Detailed instructions for getting Django and MySQL and MySQLdb working on various OS X versions

[Django]

#10936: Detailed instructions for getting Django and MySQL and MySQLdb working 
on
various OS X versions
-+--
  Reporter:  simon   | Owner:  nobody 
Status:  new | Milestone: 
 Component:  Documentation   |   Version:  SVN
Resolution:  |  Keywords:  mysqldb
 Stage:  Design decision needed  | Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Comment (by mtredinnick):

 Both of the assertions in comment:5 aren't correct. MySQL is tested at
 least as much as PostgreSQL, arguably has more code in Django to support
 it and is quite possibly even used more in terms of raw numbers, since
 it's the default with a bunch of hosting accounts. Also, developing
 against a database other than SQLite3 is often a good idea. Even necessary
 if you're using some of the database-specific features, such as postgis or
 text-field searching (MySQL) or stored procedures (vary per database),
 etc.

 I feel this whole ticket is probably a bit out-of-scope, since being a
 sysadmin for your box isn't really a goal of Django. Some pointers to
 links to help people do that setup or, as noted elsewhere, a wiki page
 maintained by people who actually do this and need it would probably be
 more efficient and accurate.

-- 
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] #10975: Accessing derived block doesn't work within ifequal tag

[Django]

#10975: Accessing derived block doesn't work within ifequal tag
--+-
 Reporter:  libwill...@gmail.com  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Uncategorized | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Here is the http://dpaste.com/40134/ code of what I mean. Essentially
 using a block in a derived template that was specified from within an
 ifequal tag in the parent template doesn't work.

-- 
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] #10936: Detailed instructions for getting Django and MySQL and MySQLdb working on various OS X versions

[Django]

#10936: Detailed instructions for getting Django and MySQL and MySQLdb working 
on
various OS X versions
-+--
  Reporter:  simon   | Owner:  nobody 
Status:  new | Milestone: 
 Component:  Documentation   |   Version:  SVN
Resolution:  |  Keywords:  mysqldb
 Stage:  Design decision needed  | Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Comment (by adamnelson):

 Actually, when I was new to Django, I didn't know a few things:

  1. The Django community does in fact favor PostgreSQL.  It might be good
 to simply make that clear to first-time users that PostgreSQL is the most
 common DB used on Django production environments.MySQL is fine (I use it
 over PostgreSQL) but here's the important part ...
  1. Developers should typically use Sqlite3 and neither Postgres or MySQL
 except for QA and live environments.  It's a much more portable/simple
 database backend for development and it works on Mac out of the box.

 I went through a whole bunch of shenanigans to get MySQL running on Mac
 only to realize that I would never run my project on anything but Linux
 anyway and that with the ORM, Sqlite3 is fine for development purposes.

 So, I think this ticket should be sidestepped with a clear declaration
 that PostgreSQL is the most test db backend and that development is
 easiest with Sqlite3 as the backend - the ORM abstracting most differences
 away.

-- 
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] #10939: Allow for dynamic registration of inlines into an admin model

[Django]

#10939: Allow for dynamic registration of inlines into an admin model
---+
  Reporter:  zbyte64   | Owner:  nobody 
Status:  new   | Milestone: 
 Component:  django.contrib.admin  |   Version:  1.0
Resolution:|  Keywords:  inlines
 Stage:  Unreviewed| Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by zbyte64):

 Only works if inlines is a list, no?

 {{{
 admin.site.unregister(FlatPageAdmin)
 FlatPageAdmin.inlines = list(FlatPageAdmin.inlines)
 FlatPageAdmin.inlines += [FlatPageAttachment]
 admin.site.register(FlatPage, FlatPageAdmin)
 }}}

 I suppose I didn't want 4 lines of code for something that used to be so
 easy :/

-- 
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] #8754: PYTHONPATH not passed through to regressiontests/admin_scripts/AdminScriptTestCase.run_test()

[Django]

#8754: PYTHONPATH not passed through to
regressiontests/admin_scripts/AdminScriptTestCase.run_test()
---+
  Reporter:  Richard Davies   |
 Owner:  nobody
Status:  new   | 
Milestone:  1.1   
 Component:  Testing framework |   
Version:  SVN   
Resolution:|  
Keywords:
 Stage:  Accepted  | 
Has_patch:  1 
Needs_docs:  0 |   
Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by Richard Davies ):

 As mentioned above under [**] it may be that with the advent of JYTHONPATH
 the incoming configuration is always readable by that mechanism. If that's
 the case then we could now back out r8238 completely and lose some
 complexity. Here's a patch which does this - but would need someone who
 uses Jython with external database backends to test it before I actually
 prefer it to the less aggressive 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] #8754: PYTHONPATH not passed through to regressiontests/admin_scripts/AdminScriptTestCase.run_test()

[Django]

#8754: PYTHONPATH not passed through to
regressiontests/admin_scripts/AdminScriptTestCase.run_test()
---+
  Reporter:  Richard Davies   |
 Owner:  nobody
Status:  new   | 
Milestone:  1.1   
 Component:  Testing framework |   
Version:  SVN   
Resolution:|  
Keywords:
 Stage:  Accepted  | 
Has_patch:  1 
Needs_docs:  0 |   
Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Richard Davies ):

  * milestone:  => 1.1

Comment:

 Apologies - I had assumed that Jacob's "Accepted" was in reply to Karen.

 I'm not a Jython user, but have now read Karen's comments and references.

 There are two scenarios:
 A) external database backends (which all of the patches refer to. so is
 presumably more common),
 B) built-in database backends which need to import the actual database
 driver (i.e. psycopg itself; my case)

 In either case, PYTHONPATH, etc. may be needed to locate the relevant
 modules.

 r8149 identified problem A, fixed for standard Python it by passing
 PYTHONPATH through, and hence also fixed B.

 r8238 realized that the above did not work for Jython of that time, where
 PYTHONPATH is not used and JYTHONPATH did not yet exist. Hence it replaced
 r8149 with _ext_backend_path() which locates external database backends
 under either Python or Jython. This fixes A on Jython too, but
 coincidentally breaks B on both platforms.

 r8400 doesn't address either A or B. It deal with the fact that Jython
 started to support configuration using JYTHONPATH (rather than
 -J-Dpython.path=), and hence we should be using that to configure the
 subprocesses. I think the comment on #8268 that Karen refers to is poorly
 phrased - JYTHONPATH does not need to be cleared for subprocesses (and
 indeed is not today!), but rather should be set and reset just like
 PYTHONPATH. [**] What I'm not clear about with r8400 is whether we can not
 safely __read__ JYTHONPATH, as well as __writing__ to it. If this were the
 case, then we could back out all the complexity of r8238 and
 _ext_backend_path() completely.


 So, in conclusion, r8238 did indeed inadvertently break scenario B (only
 scenario A was considered). I don't believe that there is ever any danger
 in adding to the end of either PYTHONPATH or JYTHONPATH - the code was
 just removed for cleanliness, given that _ext_backend_path() was meant to
 provide the same functionality.

 Given that _ext_backend_path() does not in fact provide this functionality
 in scenario B, my original patch remains a valid fix, under Python or (I
 believe) Jython.

-- 
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] #10965: Django should use an online translation system.

[Django]

#10965: Django should use an online translation system.
+---
  Reporter:  stavros| Owner:  nobody
Status:  closed | Milestone:
 Component:  Translations   |   Version:  SVN   
Resolution:  invalid|  Keywords:
 Stage:  Someday/Maybe  | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by mtredinnick):

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

Comment:

 Integrating with an existing online system is certainly a possibility. A
 requirement for any choice is that it won't *require* people to use it,
 since a web browser is a horrible text editor, so we shouldn't force
 people down that path if they're already comfortable with their existing
 tools and editors. There would also need to be ways to have staging and
 validation of changes, because we don't want automatic commits of
 essentially rubbish translations going on.

 I've looked at transifex in the past and it's a possibility, certainly,
 since it is possible to make it worth as an addition to existing
 processes. Launchpad's system certainly used to be much clunkier than
 transifex (I would consider the latter to be the leading candidate for
 something like this, by the way -- it's very well designed).

 In any case, though, this isn't really a good ticket, since it's a huge
 item with no single resolution. Broad feature additions and process
 enhancements like this are more "TODO list" items than bug reports.
 Closing as invalid for that reason. After 1.1 is out, feel free to start a
 discussion on the django-i18n list about this, bearing in mind the above
 requirements and thinking about any extra things that might be
 appropriate. A good post that lays out some possibilities and the trade-
 offs (something that only says "Django should do this" isn't useful, as
 there's clearly multiple sides and compromises in anything like this) will
 be interesting to read and discuss. Right now isn't the right time,
 though, since it really can't get the full attention it needs with Django
 1.1 coming up (it won't just be the translators themselves that are
 involved in the discussion and decisions).

-- 
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] #10974: Beta version 1.1. 404 error when I log out of Admin Site.

[Django]

#10974: Beta version 1.1. 404 error when I log out of Admin Site.
---+
  Reporter:  Mac   | Owner:  nobody
Status:  closed| Milestone:
 Component:  django.contrib.admin  |   Version:  1.0   
Resolution:  duplicate |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

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

Comment:

 Dupe of #10061.

-- 
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] #10965: Django should use an online translation system.

[Django]

#10965: Django should use an online translation system.
+---
  Reporter:  stavros| Owner:  nobody
Status:  new| Milestone:
 Component:  Translations   |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Someday/Maybe  | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Alex):

  * stage:  Unreviewed => Someday/Maybe

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #10974: Beta version 1.1. 404 error when I log out of Admin Site.

[Django]

#10974: Beta version 1.1. 404 error when I log out of Admin Site.
--+-
 Reporter:  Mac   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  1.0   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 I get a 404 error when I log out of the Administration Site. After
 clicking on logout, it throws me to
 http://localhost:8000/admin/admin/logout/ instead of
 http://localhost:8000/admin/logout/. In the Site Admininstration, clicking
 on change password throws me to a undefined url,
 http://localhost:8000/admin/admin/password_change/.

-- 
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] #10965: Django should use an online translation system.

[Django]

#10965: Django should use an online translation system.
---+
  Reporter:  stavros   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Translations  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by stavros):

 It might also be possible to just upload the .po files to Launchpad and
 let users translate them there, its translation interface is very easy and
 effective.

-- 
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] #10965: Django should use an online translation system.

[Django]

#10965: Django should use an online translation system.
---+
  Reporter:  stavros   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Translations  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by stavros):

 There already are such systems (e.g. http://transifex.org/, which is OSS
 and actually written on Django), and I don't think it would be that hard
 to set up... Its developers can frequently be found in #django, so one
 could ask there for any information...

-- 
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] #10834: BaseHandler does not handle resolver returning None

[Django]

#10834: BaseHandler does not handle resolver returning None
+---
  Reporter:  xerolas| Owner:  ccahoon
Status:  new| Milestone: 
 Component:  HTTP handling  |   Version:  SVN
Resolution: |  Keywords: 
 Stage:  Accepted   | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by ccahoon):

  * owner:  nobody => ccahoon

-- 
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] #9493: Formsets with data that violates unique constraints across forms are not marked invalid

[Django]

#9493: Formsets with data that violates unique constraints across forms are not
marked invalid
---+
  Reporter:  Alex  | Owner:  Alex
Status:  new   | Milestone:  1.1 
 Component:  Forms |   Version:  1.0 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  1 |  
---+
Changes (by russellm):

  * needs_better_patch:  0 => 1
  * stage:  Ready for checkin => Accepted

Comment:

 On the whole, this patch looks good. However, I have two comments:

  1. The patch needs to be updated to include the formset analog of
 #10134/[10646] (avoiding duplication of logic, if possible).
  2. While this patch correctly catches the error condition, I'm not
 satisfied with the way the error is reported. Consider the use case where
 you have 100 inline forms - a top level "There's a duplicate" error
 doesn't really help identify the pair of forms that is actually causing
 the problem. In addition to the formset level error, the individual forms
 should be marked as being in error.

-- 
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] #10516: Admin search doesn't work when having multiple search_fields to the same base model.

[Django]

#10516: Admin search doesn't work when having multiple search_fields to the same
base model.
---+
  Reporter:  akaariai  | Owner:  zain   
   
Status:  reopened  | Milestone:  1.1
   
 Component:  django.contrib.admin  |   Version:  1.0
   
Resolution:|  Keywords:  search, 
inheritance, admin
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by zain):

  * status:  closed => reopened
  * 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] #10516: Admin search doesn't work when having multiple search_fields to the same base model.

[Django]

#10516: Admin search doesn't work when having multiple search_fields to the same
base model.
---+
  Reporter:  akaariai  | Owner:  zain   
   
Status:  closed| Milestone:  1.1
   
 Component:  django.contrib.admin  |   Version:  1.0
   
Resolution:  fixed |  Keywords:  search, 
inheritance, admin
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by zain):

  * status:  assigned => closed
  * has_patch:  0 => 1
  * resolution:  => fixed

Comment:

 I'll bring up the (possible) ORM bug on the mailing list as a separate
 bug. It's actually pretty easy fix this bug without hitting the other one.
 Fix incoming.

-- 
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] #8087: Template tags 'ifin' and 'ifnotin' checking if element is present in sequence

[Django]

#8087: Template tags 'ifin' and 'ifnotin' checking if element is present in
sequence
-+--
  Reporter:  emes| Owner:  nobody   
 
Status:  new | Milestone:   
 
 Component:  Template system |   Version:  SVN  
 
Resolution:  |  Keywords:  templatetag, 
tag, sequence
 Stage:  Design decision needed  | Has_patch:  1
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Comment (by anonymous):

 tom: fantastic, exactly what I need. :)

-- 
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
-~--~~~~--~~--~--~---