[Changeset] r9238 - django/branches/releases/1.0.X/django/contrib/gis/gdal

[noreply]

Author: jbronn
Date: 2008-10-20 23:45:55 -0500 (Mon, 20 Oct 2008)
New Revision: 9238

Modified:
   django/branches/releases/1.0.X/django/contrib/gis/gdal/geometries.py
Log:
Fixed #9361 -- thanks to Guillaume for the bug report and patch.

Backport of r9237 from trunk.


Modified: django/branches/releases/1.0.X/django/contrib/gis/gdal/geometries.py
===
--- django/branches/releases/1.0.X/django/contrib/gis/gdal/geometries.py
2008-10-21 04:32:02 UTC (rev 9237)
+++ django/branches/releases/1.0.X/django/contrib/gis/gdal/geometries.py
2008-10-21 04:45:55 UTC (rev 9238)
@@ -42,7 +42,6 @@
 import re, sys
 from binascii import a2b_hex
 from ctypes import byref, string_at, c_char_p, c_double, c_ubyte, c_void_p
-from types import UnicodeType
 
 # Getting GDAL prerequisites
 from django.contrib.gis.gdal.envelope import Envelope, OGREnvelope
@@ -82,9 +81,9 @@
 # Constructing the geometry, 
 if str_instance:
 # Checking if unicode
-if isinstance(geom_input, UnicodeType):
+if isinstance(geom_input, unicode):
 # Encoding to ASCII, WKT or HEX doesn't need any more.
-geo_input = geo_input.encode('ascii')
+geom_input = geom_input.encode('ascii')
 
 wkt_m = wkt_regex.match(geom_input)
 json_m = json_regex.match(geom_input)


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r9237 - django/trunk/django/contrib/gis/gdal

[noreply]

Author: jbronn
Date: 2008-10-20 23:32:02 -0500 (Mon, 20 Oct 2008)
New Revision: 9237

Modified:
   django/trunk/django/contrib/gis/gdal/geometries.py
Log:
Fixed #9361 -- thanks to Guillaume for the bug report and patch.


Modified: django/trunk/django/contrib/gis/gdal/geometries.py
===
--- django/trunk/django/contrib/gis/gdal/geometries.py  2008-10-18 00:02:26 UTC 
(rev 9236)
+++ django/trunk/django/contrib/gis/gdal/geometries.py  2008-10-21 04:32:02 UTC 
(rev 9237)
@@ -42,7 +42,6 @@
 import re, sys
 from binascii import a2b_hex
 from ctypes import byref, string_at, c_char_p, c_double, c_ubyte, c_void_p
-from types import UnicodeType
 
 # Getting GDAL prerequisites
 from django.contrib.gis.gdal.envelope import Envelope, OGREnvelope
@@ -82,9 +81,9 @@
 # Constructing the geometry, 
 if str_instance:
 # Checking if unicode
-if isinstance(geom_input, UnicodeType):
+if isinstance(geom_input, unicode):
 # Encoding to ASCII, WKT or HEX doesn't need any more.
-geo_input = geo_input.encode('ascii')
+geom_input = geom_input.encode('ascii')
 
 wkt_m = wkt_regex.match(geom_input)
 json_m = json_regex.match(geom_input)


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #3566: Proposal: ORM aggregation support

[Django]

#3566: Proposal: ORM aggregation support
+---
  Reporter:  Honza Král <[EMAIL PROTECTED]>  | Owner:  russellm 
   
Status:  assigned   | Milestone:
  
 Component:  Database layer (models, ORM)   |   Version:  SVN   
  
Resolution: |  Keywords:  orm 
aggregation group by
 Stage:  Someday/Maybe  | Has_patch:  1 
  
Needs_docs:  0  |   Needs_tests:  1 
  
Needs_better_patch:  1  |  
+---
Changes (by pixelcort):

 * cc: [EMAIL PROTECTED], [EMAIL PROTECTED] (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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #8557: intpoint filter for contrib.humanize

[Django]

#8557: intpoint filter for contrib.humanize
-+--
  Reporter:  drakkan | Owner:  nobody  
Status:  closed  | Milestone:  post-1.0
 Component:  Template system |   Version:  SVN 
Resolution:  duplicate   |  Keywords:  
 Stage:  Design decision needed  | Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by SmileyChris):

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

Comment:

 See #9037 (it has a patch)

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

Re: [Django] #9039: Form validation problem for model with ForeignKey having unique=True, blank=True, null=True

[Django]

#9039: Form validation problem for model with ForeignKey having
unique=True,blank=True,null=True
---+
  Reporter:  nategriswold  | Owner:  kmtracey
Status:  assigned  | Milestone:  
 Component:  Forms |   Version:  1.0 
Resolution:|  Keywords:  model-validation
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

  * owner:  nobody => kmtracey
  * status:  new => assigned
  * stage:  Unreviewed => Accepted

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

Re: [Django] #8775: Change German translation of "E-mail address" to "E-Mail Adresse"

[Django]

#8775: Change German translation of "E-mail address" to "E-Mail Adresse"
---+
  Reporter:  anonymous | Owner:  nobody
Status:  closed| Milestone:
 Component:  Translations  |   Version:  SVN   
Resolution:  invalid   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by jezdez):

 Haha, agreed :)

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9405: [patch] DatabaseOperations should track its own connection

[Django]

#9405: [patch] DatabaseOperations should track its own connection
--+-
 Reporter:  Tarken|   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.0   
 Keywords:  multiple database |   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 Other database objects (Introspection, Creation) hold their own connection
 as self.connection, I'm guessing as part of the multi-db work. I have
 patched DatabaseOperations to do the same, and updated all of the backends
 to work with this change as well.

 The patch shows revision 2, as I've begun maintaining my own local django
 repo due to some multi-db wonkiness such as this change. My repo is based
 against the releases/1.0.X/ branch, r9236.

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9404: Proxy more File methods in InMemoryUploadedFile

[Django]

#9404: Proxy more File methods in InMemoryUploadedFile
--+-
 Reporter:  magneto   |   Owner:  nobody
   Status:  new   |   Milestone:  post-1.0  
Component:  File uploads/storage  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 Simply to make the InMemoryUploadedFile file proxy functions match the
 same bits as TemporaryUploadedFile .. so they can be used interchangeably

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9403: _set_content needs to perform the same _is_string check as the Constructor

[Django]

#9403: _set_content needs to perform the same _is_string check as the 
Constructor
---+
 Reporter:  magneto|   Owner:  nobody
   Status:  new|   Milestone:  post-1.0  
Component:  Uncategorized  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 In the HttpResponse constructor one checks that the input content is a
 string or an iterator itself.

 shouldn't _set_content do the same 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 [EMAIL PROTECTED]
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

[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   |  
-+--
Changes (by hdevries):

 * cc: [EMAIL PROTECTED] (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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9402: Whitespace validates in any field that is required

[Django]

#9402: Whitespace validates in any field that is required
-+--
  Reporter:  hdevries| Owner:  nobody   
Status:  closed  | Milestone:  post-1.0 
 Component:  Core framework  |   Version:  SVN  
Resolution:  duplicate   |  Keywords:  whitespace fields
 Stage:  Unreviewed  | Has_patch:  0
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by brosner):

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

Comment:

 Duplicate of #6362.

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9402: Whitespace validates in any field that is required

[Django]

#9402: Whitespace validates in any field that is required
-+--
  Reporter:  hdevries| Owner:  nobody   
Status:  new | Milestone:  post-1.0 
 Component:  Core framework  |   Version:  SVN  
Resolution:  |  Keywords:  whitespace fields
 Stage:  Unreviewed  | Has_patch:  0
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by hdevries):

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

Comment:

 if value is None .rstrip() will raise an Error. I'm not an experienced
 Python programmer, so my bad for that ;-).

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

[Django] #9402: Whitespace validates in any field that is required

[Django]

#9402: Whitespace validates in any field that is required
---+
 Reporter:  hdevries   |   Owner:  nobody
   Status:  new|   Milestone:  post-1.0  
Component:  Core framework | Version:  SVN   
 Keywords:  whitespace fields  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 How to reproduce:
 Create a form with a !CharField that has required=True .

 Put whitespace into the field ( for example 4 spaces ).

 Submit the form. It will validate as is_valid().

 The problem lies in fields.py at line 111 ( django trunk ):
 {{{
 def clean(self, value):
 """
 Validates the given value and returns its "cleaned" value as an
 appropriate Python object.

 Raises ValidationError for any errors.
 """
 if self.required and value in EMPTY_VALUES:
 raise ValidationError(self.error_messages['required'])
 return value
 }}}

 At line 46 is the following:
 {{{
 # These values, if given to to_python(), will trigger the self.required
 check.
 EMPTY_VALUES = (None, '')
 }}}

 Problem is that any amount of whitespace will get through this check. I
 don't know how you guys think about this ( I mean, whitespace is data ;-)
 ), but filling in whitespace has pretty much the same effect as filling in
 nothing.

 Proposed fix:
 {{{
 if self.required and value.rstrip() in EMPTY_VALUES:
 }}}

 I know I should do this with a patch etc. but I don't know how to do this.
 I hope this is sufficient.

 Thanks in advance,

 Hdevries.

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9401: inlineformset_factory raise IntegrityError Exception when correct data (is_valid() method) is ok

[Django]

#9401: inlineformset_factory raise IntegrityError Exception when correct data
(is_valid() method) is ok
--+-
 Reporter:  bartosak  |   Owner:  nobody
   Status:  new   |   Milestone:  post-1.0  
Component:  Forms | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 {{{
 Exception Type: IntegrityError at /patients/new/
 Exception Value: patients_guardian.pesel may not be NULL

 Environment:

 Request Method: POST
 Request URL: http://localhost:8080/patients/new/
 Django Version: 1.0-final-SVN-8985
 Python Version: 2.5.2
 Installed Applications:
 ['django.contrib.auth',
  'django.contrib.contenttypes',
  'django.contrib.sessions',
  'django.contrib.admin',
  'viomed.epikryza',
  'viomed.patients']
 Installed Middleware:
 ('django.middleware.common.CommonMiddleware',
  'django.contrib.csrf.middleware.CsrfMiddleware',
  'django.contrib.sessions.middleware.SessionMiddleware',
  'django.contrib.auth.middleware.AuthenticationMiddleware',
  'django.middleware.doc.XViewMiddleware',
  'django.middleware.transaction.TransactionMiddleware')
 }}}
 '''POST'''
 {{{
 surname u'dshf'
 nameu'hsdfdsfh'
 guardian_set-0-peselu'564865486548'
 guardian_set-TOTAL_FORMSu'1'
 age u'324'
 guardian_set-0-relationship u'R'
 guardian_set-0-name u'hdfsg'
 guardian_set-INITIAL_FORMS  u'0'
 guardian_set-0-surname  u'hdfs'
 csrfmiddlewaretoken u'19650c559d0c0f113faba870e4b30d23'
 pesel   u'234534253452'
 }}}

 ''' Models: '''
 {{{
 class Patient(models.Model):
 pesel = models.DecimalField(verbose_name=_('PESEL'), max_digits=20,
 decimal_places=0, primary_key=True, unique=True)
 name  = models.CharField(verbose_name=_('Imie'), max_length=20)
 surname = models.CharField(verbose_name=_('Nazwisko'), max_length=20)
 age  = models.IntegerField(verbose_name=_('Wiek'))

 def __unicode__(self):
 return '[ %s ] - %s %s' % (self.pesel, self.surname, self.name);

 class Meta:
 verbose_name = _('Pacjent')
 verbose_name_plural = _('Pacjenci')
 ordering = ['pesel']

 class Guardian(models.Model):
 FAMILY_RELATIONSHIP = (('R', _('Rodzic')),
('s', _('Prawny')),
('o', _('Inne')),
   )
 patient = models.ForeignKey(Patient)
 pesel = models.DecimalField(verbose_name=_('PESEL'), max_digits=20,
 decimal_places=0 ,primary_key=True, unique=True)
 name  = models.CharField(verbose_name=_('Imie'), max_length=20)
 surname = models.CharField(verbose_name=_('Nazwisko'), max_length=20)
 relationship  = models.CharField(verbose_name=_('Pokrewienstwo'),
 max_length=1, choices=FAMILY_RELATIONSHIP)

 def __unicode__(self):
 return '[ %s ] - %s %s' % (self.pesel, self.surname, self.name);

 class Meta:
 verbose_name = _('Opiekun')
 verbose_name_plural = _('Opiekunowie')
 ordering = ['patient', 'pesel']
 }}}

 ''' Source code : '''
 {{{
 @login_required
 @transaction.commit_manually
 def new_patient_and_guardian(request):
 patient_form = modelform_factory(Patient)
 guardian_form = inlineformset_factory(Patient, Guardian, extra=1,
 max_num=1)
 patient_f=patient_form()
 guardian_f=guardian_form()

 if request.method=="POST":
 patient_f=patient_form(clone(request.POST))
 if patient_f.is_valid():
 try:
 patient = patient_f.save(commit=False)
 guardian_f=guardian_form(clone(request.POST),
 instance=patient)
 if guardian_f.is_valid():
 guardian_f.save()
 patient.save()
 transaction.commit()
 return
 HttpResponseRedirect(reverse('viomed.patients.views.patient_address_edit',
 args=[patient.pesel]))
 except Exception, e:
 transaction.rollback()
 raise e

 return render_to_response('patients/patient_form.html',
{
 'patient_f': patient_f,
 'guardian_f'  : guardian_f,
},
context_instance=RequestContext(request))
 }}}

 Exception is raised at line: '' guardian_f.save() ''

-- 
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] #9400: flock causes problems when writing to an NFS share

[Django]

#9400: flock causes problems when writing to an NFS share
---+
 Reporter:  mikeh  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Hi,

 This seems to be the same behaviour as reported in #8403, but as that
 ticket has been closed as there was a request not to reopen it, here's a
 new ticket.

 We have a media directory mounted over NFS. Our system is RHEL5.2, Python
 2.4, Django-1.0. Saving a file through the standard FileField mechanisms
 (we're not using any custom storage backends, just out of the box django
 setup stuff) results in the following :

 {{{

 File "/usr/lib64/python2.4/site-packages/mod_python/apache.py", line 299,
 in HandlerDispatch?

 result = object(req)

 File "/usr/lib/python2.4/site-packages/django/core/handlers/modpython.py",
 line 222, in handler

 return ModPythonHandler?()(req)

 File "/usr/lib/python2.4/site-packages/django/core/handlers/modpython.py",
 line 195, in call

 response = self.get_response(request)

 File "/usr/lib/python2.4/site-packages/django/core/handlers/base.py", line
 128, in get_response

 return self.handle_uncaught_exception(request, resolver, exc_info)

 File "./../apps/dave_common/init.py", line 20, in new
 File "/usr/lib/python2.4/site-packages/django/core/handlers/base.py", line
 86, in get_response

 response = callback(request, *callback_args, **callback_kwargs)

 File "/usr/lib/python2.4/site-packages/django/contrib/admin/sites.py",
 line 158, in root

 return self.model_page(request, *url.split('/', 2))

 File "/usr/lib/python2.4/site-packages/django/views/decorators/cache.py",
 line 44, in _wrapped_view_func

 response = view_func(request, *args, **kwargs)

 File "/usr/lib/python2.4/site-packages/django/contrib/admin/sites.py",
 line 177, in model_page

 return admin_obj(request, rest_of_url)

 File "/usr/lib/python2.4/site-packages/django/contrib/admin/options.py",
 line 191, in call

 return self.add_view(request)

 File "/usr/lib/python2.4/site-packages/django/db/transaction.py", line
 238, in _commit_on_success

 res = func(*args, **kw)

 File "/usr/lib/python2.4/site-packages/django/contrib/admin/options.py",
 line 492, in add_view

 new_object = self.save_form(request, form, change=False)

 File "/usr/lib/python2.4/site-packages/django/contrib/admin/options.py",
 line 370, in save_form

 return form.save(commit=False)

 File "/usr/lib/python2.4/site-packages/django/forms/models.py", line 302,
 in save

 return save_instance(self, self.instance, self._meta.fields, fail_message,
 commit)

 File "/usr/lib/python2.4/site-packages/django/forms/models.py", line 47,
 in save_instance

 f.save_form_data(instance, cleaned_data[f.name])

 File "/usr/lib/python2.4/site-packages/django/db/models/fields/files.py",
 line 192, in save_form_data

 getattr(instance, self.name).save(data.name, data, save=False)

 File "/usr/lib/python2.4/site-packages/django/db/models/fields/files.py",
 line 217, in save

 super(ImageFieldFile?, self).save(name, content, save)

 File "/usr/lib/python2.4/site-packages/django/db/models/fields/files.py",
 line 74, in save

 self._name = self.storage.save(name, content)

 File "/usr/lib/python2.4/site-packages/django/core/files/storage.py", line
 45, in save

 name = self._save(name, content)

 File "/usr/lib/python2.4/site-packages/django/core/files/storage.py", line
 159, in _save

 locks.lock(fd, locks.LOCK_EX)

 File "/usr/lib/python2.4/site-packages/django/core/files/locks.py", line
 57, in lock

 fcntl.lockf(fd(file), flags)

 IOError: [Errno 37] No locks available
 }}}

 The default with RHEL5.2 is NFSv3, and that's what we're using.

 Cheers,

 Mike

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #8775: Change German translation of "E-mail address" to "E-Mail Adresse"

[Django]

#8775: Change German translation of "E-mail address" to "E-Mail Adresse"
---+
  Reporter:  anonymous | Owner:  nobody
Status:  closed| Milestone:
 Component:  Translations  |   Version:  SVN   
Resolution:  invalid   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by kyjv):

 Whoever created that ticket, boo for you :)
 Going as far as asking to change strings to reflect a very common mistake
 in todays german is really scary.

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #6483: Support European date format for JavaScript

[Django]

#6483: Support European date format for JavaScript
-+--
  Reporter:  Bastian Kleineidam <[EMAIL PROTECTED]>  | Owner:  
garcia_marc
Status:  new | Milestone:  
post-1.0   
 Component:  Internationalization|   Version:  
SVN
Resolution:  |  Keywords:  
i18n-rf
 Stage:  Accepted| Has_patch:  
1  
Needs_docs:  0   |   Needs_tests:  
0  
Needs_better_patch:  1   |  
-+--
Comment (by G2LOQ):

 Maybe a typo error in the Regex expression:

 {{{
 #!javascript
 re: /(\d{1,2})\.(\d{1,2}).(\d{4})/
 --> re: /(\d{1,2}).(\d{1,2}).(\d{4})/
 }}}
 One extra \ character ?

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9384: en/dev/ref/forms/validation 2 typos

[Django]

#9384: en/dev/ref/forms/validation 2 typos
+---
  Reporter:  romke  | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by guettli):

 * cc: [EMAIL PROTECTED] (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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9384: en/dev/ref/forms/validation 2 typos

[Django]

#9384: en/dev/ref/forms/validation 2 typos
+---
  Reporter:  romke  | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by guettli):

  * needs_better_patch:  => 0
  * has_patch:  0 => 1
  * stage:  Unreviewed => Ready for checkin
  * 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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---