Re: [Django] #9935: The session db backend throws UnicodeEncodeError when used with Oracle

2009-01-08 Thread Django 
#9935: The session db backend throws UnicodeEncodeError when used with Oracle
--+-
  Reporter:  jamesli  | Owner:  nobody  
 
Status:  new  | Milestone:  post-1.0
 
 Component:  django.contrib.sessions  |   Version:  1.0 
 
Resolution:   |  Keywords:  oracle session 
unicode UnicodeEncodeError
 Stage:  Unreviewed   | Has_patch:  0   
 
Needs_docs:  0|   Needs_tests:  0   
 
Needs_better_patch:  0|  
--+-
Comment (by jamesli):

 I can confirm that cx_oracle 4.4.1 works fine (at least I didn't run into
 the problem I reported 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 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] #9935: The session db backend throws UnicodeEncodeError when used with Oracle

2009-01-08 Thread Django 
#9935: The session db backend throws UnicodeEncodeError when used with Oracle
--+-
  Reporter:  jamesli  | Owner:  nobody  
 
Status:  new  | Milestone:  post-1.0
 
 Component:  django.contrib.sessions  |   Version:  1.0 
 
Resolution:   |  Keywords:  oracle session 
unicode UnicodeEncodeError
 Stage:  Unreviewed   | Has_patch:  0   
 
Needs_docs:  0|   Needs_tests:  0   
 
Needs_better_patch:  0|  
--+-
Comment (by jamesli):

 Replying to [comment:4 ikelly]:
 > What version of cx_Oracle is being used in these setups?  My hope is
 that this is occurring with cx_Oracle 5.0, in which case the solution is
 easy: don't use that.  cx_Oracle 5.0 has a known NCLOB decoding bug that
 makes it unusable for Django (I suppose we should document this).
 cx_Oracle trunk and the upcoming 5.0.1 release should be okay, as is the
 4.4.1 release.
 >
 > If you're not using cx_Oracle 5.0, let me know so we can investigate
 further.

 Indeed, I was using version 5.0. Will try version 4.4.1 later.

-- 
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] #1946: [patch] to allow overriding of default sequence name

2009-01-08 Thread Django 
#1946: [patch] to allow overriding of default sequence name
---+
  Reporter:  ab...@cabal.org.uk| Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  1 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Comment (by mtredinnick):

 For anybody working to bring this to conclusion, a few notes from some
 discussions Rob Hudson and I have had about this:

 There are three separate sub-problems that probably need to be addressed.
  1. Manually specifying the sequence name to use.
  2. Specifying that `ModelA` should use the same sequence name as `ModelB`
  3. Perhaps: somehow creating the sequence for case 1.

 It's not necessarily compulsory that all are solved, and the original
 problem description only looks at situation 1, from what I understand. The
 difficulty there is when does this sequence we are referring to by name
 get created? It can't be as part of "initial SQL" processing or
 post_syncdb signal handling, since that's after the table has been created
 and, presumably, the sequence has to exist before you can refer to it in a
 table definition. Maybe that's completely out of scope (quite possibly).
 If not, it's situation 3. Solving that certainly makes testing a lot
 easier (might well move it from "impossible" into the "possible"
 category).

 The second point, above, seems to be something that might crop up quite
 naturally here. If you want to share a sequence for some reason, you need
 to indicate that, but you don't actually know the name of the sequence.
 Again, maybe out of scope, although it would be nice if it were possible.

-- 
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] #9025: Nested Inline Support in Admin

2009-01-08 Thread Django 
#9025: Nested Inline Support in Admin
-+--
  Reporter:  pixelcort   | Owner:  nobody
Status:  new | Milestone:
 Component:  django.contrib.admin|   Version:  1.0   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Changes (by knoffhoff):

 * cc: steffen.jas...@descript.de (removed)

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

Re: [Django] #6845: Model validation and its propagation to ModelForms

2009-01-08 Thread Django 
#6845: Model validation and its propagation to ModelForms
-+--
  Reporter:  Honza_Kral  | Owner:  Honza_Kral   
 
Status:  new | Milestone:  post-1.0 
 
 Component:  Forms   |   Version:  SVN  
 
Resolution:  |  Keywords:  newforms validation model 
modelform ep2008
 Stage:  Accepted| Has_patch:  1
 
Needs_docs:  1   |   Needs_tests:  1
 
Needs_better_patch:  1   |  
-+--
Comment (by Honza_Kral):

 Replying to [comment:59 mrts]:
 > I have nothing against gruntwork :). I'll take care of porting 0.96
 validators to `django.db.models.validators`.

 please don't put it there - it should server for form validation as well.

 Validators are functions like this:
 {{{
 def validate_something( value, all_values={}, instance=None ):
   if i_dont_like( value ):
 raise ValidationError( 'I dont like %r' % value,
 error_code=validators.SOME_CODE )
 }}}
 where error code is some constant that will later be used to remap the
 default errors in custom_messages

-- 
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] #6845: Model validation and its propagation to ModelForms

2009-01-08 Thread Django 
#6845: Model validation and its propagation to ModelForms
-+--
  Reporter:  Honza_Kral  | Owner:  Honza_Kral   
 
Status:  new | Milestone:  post-1.0 
 
 Component:  Forms   |   Version:  SVN  
 
Resolution:  |  Keywords:  newforms validation model 
modelform ep2008
 Stage:  Accepted| Has_patch:  1
 
Needs_docs:  1   |   Needs_tests:  1
 
Needs_better_patch:  1   |  
-+--
Comment (by mrts):

 I have nothing against gruntwork :). I'll take care of porting 0.96
 validators to `django.db.models.validators`.

-- 
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] #9749: ModelAdmin should allow specifying Changelist class to further modify Changelist behavior

2009-01-08 Thread Django 
#9749: ModelAdmin should allow specifying Changelist class to further modify
Changelist behavior
---+
  Reporter:  anonymous | Owner:  david  
   
Status:  assigned  | Milestone: 
   
 Component:  django.contrib.admin  |   Version:  1.0
   
Resolution:|  Keywords:  ModelAdmin 
Changelist subclass
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  1 |   Needs_tests:  1  
   
Needs_better_patch:  1 |  
---+
Changes (by david):

 * cc: lar...@gmail.com (removed)
  * owner:  nobody => david
  * 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] #9749: ModelAdmin should allow specifying Changelist class to further modify Changelist behavior

2009-01-08 Thread Django 
#9749: ModelAdmin should allow specifying Changelist class to further modify
Changelist behavior
---+
  Reporter:  anonymous | Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  django.contrib.admin  |   Version:  1.0
   
Resolution:|  Keywords:  ModelAdmin 
Changelist subclass
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  1 |   Needs_tests:  1  
   
Needs_better_patch:  1 |  
---+
Changes (by brosner):

  * stage:  Design decision needed => 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 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] #9974: Allow pluralize filter to consider zero as a singular form

2009-01-08 Thread Django 
#9974: Allow pluralize filter to consider zero as a singular form
--+-
  Reporter:  david| Owner:  david
Status:  assigned | Milestone:   
 Component:  Template system  |   Version:  1.0  
Resolution:   |  Keywords:   
 Stage:  Unreviewed   | Has_patch:  0
Needs_docs:  0|   Needs_tests:  0
Needs_better_patch:  0|  
--+-
Changes (by david):

  * status:  new => assigned
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 For the record, here is the thread: http://groups.google.com/group/Django-
 I18N/browse_thread/thread/465b902db0c7dea9

-- 
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] #6362: Remove blank spaces with strip when validating the data

2009-01-08 Thread Django 
#6362: Remove blank spaces with strip when validating the data
-+--
  Reporter:  marinho | Owner:  nobody   
Status:  new | Milestone:   
 Component:  Forms   |   Version:  SVN  
Resolution:  |  Keywords:  blank space strip
 Stage:  Design decision needed  | Has_patch:  1
Needs_docs:  0   |   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 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] #6362: Remove blank spaces with strip when validating the data

2009-01-08 Thread Django 
#6362: Remove blank spaces with strip when validating the data
-+--
  Reporter:  marinho | Owner:  nobody   
Status:  new | Milestone:   
 Component:  Forms   |   Version:  SVN  
Resolution:  |  Keywords:  blank space strip
 Stage:  Design decision needed  | Has_patch:  1
Needs_docs:  0   |   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 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] #2495: db.models.TextField cannot be marked unique when using mysql backend

2009-01-08 Thread Django 
#2495: db.models.TextField cannot be marked unique when using mysql backend
---+
  Reporter:  anonymous | Owner:  nobody 

Status:  new   | Milestone: 

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

Resolution:|  Keywords:  mysql 
TextField
 Stage:  Accepted  | Has_patch:  0  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  0 |  
---+
Changes (by martin):

 * cc: mar...@akoha.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-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] #373: Add support for multiple-column primary keys

2009-01-08 Thread Django 
#373: Add support for multiple-column primary keys
---+
  Reporter:  jacob | Owner:  dcramer 
Status:  assigned  | Milestone:  post-1.0
 Component:  Database layer (models, ORM)  |   Version:  
Resolution:|  Keywords:  database
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by david):

 * cc: david (added)

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

Re: [Django] #9433: File locking broken on AFP mounts

2009-01-08 Thread Django 
#9433: File locking broken on AFP mounts
---+
  Reporter:  rndblnch  | Owner:  anonymous
Status:  new   | Milestone:   
 Component:  File uploads/storage  |   Version:  1.0  
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

  * owner:  rndblnch => anonymous

-- 
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] #6845: Model validation and its propagation to ModelForms

2009-01-08 Thread Django 
#6845: Model validation and its propagation to ModelForms
-+--
  Reporter:  Honza_Kral  | Owner:  Honza_Kral   
 
Status:  new | Milestone:  post-1.0 
 
 Component:  Forms   |   Version:  SVN  
 
Resolution:  |  Keywords:  newforms validation model 
modelform ep2008
 Stage:  Accepted| Has_patch:  1
 
Needs_docs:  1   |   Needs_tests:  1
 
Needs_better_patch:  1   |  
-+--
Changes (by Honza_Kral):

  * owner:  nobody => Honza_Kral

Comment:

 I will post my commits here:
 http://github.com/HonzaKral/django/tree/master

 After this weekend I hope to have a lot of tasks for anybody willing to
 help, now I have to update the base of the code to match current state of
 django.

 If you have time now, you can definitely start working on validators (not
 glamorous task, I agree, but it needs to be done) so that we can later
 integrate them.

 @carlopires: I am working on new code, but the main thing I am doing now
 is cleaning and updating the last patch to trunk, will push to github as
 soon as that's done.

-- 
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] #6845: Model validation and its propagation to ModelForms

2009-01-08 Thread Django 
#6845: Model validation and its propagation to ModelForms
-+--
  Reporter:  Honza_Kral  | Owner:  nobody   
 
Status:  new | Milestone:  post-1.0 
 
 Component:  Forms   |   Version:  SVN  
 
Resolution:  |  Keywords:  newforms validation model 
modelform ep2008
 Stage:  Accepted| Has_patch:  1
 
Needs_docs:  1   |   Needs_tests:  1
 
Needs_better_patch:  1   |  
-+--
Changes (by carlopires):

 * cc: carlopires (added)

Comment:

 @Honza, I didn't understand if your last code is 6845-against-9226.diff or
 you are working on new one for a few days.

-- 
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] #6845: Model validation and its propagation to ModelForms

2009-01-08 Thread Django 
#6845: Model validation and its propagation to ModelForms
-+--
  Reporter:  Honza_Kral  | Owner:  nobody   
 
Status:  new | Milestone:  post-1.0 
 
 Component:  Forms   |   Version:  SVN  
 
Resolution:  |  Keywords:  newforms validation model 
modelform ep2008
 Stage:  Accepted| Has_patch:  1
 
Needs_docs:  1   |   Needs_tests:  1
 
Needs_better_patch:  1   |  
-+--
Comment (by mrts):

 Aha, good. Do you want me to assist you? Perhaps you could fork the django
 svn clone on github yourself and publish your work so that all who are
 interested can contribute (the fork-based workflow is really nice and
 flexible)? The automatically updated django svn clone is at
 http://github.com/django/django/tree/master.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #6845: Model validation and its propagation to ModelForms

2009-01-08 Thread Django 
#6845: Model validation and its propagation to ModelForms
-+--
  Reporter:  Honza_Kral  | Owner:  nobody   
 
Status:  new | Milestone:  post-1.0 
 
 Component:  Forms   |   Version:  SVN  
 
Resolution:  |  Keywords:  newforms validation model 
modelform ep2008
 Stage:  Accepted| Has_patch:  1
 
Needs_docs:  1   |   Needs_tests:  1
 
Needs_better_patch:  1   |  
-+--
Comment (by Honza_Kral):

 I am the last one to say that everything is moving according to plan, but
 I AM working on this - I have set aside almost entire next week to update
 the patch and rebase it to new version of django.

 The least I would expect is that somebody would contact me directly and
 ask about the status before assuming my death. Only Malcolm did that, and
 I answered that I should have new version within a couple of days.

 btw. the version you based your wiki on is obsolete, there is a new one
 availible:

 http://groups.google.com/group/django-
 developers/browse_thread/thread/6143408977f7ad/d09c52e1fb561469

-- 
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] #9990: Management shell autocomplete breaks PYTHONSTARTUP autocomplete

2009-01-08 Thread Django 
#9990: Management shell autocomplete breaks PYTHONSTARTUP autocomplete
--+-
 Reporter:  bruno |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Core framework| Version:  SVN   
 Keywords:  management shell command  |   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 * create a PYTHONSTARTUP file setting up autocompletion with readline
  * run manage.py shell
  * neither the PYTHONSTARTUP's autocomplete nor the shell command
 default's one work

 (tested on ubuntu linux and gentoo linux with Python 2.5.x)

 The problem seems to come from the fact that the shell command install
 autocompletion _before_ executing the PYTHONSTARTUP.

 The attached patch reverse the order of operations, and check
 readline.get_completer before trying to install it's own completer.
 Worksforme, *but* requires that the PYTHONSTARTUP script pass globals() to
 the completer (else we'd be back to #5082). It also just ignore the
 use_plain flag except to tell wether to use IPython or the default
 shell(cf #5936). There's perhaps something better to do to get the whole
 thing right (perhaps passing a 'DJANGO_SHELL=1') option to execfile ???),
 but this is a design decision so I leave it to you guys.

-- 
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] #9549: Give initial_data.* files an option for not over writing current data.

2009-01-08 Thread Django 
#9549: Give initial_data.* files  an option for not over writing current data.
+---
  Reporter:  MrNarwhal  | Owner:  nobody
   
Status:  reopened   | Milestone:
   
 Component:  Serialization  |   Version:  1.0   
   
Resolution: |  Keywords:  initial data, syncdb, 
json, xml, yaml
 Stage:  Accepted   | Has_patch:  1 
   
Needs_docs:  1  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Changes (by mtredinnick):

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

Comment:

 @uptimebox: the ticket is closed or fixed yet. That happens if/when the
 patch is committed. Reopening.

-- 
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] #9549: Give initial_data.* files an option for not over writing current data.

2009-01-08 Thread Django 
#9549: Give initial_data.* files  an option for not over writing current data.
+---
  Reporter:  MrNarwhal  | Owner:  nobody
   
Status:  closed | Milestone:
   
 Component:  Serialization  |   Version:  1.0   
   
Resolution:  fixed  |  Keywords:  initial data, syncdb, 
json, xml, yaml
 Stage:  Accepted   | Has_patch:  1 
   
Needs_docs:  1  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Changes (by uptimebox):

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

Comment:

 I don't think efficient implementation is so important in this case. This
 operation only used from time to time by administrator, so it has no real
 impact in production environment. I belive simplicity of implementation is
 much more important 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 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] #9569: [l10n][zh_CN] fix translation in django.po (revision 9264)

2009-01-08 Thread Django 
#9569: [l10n][zh_CN] fix translation in django.po (revision 9264)
---+
  Reporter:  isoem...@163.com  | Owner:  nobody
Status:  closed| Milestone:
 Component:  Translations  |   Version:  SVN   
Resolution:  fixed |  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by mtredinnick):

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

Comment:

 Fixed in r9722.

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

[Changeset] r9722 - django/trunk/django/conf/locale/zh_CN/LC_MESSAGES

2009-01-08 Thread noreply 

Author: mtredinnick
Date: 2009-01-08 04:33:36 -0600 (Thu, 08 Jan 2009)
New Revision: 9722

Modified:
   django/trunk/django/conf/locale/zh_CN/LC_MESSAGES/django.mo
   django/trunk/django/conf/locale/zh_CN/LC_MESSAGES/django.po
Log:
Fixed #9569 -- Small correction to Simplified Chinese translation.
Thanks, isoem...@163.com and neom...@gmail.com for the confirmation.

Modified: django/trunk/django/conf/locale/zh_CN/LC_MESSAGES/django.mo
===
(Binary files differ)

Modified: django/trunk/django/conf/locale/zh_CN/LC_MESSAGES/django.po
===
--- django/trunk/django/conf/locale/zh_CN/LC_MESSAGES/django.po 2009-01-08 
10:32:55 UTC (rev 9721)
+++ django/trunk/django/conf/locale/zh_CN/LC_MESSAGES/django.po 2009-01-08 
10:33:36 UTC (rev 9722)
@@ -821,7 +821,7 @@
 
 #: contrib/admin/templates/registration/password_reset_complete.html:12
 msgid "Your password has been set.  You may go ahead and log in now."
-msgstr "你的密码尚未设置。现在你可以继续进行登录。"
+msgstr "你的口令己经设置。现在你可以继续进行登录。"
 
 #: contrib/admin/templates/registration/password_reset_confirm.html:4
 msgid "Password reset confirmation"


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

[Changeset] r9720 - django/branches/releases/1.0.X/django/conf/locale/ja/LC_MESSAGES

2009-01-08 Thread noreply 

Author: mtredinnick
Date: 2009-01-08 04:20:58 -0600 (Thu, 08 Jan 2009)
New Revision: 9720

Modified:
   django/branches/releases/1.0.X/django/conf/locale/ja/LC_MESSAGES/django.mo
   django/branches/releases/1.0.X/django/conf/locale/ja/LC_MESSAGES/django.po
   django/branches/releases/1.0.X/django/conf/locale/ja/LC_MESSAGES/djangojs.mo
   django/branches/releases/1.0.X/django/conf/locale/ja/LC_MESSAGES/djangojs.po
Log:
[1.0.X] Fixed #9888 -- Updated Japanese translation from Takashi Matsuo.

Modified: 
django/branches/releases/1.0.X/django/conf/locale/ja/LC_MESSAGES/django.mo
===
(Binary files differ)

Modified: 
django/branches/releases/1.0.X/django/conf/locale/ja/LC_MESSAGES/django.po
===
--- django/branches/releases/1.0.X/django/conf/locale/ja/LC_MESSAGES/django.po  
2009-01-08 10:12:48 UTC (rev 9719)
+++ django/branches/releases/1.0.X/django/conf/locale/ja/LC_MESSAGES/django.po  
2009-01-08 10:20:58 UTC (rev 9720)
@@ -3,8 +3,8 @@
 msgstr ""
 "Project-Id-Version: Django\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2008-09-03 10:01+0900\n"
-"PO-Revision-Date: 2008-09-03 10:03+0900\n"
+"POT-Creation-Date: 2008-12-19 13:45+0900\n"
+"PO-Revision-Date: 2008-12-19 13:57+0900\n"
 "Last-Translator: Takashi Matsuo \n"
 "Language-Team: Japanese \n"
 "MIME-Version: 1.0\n"
@@ -97,114 +97,122 @@
 msgstr "ヘブライ語"
 
 #: conf/global_settings.py:65
+msgid "Hindi"
+msgstr "ヒンディー語"
+
+#: conf/global_settings.py:66
 msgid "Croatian"
 msgstr "クロアチア語"
 
-#: conf/global_settings.py:66
+#: conf/global_settings.py:67
 msgid "Icelandic"
 msgstr "アイスランド語"
 
-#: conf/global_settings.py:67
+#: conf/global_settings.py:68
 msgid "Italian"
 msgstr "イタリア語"
 
-#: conf/global_settings.py:68
+#: conf/global_settings.py:69
 msgid "Japanese"
 msgstr "日本語"
 
-#: conf/global_settings.py:69
+#: conf/global_settings.py:70
 msgid "Georgian"
 msgstr "グルジア語"
 
-#: conf/global_settings.py:70
+#: conf/global_settings.py:71
 msgid "Korean"
 msgstr "韓国語"
 
-#: conf/global_settings.py:71
+#: conf/global_settings.py:72
 msgid "Khmer"
 msgstr "クメール語"
 
-#: conf/global_settings.py:72
+#: conf/global_settings.py:73
 msgid "Kannada"
 msgstr "カンナダ語"
 
-#: conf/global_settings.py:73
+#: conf/global_settings.py:74
 msgid "Latvian"
 msgstr "ラトビア語"
 
-#: conf/global_settings.py:74
+#: conf/global_settings.py:75
 msgid "Lithuanian"
 msgstr "リトアニア語"
 
-#: conf/global_settings.py:75
+#: conf/global_settings.py:76
 msgid "Macedonian"
 msgstr "マケドニア語"
 
-#: conf/global_settings.py:76
+#: conf/global_settings.py:77
 msgid "Dutch"
 msgstr "オランダ語"
 
-#: conf/global_settings.py:77
+#: conf/global_settings.py:78
 msgid "Norwegian"
 msgstr "ノルウェー語"
 
-#: conf/global_settings.py:78
+#: conf/global_settings.py:79
 msgid "Polish"
 msgstr "ポーランド語"
 
-#: conf/global_settings.py:79
-msgid "Portugese"
+#: conf/global_settings.py:80
+msgid "Portuguese"
 msgstr "ポルトガル語"
 
-#: conf/global_settings.py:80
+#: conf/global_settings.py:81
 msgid "Brazilian Portuguese"
 msgstr "ブラジルポルトガル語"
 
-#: conf/global_settings.py:81
+#: conf/global_settings.py:82
 msgid "Romanian"
 msgstr "ルーマニア語"
 
-#: conf/global_settings.py:82
+#: conf/global_settings.py:83
 msgid "Russian"
 msgstr "ロシア語"
 
-#: conf/global_settings.py:83
+#: conf/global_settings.py:84
 msgid "Slovak"
 msgstr "スロバキア語"
 
-#: conf/global_settings.py:84
+#: conf/global_settings.py:85
 msgid "Slovenian"
 msgstr "スロヴェニア語"
 
-#: conf/global_settings.py:85
+#: conf/global_settings.py:86
 msgid "Serbian"
 msgstr "セルビア語"
 
-#: conf/global_settings.py:86
+#: conf/global_settings.py:87
 msgid "Swedish"
 msgstr "スウェーデン語"
 
-#: conf/global_settings.py:87
+#: conf/global_settings.py:88
 msgid "Tamil"
 msgstr "タミル語"
 
-#: conf/global_settings.py:88
+#: conf/global_settings.py:89
 msgid "Telugu"
 msgstr "テルグ語"
 
-#: conf/global_settings.py:89
+#: conf/global_settings.py:90
+msgid "Thai"
+msgstr "タイ語"
+
+#: conf/global_settings.py:91
 msgid "Turkish"
 msgstr "トルコ語"
 
-#: conf/global_settings.py:90
+#: conf/global_settings.py:92
 msgid "Ukrainian"
 msgstr "ウクライナ語"
 
-#: conf/global_settings.py:91
+#: conf/global_settings.py:93
 msgid "Simplified Chinese"
 msgstr "簡体字中国語"
 
-#: conf/global_settings.py:92
+#: conf/global_settings.py:94
 msgid "Traditional Chinese"
 msgstr "繁体字中国語"
 
@@ -217,40 +225,40 @@
 "%s で絞り込む\n"
 "\n"
 
-#: contrib/admin/filterspecs.py:74 contrib/admin/filterspecs.py:92
-#: contrib/admin/filterspecs.py:147 contrib/admin/filterspecs.py:173
+#: contrib/admin/filterspecs.py:74 contrib/admin/filterspecs.py:91
+#: contrib/admin/filterspecs.py:146 contrib/admin/filterspecs.py:172
 msgid "All"
 msgstr "全て"
 
-#: contrib/admin/filterspecs.py:113
+#: contrib/admin/filterspecs.py:112
 msgid "Any date"
 msgstr "いつでも"
 
-#: contrib/admin/filterspecs.py:114
+#: contrib/admin/filterspecs.py:113
 msgid "Today"
 msgstr "今日"
 
-#:

[Changeset] r9719 - django/trunk/django/conf/locale/ja/LC_MESSAGES

2009-01-08 Thread noreply 

Author: mtredinnick
Date: 2009-01-08 04:12:48 -0600 (Thu, 08 Jan 2009)
New Revision: 9719

Modified:
   django/trunk/django/conf/locale/ja/LC_MESSAGES/django.mo
   django/trunk/django/conf/locale/ja/LC_MESSAGES/django.po
   django/trunk/django/conf/locale/ja/LC_MESSAGES/djangojs.mo
   django/trunk/django/conf/locale/ja/LC_MESSAGES/djangojs.po
Log:
Fixed #9888 -- Updated Japanese translation from Takashi Matsuo.

Modified: django/trunk/django/conf/locale/ja/LC_MESSAGES/django.mo
===
(Binary files differ)

Modified: django/trunk/django/conf/locale/ja/LC_MESSAGES/django.po
===
--- django/trunk/django/conf/locale/ja/LC_MESSAGES/django.po2009-01-08 
05:51:15 UTC (rev 9718)
+++ django/trunk/django/conf/locale/ja/LC_MESSAGES/django.po2009-01-08 
10:12:48 UTC (rev 9719)
@@ -3,8 +3,8 @@
 msgstr ""
 "Project-Id-Version: Django\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2008-09-03 10:01+0900\n"
-"PO-Revision-Date: 2008-09-03 10:03+0900\n"
+"POT-Creation-Date: 2008-12-19 12:05+0900\n"
+"PO-Revision-Date: 2008-12-19 12:26+0900\n"
 "Last-Translator: Takashi Matsuo \n"
 "Language-Team: Japanese \n"
 "MIME-Version: 1.0\n"
@@ -97,114 +97,122 @@
 msgstr "ヘブライ語"
 
 #: conf/global_settings.py:65
+msgid "Hindi"
+msgstr "ヒンディー語"
+
+#: conf/global_settings.py:66
 msgid "Croatian"
 msgstr "クロアチア語"
 
-#: conf/global_settings.py:66
+#: conf/global_settings.py:67
 msgid "Icelandic"
 msgstr "アイスランド語"
 
-#: conf/global_settings.py:67
+#: conf/global_settings.py:68
 msgid "Italian"
 msgstr "イタリア語"
 
-#: conf/global_settings.py:68
+#: conf/global_settings.py:69
 msgid "Japanese"
 msgstr "日本語"
 
-#: conf/global_settings.py:69
+#: conf/global_settings.py:70
 msgid "Georgian"
 msgstr "グルジア語"
 
-#: conf/global_settings.py:70
+#: conf/global_settings.py:71
 msgid "Korean"
 msgstr "韓国語"
 
-#: conf/global_settings.py:71
+#: conf/global_settings.py:72
 msgid "Khmer"
 msgstr "クメール語"
 
-#: conf/global_settings.py:72
+#: conf/global_settings.py:73
 msgid "Kannada"
 msgstr "カンナダ語"
 
-#: conf/global_settings.py:73
+#: conf/global_settings.py:74
 msgid "Latvian"
 msgstr "ラトビア語"
 
-#: conf/global_settings.py:74
+#: conf/global_settings.py:75
 msgid "Lithuanian"
 msgstr "リトアニア語"
 
-#: conf/global_settings.py:75
+#: conf/global_settings.py:76
 msgid "Macedonian"
 msgstr "マケドニア語"
 
-#: conf/global_settings.py:76
+#: conf/global_settings.py:77
 msgid "Dutch"
 msgstr "オランダ語"
 
-#: conf/global_settings.py:77
+#: conf/global_settings.py:78
 msgid "Norwegian"
 msgstr "ノルウェー語"
 
-#: conf/global_settings.py:78
+#: conf/global_settings.py:79
 msgid "Polish"
 msgstr "ポーランド語"
 
-#: conf/global_settings.py:79
-msgid "Portugese"
+#: conf/global_settings.py:80
+msgid "Portuguese"
 msgstr "ポルトガル語"
 
-#: conf/global_settings.py:80
+#: conf/global_settings.py:81
 msgid "Brazilian Portuguese"
 msgstr "ブラジルポルトガル語"
 
-#: conf/global_settings.py:81
+#: conf/global_settings.py:82
 msgid "Romanian"
 msgstr "ルーマニア語"
 
-#: conf/global_settings.py:82
+#: conf/global_settings.py:83
 msgid "Russian"
 msgstr "ロシア語"
 
-#: conf/global_settings.py:83
+#: conf/global_settings.py:84
 msgid "Slovak"
 msgstr "スロバキア語"
 
-#: conf/global_settings.py:84
+#: conf/global_settings.py:85
 msgid "Slovenian"
 msgstr "スロヴェニア語"
 
-#: conf/global_settings.py:85
+#: conf/global_settings.py:86
 msgid "Serbian"
 msgstr "セルビア語"
 
-#: conf/global_settings.py:86
+#: conf/global_settings.py:87
 msgid "Swedish"
 msgstr "スウェーデン語"
 
-#: conf/global_settings.py:87
+#: conf/global_settings.py:88
 msgid "Tamil"
 msgstr "タミル語"
 
-#: conf/global_settings.py:88
+#: conf/global_settings.py:89
 msgid "Telugu"
 msgstr "テルグ語"
 
-#: conf/global_settings.py:89
+#: conf/global_settings.py:90
+msgid "Thai"
+msgstr "タイ語"
+
+#: conf/global_settings.py:91
 msgid "Turkish"
 msgstr "トルコ語"
 
-#: conf/global_settings.py:90
+#: conf/global_settings.py:92
 msgid "Ukrainian"
 msgstr "ウクライナ語"
 
-#: conf/global_settings.py:91
+#: conf/global_settings.py:93
 msgid "Simplified Chinese"
 msgstr "簡体字中国語"
 
-#: conf/global_settings.py:92
+#: conf/global_settings.py:94
 msgid "Traditional Chinese"
 msgstr "繁体字中国語"
 
@@ -217,40 +225,40 @@
 "%s で絞り込む\n"
 "\n"
 
-#: contrib/admin/filterspecs.py:74 contrib/admin/filterspecs.py:92
-#: contrib/admin/filterspecs.py:147 contrib/admin/filterspecs.py:173
+#: contrib/admin/filterspecs.py:74 contrib/admin/filterspecs.py:91
+#: contrib/admin/filterspecs.py:146 contrib/admin/filterspecs.py:172
 msgid "All"
 msgstr "全て"
 
-#: contrib/admin/filterspecs.py:113
+#: contrib/admin/filterspecs.py:112
 msgid "Any date"
 msgstr "いつでも"
 
-#: contrib/admin/filterspecs.py:114
+#: contrib/admin/filterspecs.py:113
 msgid "Today"
 msgstr "今日"
 
-#: contrib/admin/filterspecs.py:117
+#: contrib/admin/filterspecs.py:116
 msgid "Past 7 days"
 msgstr "過去 7 日間"
 
-#: contrib/admin/filterspecs.py:119
+#:

[Django] #9989: removal flaw in django.dispatch.Signal.disconnect

2009-01-08 Thread Django 
#9989: removal flaw in django.dispatch.Signal.disconnect
---+
 Reporter:  ferringb   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Eyeballing cleanup in signals, spotted a bit of whackyness trying to
 cleanse a list via enumerate usage; presume the author tried removing from
 the list directory (which blows up since that invalidates the listiter)
 and came up w/ this instead.  Flaw with it is that enumerate continues to
 increase the index even if you change the list under it's feet- in other
 words, you skip the item immediately following a deletion.  One reason
 list comps are usually better in this case (although dependant on # of
 items and deletions of course).

 So... that should be using list.remove and catching ValueError where it
 doesn't exist.  Quite a bit faster due to shifting comparison to cpy, and
 stopping the search after the first find.
 Clarifying the latter, a quick read of Signal.connect shows it disallows
 redundant connections to the same 'key'; meaning that the enumerate code
 in place right now is daft for continuing it's search for more to wipe-
 essentially a mismatch between connect/disconnect (guessing it crept in
 when someone tweaking signal.connect to disallow redundant registrations).

 basically convert
 {{{
 for idx, (r_key, _) in self.receivers:
  if r_key == lookup_key:
   del self.receives[idx]
 }}}
 into
 {{{
 try:
  self.receivers.remove(lookup_key)
 except ValueError:
  pass
 }}}
 'nuff said.

-- 
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] #9988: It's not possible to correctly translate the months

2009-01-08 Thread Django 
#9988: It's not possible to correctly translate the months
---+
  Reporter:  stephaner | Owner:  nobody
Status:  new   | Milestone:
 Component:  Internationalization  |   Version:  SVN   
Resolution:|  Keywords:  french
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by mtredinnick):

  * needs_better_patch:  => 0
  * component:  Translations => Internationalization
  * needs_tests:  => 0
  * needs_docs:  => 0

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

Re: [Django] #6845: Model validation and its propagation to ModelForms

2009-01-08 Thread Django 
#6845: Model validation and its propagation to ModelForms
-+--
  Reporter:  Honza_Kral  | Owner:  nobody   
 
Status:  new | Milestone:  post-1.0 
 
 Component:  Forms   |   Version:  SVN  
 
Resolution:  |  Keywords:  newforms validation model 
modelform ep2008
 Stage:  Accepted| Has_patch:  1
 
Needs_docs:  1   |   Needs_tests:  1
 
Needs_better_patch:  1   |  
-+--
Comment (by mrts):

 Arguing is not on my Favourite Pastimes List, but last update here is from
 October (followed by two requests for status updates) and the only mention
 since ages on the mailing list is a line "I'll check in with Honza and
 make sure that validation is under control" by yourself a few days ago --
 which doesn't really say much (whether it is or is not under control
 remains open). Thus, there were sufficient grounds to conclude that no
 progress has been made since the last patch.

 Anyhow, good luck, Honza, and thanks for working on this!

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

[Django] #9988: It's not possible to correctly translate the months

2009-01-08 Thread Django 
#9988: It's not possible to correctly translate the months
--+-
 Reporter:  stephaner |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Translations  | Version:  SVN   
 Keywords:  french|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 The file utils/date.py contains the following strings:
 MONTHS = {
 1:_('January'), 2:_('February'), 3:_('March'), 4:_('April'),
 5:_('May'), 6:_('June'),
 7:_('July'), 8:_('August'), 9:_('September'), 10:_('October'),
 11:_('November'),
 12:_('December')
 }

 MONTHS_AP = { # month names in Associated Press style
 1:_('Jan.'), 2:_('Feb.'), 3:_('March'), 4:_('April'), 5:_('May'),
 6:_('June'), 7:_('July'),
 8:_('Aug.'), 9:_('Sept.'), 10:_('Oct.'), 11:_('Nov.'), 12:_('Dec.')
 }

 so there is only one string for 'July' in the PO file and it's not
 possible to have a contextual translation.
 For example, in French, the first translation is 'Juillet' and the second
 one for AP is 'Juil.'.

 The solution depends on http://bugs.python.org/issue2504

-- 
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] #7584: AUTH_PROFILE_MODULE should be able to provide some default profile

2009-01-08 Thread Django 
#7584: AUTH_PROFILE_MODULE should be able to provide some default profile
+---
  Reporter:  David Danier   | 
Owner: 
Status:  closed | 
Milestone: 
 Component:  Authentication |   
Version:  SVN
Resolution:  invalid|  
Keywords: 
 Stage:  Unreviewed | 
Has_patch:  1  
Needs_docs:  0  |   
Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Comment (by guettli):

 See patch for the documentation: #9987

-- 
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] #9987: get_profile documentation: Autocreate by signal

2009-01-08 Thread Django 
#9987: get_profile documentation: Autocreate by signal
+---
 Reporter:  guettli |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Documentation   | Version:  1.0   
 Keywords:  profile signal  |   Stage:  Unreviewed
Has_patch:  1   |  
+---
 Hi,

 since a lot of users as this I wrote a small patch for the documentation.

 Related Tickets:

 #7584

-- 
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] #6845: Model validation and its propagation to ModelForms

2009-01-08 Thread Django 
#6845: Model validation and its propagation to ModelForms
-+--
  Reporter:  Honza_Kral  | Owner:  nobody   
 
Status:  new | Milestone:  post-1.0 
 
 Component:  Forms   |   Version:  SVN  
 
Resolution:  |  Keywords:  newforms validation model 
modelform ep2008
 Stage:  Accepted| Has_patch:  1
 
Needs_docs:  1   |   Needs_tests:  1
 
Needs_better_patch:  1   |  
-+--
Comment (by mtredinnick):

 Except that it has been mentioned on the mailing list multiple times (most
 recently last week when ericflo asked about it) and has been on the
 Version1.1Features page for ages. A quick glance at the producer of all
 the patches would show some evidence of Honza working on it as well.

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

Re: [Django] #6845: Model validation and its propagation to ModelForms

2009-01-08 Thread Django 
#6845: Model validation and its propagation to ModelForms
-+--
  Reporter:  Honza_Kral  | Owner:  nobody   
 
Status:  new | Milestone:  post-1.0 
 
 Component:  Forms   |   Version:  SVN  
 
Resolution:  |  Keywords:  newforms validation model 
modelform ep2008
 Stage:  Accepted| Has_patch:  1
 
Needs_docs:  1   |   Needs_tests:  1
 
Needs_better_patch:  1   |  
-+--
Comment (by mrts):

 Good to hear that Honza is working on it, but it's unfortunate that this
 wasn't mentioned neither here nor on the mailing list -- what a waste of
 my time...

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