Re: [Django] #13218: django-syndication can't handle https URLs

[Django]

#13218: django-syndication can't handle https URLs
+---
  Reporter:  schaefer   | Owner:  bfirsh
Status:  new| Milestone:
 Component:  RSS framework  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by samkeen):

 * cc: samkeen (removed)
 * cc: sk...@mozilla.com (added)

Comment:

 Just checking on progress for this bug

 I found that as mentioned, I could work around the generation of the
  tag by providing the entire URL (including the https), But the
 syndication framework is generating the http://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Fpreview.addons.mozilla.org
 %2Fen-US%2Ffirefox%2Faddon%2F10868%2Fversions%2Fformat%3Arss

 I'm new to the Django ticket triage process, but it looks like the next
 stage for this ticket is "ready for checkin".  Let me know if there is
 anything I can do to help move this patch towards being landed.

 thanks

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13218: django-syndication can't handle https URLs

[Django]

#13218: django-syndication can't handle https URLs
+---
  Reporter:  schaefer   | Owner:  bfirsh
Status:  new| Milestone:
 Component:  RSS framework  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by samkeen):

 * cc: samkeen (added)

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #2227: atch] transaction.commit()/rollback() should be aware of nested calls to transaction.managed(True)

[Django]

#2227: atch] transaction.commit()/rollback() should be aware of nested calls to
transaction.managed(True)
---+
  Reporter:  md...@yandex.ru   | Owner:  nobody 
   
Status:  assigned  | Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  SVN
   
Resolution:|  Keywords:  
transaction, nest, scope, nested, rollback, commit
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  1 |  
---+
Comment (by Glenn):

 For most intents and purposes, savepoints *are* nested transactions, just
 presented a bit differently.  I don't think there's anything actually
 lacking in the back-end--you just have to switch from transactions to
 savepoints once you're nesting.  With this tucked away in a decorator (and
 a context manager, etc.), the difference doesn't even have to be visible
 to high-level code and simply be presented as nested transactions.

 I've used savepoints this way for a while now, and it works extremely
 well.  It ensures that I can call a function that accesses the database,
 and if it throws an exception, the database will be left where it was
 before I called the function.  I can catch exceptions and, if appropriate,
 reliably recover the existing transaction.  Without this, I have to
 carefully audit everything that might access the database, so I know
 whether exceptions from a function are unrecoverable and force me to abort
 the entire request in order to roll it back all the way.  That's a
 terrible loss of abstraction.

-- 
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-upda...@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] #2227: atch] transaction.commit()/rollback() should be aware of nested calls to transaction.managed(True)

[Django]

#2227: atch] transaction.commit()/rollback() should be aware of nested calls to
transaction.managed(True)
---+
  Reporter:  md...@yandex.ru   | Owner:  nobody 
   
Status:  assigned  | Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  SVN
   
Resolution:|  Keywords:  
transaction, nest, scope, nested, rollback, commit
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  1 |  
---+
Changes (by jacmkno):

  * keywords:  transaction, nest, scope => transaction, nest, scope,
   nested, rollback, commit

Comment:

 I really like Glenn's approach because the lack of nested transaction
 management in the back-end databases is made transparent to the
 programmer. I think that solving this problem with database features will
 be a good idea when when those features are ready to fully support nested
 transactions. In the current implementation good documentation of
 transactional functions in your app is required to mantain data
 consitency, and Glen's approach would reduce this need significantly.

-- 
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-upda...@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] #3508: MergeDict needs more descriptive return values from __str__ and __repr__

[Django]

#3508: MergeDict needs more descriptive return values from __str__ and __repr__
+---
  Reporter:  thebanana  | Owner: 
Status:  new| Milestone: 
 Component:  Core framework |   Version:  SVN
Resolution: |  Keywords: 
 Stage:  Ready for checkin  | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  1  
Needs_better_patch:  0  |  
+---
Comment (by mlissner):

 Can we get this checked in? contrib.auth.views has several uses of
 request.REQUEST, and I just had the occasion to need to inspect them.
 Having this patch would have made life easier, for sure.

-- 
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-upda...@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] #13956: Indefinite args for simpletags and inclusion tags

[Django]

#13956: Indefinite args for simpletags and inclusion tags
--+-
  Reporter:  melinath | Owner:  gregmuellegger   
Status:  assigned | Milestone:   
 Component:  Template system  |   Version:  SVN  
Resolution:   |  Keywords:  simple_tag, simpletag
 Stage:  Accepted | Has_patch:  1
Needs_docs:  1|   Needs_tests:  0
Needs_better_patch:  0|  
--+-
Changes (by gregmuellegger):

  * keywords:  => simple_tag, simpletag
  * version:  1.2 => SVN
  * needs_tests:  1 => 0

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13982: django admin overwrites objects

[Django]

#13982: django admin overwrites objects
--+-
  Reporter:  dragon_men   | Owner:  nobody
Status:  closed   | Milestone:
 Component:  django-admin.py  |   Version:  1.1   
Resolution:  invalid  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by dragon_men):

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

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13983: Hosting Requirements for Django

[Django]

#13983: Hosting Requirements for Django
-+--
  Reporter:  Tim N   | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Uncategorized   |   Version:  1.2   
Resolution:  duplicate   |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by kmtracey):

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

Comment:

 Duplicate of #13981.

-- 
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-upda...@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] #13981: Hosting Requirements for Django

[Django]

#13981: Hosting Requirements for Django
+---
  Reporter:  tnach  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.2   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by kmtracey):

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

Comment:

 Django's ticket tracker is for bug reports, not support questions. A
 better place to ask this question would be the django-users 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 post to this group, send email to django-upda...@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] #6669: @transaction.commit_on_success does not rollback when it should

[Django]

#6669: @transaction.commit_on_success does not rollback when it should
---+
  Reporter:  ja...@10gic.net   | Owner:  nobody 

Status:  new   | Milestone: 

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

Resolution:|  Keywords:  
transaction, commit
 Stage:  Accepted  | Has_patch:  0  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  0 |  
---+
Comment (by dben...@gmail.com):

 I hit this problem too. Is this the intended behavior? It seems other
 people have hit this- http://www.mail-archive.com/django-
 us...@googlegroups.com/msg99702.html

-- 
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-upda...@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] #13516: sqlall silently ignores any fields that are a subclass of AutoField

[Django]

#13516: sqlall silently ignores any fields that are a subclass of AutoField
---+
  Reporter:  manfre| Owner:  manfre
Status:  reopened  | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Ready for checkin | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by manfre):

  * stage:  Accepted => Ready for checkin

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13516: sqlall silently ignores any fields that are a subclass of AutoField

[Django]

#13516: sqlall silently ignores any fields that are a subclass of AutoField
---+
  Reporter:  manfre| Owner:  manfre
Status:  reopened  | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by manfre):

  * 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-upda...@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] #13983: Hosting Requirements for Django

[Django]

#13983: Hosting Requirements for Django
-+--
  Reporter:  Tim N   | Owner:  nobody
Status:  new | Milestone:
 Component:  Uncategorized   |   Version:  1.2   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by Tim N ):

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

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13983: Hosting Requirements for Django

[Django]

#13983: Hosting Requirements for Django
+---
 Reporter:  Tim N   |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Uncategorized   | Version:  1.2   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 Hi there,

 I've recently came across a client who has a Django built System they were
 told by their hosting provider they needed to pay 520.00 a month to
 support the Django framework.  Is it possible to send me all hosting
 requirements for Django so I can find them a new more affordable solution
 with my hosting partner.  I plan on setting them up on a dedicated box
 with the following provider http://www.theplanet.com/dedicated-
 hosting.aspx


 Thanks for your help

-- 
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-upda...@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] #13516: sqlall silently ignores any fields that are a subclass of AutoField

[Django]

#13516: sqlall silently ignores any fields that are a subclass of AutoField
---+
  Reporter:  manfre| Owner:  manfre
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:  fixed |  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by manfre):

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

Comment:

 Added patch for Django v1.2 (up to r13444).

 There is also the workaround of overriding get_internal_type in the
 subclass to return "AutoField" instead of self.class.__name__ (from class
 Field). The issue is that the internal type is passed to the database
 backends so they can map the field to a database type.


 {{{
 class MyAutoField(models.AutoField):
 def get_internal_type(self):
 return "AutoField"
 }}}

-- 
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-upda...@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] #13982: django admin overwrites objects

[Django]

#13982: django admin overwrites objects
-+--
 Reporter:  dragon_men   |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  django-admin.py  | Version:  1.1   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 Hi , I think django has a problem in admin, I have a model like :

 class Test(models.Model):
 code_test= models.CharField(max_length=5,primary_key=True)
 name = models.CharField(max_length=15)


 when i get to admin and i make add a test fill the fields with for example
 code_test = a and name = first test. And them make save, until there no
 problem it saves. now I add another Test  and  the fields this time
 Code_teste = a and name = second test.

 this time django OVERWRITES the older object, instead of saying that the
 object with that pk already exists.  please tell help i have this problem
 in one produtive system.

 Django version 1.1.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-upda...@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] #13981: Hosting Requirements for Django

[Django]

#13981: Hosting Requirements for Django
---+
 Reporter:  tnach  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Hi there,

 I've recently came across a client who has a Django built System they were
 told by their hosting provider they needed to pay 520.00 a month to
 support the Django framework.  Is it possible to send me all hosting
 requirements for Django so I can find them a new more affordable solution
 with my hosting partner.  I plan on setting them up on a dedicated box
 with the following provider http://www.theplanet.com/dedicated-
 hosting.aspx


 Thanks for your help

-- 
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-upda...@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] #12651: AutoSlugField, that can recreate unique slugs during saving.

[Django]

#12651: AutoSlugField, that can recreate unique slugs during saving.
-+--
  Reporter:  Ciantic | Owner:  nobody
Status:  new | Milestone:
 Component:  Uncategorized   |   Version:
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Changes (by JMagnusson):

 * cc: ja...@jmagnusson.com (added)

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13980: The markdown template tag in django.contrib.markup should not be marked as safe output

[Django]

#13980: The markdown template tag in django.contrib.markup should not be marked 
as
safe output
---+
  Reporter:  nomulous  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Changes (by anonymous):

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

Comment:

 Please add a proper SVN diff file

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13516: sqlall silently ignores any fields that are a subclass of AutoField

[Django]

#13516: sqlall silently ignores any fields that are a subclass of AutoField
---+
  Reporter:  manfre| Owner:  manfre
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by manfre):

  * owner:  nobody => manfre

-- 
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-upda...@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] #13980: The markdown template tag in django.contrib.markup should not be marked as safe output

[Django]

#13980: The markdown template tag in django.contrib.markup should not be marked 
as
safe output
--+-
 Reporter:  nomulous  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Contrib apps  | Version:  1.2   
 Keywords:|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 I'm not sure about the other markup options, but Markdown itself should
 definitely not be marked as safe. You can easily render alert('pwned') with Markdown, and with
 that is_safe = True there, the HTML will not be escaped.

-- 
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-upda...@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] #13906: REPEATABLE READ (as used by default on MySQL) breaks atleast QuerySet.get_or_create().

[Django]

#13906: REPEATABLE READ (as used by default on MySQL) breaks atleast
QuerySet.get_or_create().
---+
  Reporter:  sebastian_noack   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by sebastian_noack):

 The solution I have proposed includes adding a setting, but would make
 READ COMMITTED the default. Yes, this would break backward compatibility.
 But the user just have to set a setting, to get the old behaviour back.
 And on the other hand it makes most ORM code even more compatible with
 MySQL. So code that was tested against any other database backends would
 work more reliable on MySQL with that change.

 Btw, I have looked at modeltests/transactions/models.py and noted that the
 tests in there are bypassed for mysql. I don't have looked in detail at
 the tests, but it looks like that there are known issues with MySQL and
 transactions. And I would not wonder if that is because of the different
 isolation level.

-- 
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-upda...@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] #5494: javascript_catalog generic view only search catalogs in application/locale and not in project/locale

[Django]

#5494: javascript_catalog generic view only search catalogs in 
application/locale
and not in project/locale
---+
  Reporter:  anonymous | Owner: 
Status:  new   | Milestone: 
 Component:  Internationalization  |   Version:  SVN
Resolution:|  Keywords:  javascript i18n
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by EmilStenstrom):

  * needs_better_patch:  1 => 0

Comment:

 Removing "Patch needs improvement" since there's a new patch waiting for
 review.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13906: REPEATABLE READ (as used by default on MySQL) breaks atleast QuerySet.get_or_create().

[Django]

#13906: REPEATABLE READ (as used by default on MySQL) breaks atleast
QuerySet.get_or_create().
---+
  Reporter:  sebastian_noack   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by akaariai):

 Ok, I see your point.

 However I seriously doubt that changing the default transaction isolation
 level will be accepted, as it is a big backwards incompatible change. A
 better option would probably be isolation level setting in settings.py.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13976: Admin view with relations (ForeignKey or ManyToMany) does not limit number of entries in document

[Django]

#13976: Admin view with relations (ForeignKey or ManyToMany) does not limit 
number
of entries in document
--+-
  Reporter:  yn...@opera.com  | Owner:  nobody
Status:  closed   | Milestone:
 Component:  Uncategorized|   Version:  1.1   
Resolution:  invalid  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by yn...@opera.com):

 * cc: hcarvalhoalves (added)

Comment:

 Currently I am not using Django 1.2, as it is incompatible with the Django
 1.1 generated tables I have.

 In any case, it should not be necessary to manually override such cases.
 It is quite likely that many models in production will have tables that
 quickly grow to a size in which the 1.1 form of presenting the relations
 will become too cumbersome, and the code should automatically adapt to 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-upda...@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] #694: [patch] TEMPLATE_DIRS should allow project root relative paths

[Django]

#694: [patch] TEMPLATE_DIRS should allow project root relative paths
--+-
  Reporter:  nirvdrum | Owner:  adrian
Status:  closed   | Milestone:
 Component:  Template system  |   Version:  SVN   
Resolution:  wontfix  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by ubernostrum):

 Quoting myself: '''If you disagree, start a thread on the django-
 developers list.'''

 So if you feel strongly about this, you know what to 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 post to this group, send email to django-upda...@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] #11052: Q-Object disjunction join promotion .. bug

[Django]

#11052: Q-Object disjunction join promotion .. bug
---+
  Reporter:  emulbreh  | Owner:  
mtredinnick   
Status:  assigned  | Milestone:  1.3
   
 Component:  Database layer (models, ORM)  |   Version:  SVN
   
Resolution:|  Keywords:  m2m, join, 
null, q
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  1  
   
Needs_better_patch:  1 |  
---+
Comment (by rcarton):

 I am unsure this is related but:

 {{{
 In [81]: PullPending.objects.exclude(~Q(id__in=[])).count()
 Out[81]: 53

 In [82]: PullPending.objects.exclude(~Q(id__in=[]) & Q(id__gt=-1)).count()
 Out[82]: 0
 }}}

 Correct me if I'm wrong:

  1. should return 0 (exclude any object whose id is ''not'' in an empty
 dict, hence exclude all the objects)
  1. should return 0 too, the only difference is like q1 & q2 where q2 is
 always true.

 As I understand it:

  * exclude('True') -> does not exclude
  * exclude('True' and 'True') -> does exclude.

-- 
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-upda...@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] #13979: Django manage.py doesn ’t work with IPython

[Django]

#13979: Django manage.py doesn’t work with IPython
-+--
 Reporter:  ingo86   |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Core framework   | Version:  1.2   
 Keywords:  manage.py shell ipython  |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 I am on MacOSX Snow Leopard and I'm using python 2.6.5 installed with
 macports. I'm inside a virtualenv.
 I can't run python manage.py shell after installing IPython but I can run
 IPython standalone.
 I figured out that the following line, contained into IPython is what
 causes the issue:
 {{{
 (status, result) = commands.getstatusoutput( "otool -L %s | grep libedit"
 % _rl.__file__ )
 }}}

 This happens because for a strange reason, the method getstatusoutput is
 not available when i launch python manage.py shell but it's available when
 I launch ipython. I can import the commands module in both cases. I tried
 looking at the sys.path during the execution of both, but there are no
 differences.

-- 
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-upda...@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] #13906: REPEATABLE READ (as used by default on MySQL) breaks atleast QuerySet.get_or_create().

[Django]

#13906: REPEATABLE READ (as used by default on MySQL) breaks atleast
QuerySet.get_or_create().
---+
  Reporter:  sebastian_noack   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by sebastian_noack):

 I have written about that issue in my blog.

 http://www.no-ack.org/2010/07/mysql-transactions-and-django.html

-- 
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-upda...@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.