Re: [Django] #15643: Custom SQL can not be executed in any way

[Django]

#15643: Custom SQL can not be executed in any way
---+--
   Reporter:  vzima|Owner:  nobody
 Status:  closed   |Milestone:
  Component:  django-admin.py  |  Version:  SVN
 Resolution:  duplicate| Keywords:
   Triage Stage:  Unreviewed   |Has patch:  0
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+--
Changes (by russellm):

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


Comment:

 Duplicate of #3485

-- 
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] #15646: FileField's path attribute lacks 'upload_to' bit.

[Django]

#15646: FileField's path attribute lacks 'upload_to' bit.
-+-
   Reporter:  anonymous  |Owner:  nobody
 Status:  new|Milestone:
  Component: |  Version:  1.2
  Documentation  | Keywords:  storage system path
 Resolution: |  upload_to
   Triage Stage:  Accepted   |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-

Comment (by kmtracey):

 (Sorry, that was me. Somehow I can now post as anonymous where in the past
 I'd always get the rejected as potential spam message on anything as soon
 as trac logged me out.)

-- 
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] #15646: FileField's path attribute lacks 'upload_to' bit.

[Django]

#15646: FileField's path attribute lacks 'upload_to' bit.
-+-
   Reporter:  anonymous  |Owner:  nobody
 Status:  new|Milestone:
  Component: |  Version:  1.2
  Documentation  | Keywords:  storage system path
 Resolution: |  upload_to
   Triage Stage:  Accepted   |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-
Changes (by anonymous):

 * component:  File uploads/storage => Documentation
 * stage:  Unreviewed => Accepted


Comment:

 This is #10788. It was determined back then that it is not fixable in a
 reasonable fashion, so the change from previous was documented in the
 release notes:

 http://docs.djangoproject.com/en/1.1/releases/1.1/#names-of-uploaded-
 files-are-available-later

 However I don't see that we documented this anywhere in the main docs, and
 we should. (Or maybe we do, and I just can't find it...I can't seem to
 find anywhere that we actually document the path attribute of a model
 !FileField?) Accepting as a ticket against the docs.

-- 
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] #11185: Document how to customize widgets

[Django]

#11185: Document how to customize widgets
-+--
   Reporter:  bensmith   |Owner:  fadeev
 Status:  reopened   |Milestone:  1.3
  Component:  Documentation  |  Version:  1.0
 Resolution: | Keywords:  widget
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+--
Changes (by russellm):

 * status:  closed => reopened
 * has_patch:  0 => 1
 * resolution:  worksforme =>


Comment:

 @fadeev -- You only close a ticket when it has actually been committed to
 trunk. You're looking for the 'has patch' flag -- that tells other people
 that there is a patch that needs to be reviewed.

-- 
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] #15647: in_bulk() should not type check its input

[Django]

#15647: in_bulk() should not type check its input
--+---
 Reporter:  calvinspealman| Owner:  nobody
   Status:  new   | Milestone:
Component:  Database layer (models, ORM)  |   Version:  SVN
 Keywords:|  Triage Stage:  Unreviewed
Has patch:  0 |
--+---
 #12251 added additional types it will allow, but why does it typecheck at
 all? For example, I wanted to pass it a ValuesList, which had come from
 queryset.values_list('id', flat=True), but I don't just want another type
 added to the assert. Can the assert be removed entirely? it should work
 with any iterable I pass it.

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

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

Re: [Django] #15646: FileField's path attribute lacks 'upload_to' bit.

[Django]

#15646: FileField's path attribute lacks 'upload_to' bit.
-+-
   Reporter:  anonymous  |Owner:  nobody
 Status:  new|Milestone:
  Component:  File   |  Version:  1.2
  uploads/storage| Keywords:  storage system path
 Resolution: |  upload_to
   Triage Stage: |Has patch:  0
  Unreviewed |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by anonymous):

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


Comment:

 ADDENDUM:

 Saving the instance apparently constructs the right path and fills it in.
 Due to the fact, that uploaded files often need processing -- for instance
 converting them to a different file format -- I would find it most
 reasonable to change that behaviour. Please consider.

 Thank you.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #15646: FileField's path attribute lacks 'upload_to' bit.

[Django]

#15646: FileField's path attribute lacks 'upload_to' bit.
---+---
 Reporter:  anonymous  | Owner:  nobody
   Status:  new| Milestone:
Component:  File uploads/storage   |   Version:  1.2
 Keywords:  storage system path upload_to  |  Triage Stage:  Unreviewed
Has patch:  0  |
---+---
 The FileField's .path attribute misses the path given in 'upload_to'.

 Example:
 In settings.py:
 {{{
 MEDIA_ROOT = '/somewhere/'
 }}}

 In some model:
 {{{
 data = models.FileField(upload_to='files')
 }}}

 In the view that handles the file upload:
 {{{
 print data.path
 }}}

 This prints '/somewhere/filename' but if I am correct it shall print
 '/somewhere/files/filename'
 Exact Version is 1.2.5(-1) (current version in debian/wheezy)
 upload_to='files/' does not remedy this issue.
 I sincerely hope that I am not wasting your time.
 Thank you.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #15632: django-admin.py makemessages failure on ' symbol in templates comment block

[Django]

#15632: django-admin.py makemessages failure on ' symbol in templates comment 
block
+
   Reporter:  andrew@…  |Owner:  nobody
 Status:  new   |Milestone:  1.3
  Component:  Internationalization  |  Version:  SVN
 Resolution:| Keywords:  xgettext
   Triage Stage:  Accepted  |Has patch:  1
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  0 |
+

Comment (by ramiro):

 `15632-5.diff` is a further evolution of the patch we were discussing with
 Claude on IRC. I wasn't comfortable with ignoring the multi-line comments
 in templates because that means we get non-accurate line numbers `#:
 path/to/template/file.html:NN` comments in the PO files, so this patch
 also solves this. Tests were also expanded to cover some edge cases.

-- 
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] #15645: HTTP methods in urls.py

[Django]

#15645: HTTP methods in urls.py
---+---
 Reporter:  haras  | Owner:  nobody
   Status:  new| Milestone:
Component:  HTTP handling  |   Version:
 Keywords:  http urls  |  Triage Stage:  Unreviewed
Has patch:  0  |
---+---
 It would be nice to have possibility to distinguish a HTTP method in
 urls.py.
 IMHO it would be clearer and more extensible in future
 for example:

 {{{
 urlpatterns = patterns('',
   url ('POST', r'/user/(?P\d+)$', 'myapp.views.user.view1'),
   url ('GET', r'/user/(?P\d+)$', 'myapp.views.user.view2'),
   url ('DELETE', r'/user/(?P\d+)$', 'myapp.views.user.delete'),
 )
 }}}

-- 
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] #15632: django-admin.py makemessages failure on ' symbol in templates comment block

[Django]

#15632: django-admin.py makemessages failure on ' symbol in templates comment 
block
+
   Reporter:  andrew@…  |Owner:  nobody
 Status:  new   |Milestone:  1.3
  Component:  Internationalization  |  Version:  SVN
 Resolution:| Keywords:  xgettext
   Triage Stage:  Accepted  |Has patch:  1
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  0 |
+
Changes (by claudep):

 * has_patch:  0 => 1
 * 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 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15644: django.core.files.base.File enhancement / fix

[Django]

#15644: django.core.files.base.File enhancement / fix
-+--
   Reporter:  nickname123|Owner:  nobody
 Status:  new|Milestone:  1.3
  Component:  Uncategorized  |  Version:  SVN
 Resolution: | Keywords:  file
   Triage Stage:  Unreviewed |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+--
Changes (by nickname123):

 * needs_better_patch:   => 0
 * version:  1.2 => SVN
 * 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] #11185: Document how to customize widgets

[Django]

#11185: Document how to customize widgets
-+--
   Reporter:  bensmith   |Owner:  fadeev
 Status:  closed |Milestone:  1.3
  Component:  Documentation  |  Version:  1.0
 Resolution:  worksforme | Keywords:  widget
   Triage Stage:  Accepted   |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+--
Changes (by fadeev):

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


Comment:

 Reference part for the Custom Widget is done, still need to create a topic
 guide, which probably should be a separate ticket.

 Also, organized the widget.txt doc a bit - split widget classes into
 several logical groups and added section on how to add media to the
 widgets.

-- 
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] #6989: Inability to define DNS_NAME in django.core.mail results in e-mail messages being rejected or marked as spam

[Django]

#6989: Inability to define DNS_NAME in django.core.mail results in e-mail 
messages
being rejected or marked as spam
-+-
   Reporter:  Franklin   |Owner:  nobody
 Status:  new|Milestone:
  Component: |  Version:  SVN
  django.core.mail   | Keywords:  local_hostname,
 Resolution: |  DNS_NAME, CachedDnsName, smtplib,
   Triage Stage:  Accepted   |  SMTPConnection
Needs documentation:  1  |Has patch:  1
Patch needs improvement:  1  |  Needs tests:  0
-+-

Comment (by synack):

 We could force anybody needing this to subclass the SMTP EmailBackend, but
 that seems a bit excessive to me.

-- 
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] #15625: MultiValueDictKeyError exception has large performance penalty

[Django]

#15625: MultiValueDictKeyError exception has large performance penalty
--+--
   Reporter:  margieroginski  |Owner:  nobody
 Status:  new |Milestone:
  Component:  Uncategorized   |  Version:  1.2
 Resolution:  | Keywords:
   Triage Stage:  Accepted|Has patch:  0
Needs documentation:  0   |  Needs tests:  0
Patch needs improvement:  0   |
--+--
Changes (by adrian):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 This is a fair point. I would be in favor of changing the exception to
 match that of the built-in dictionary type: {{{KeyError: 'key'}}}.

-- 
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] #5763: Queryset doesn't have a "not equal" filter operator

[Django]

#5763: Queryset doesn't have a "not equal" filter operator
-+-
   Reporter:  jdetaeye   |Owner:  nobody
 Status:  reopened   |Milestone:
  Component:  Database   |  Version:  SVN
  layer (models, ORM)| Keywords:  qs-rf
 Resolution: |Has patch:  0
   Triage Stage:  Design |  Needs tests:  0
  decision needed|
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by anonymous):

 I would love to see this.  Case in point:

 {{{
 return self.filter(
 group__sites=Site.objects.get_current(),
 user=user
 ).exclude(
 group__status=GROUP_REMOVED,
 status=MEMBER_STATUS_BANNED,
 subscription=SUBSCRIPTION_NEVER
 )
 }}}

 Generates:

 {{{
SELECT ...
INNER JOIN ...
WHERE (
   "groups_group_sites"."site_id" = 1  AND
   "groups_membership"."user_id" = 17  AND NOT (
  "groups_membership"."status" = 99  AND
  "groups_group"."status" = 3  AND (
 "groups_membership"."subscription" = 0  AND
 "groups_membership"."subscription" IS NOT NULL
  )
   )
) ORDER BY "groups_membership"."status" DESC
 }}}

 Would like to see instead:

 {{{
 "groups_group_sites"."site_id" = 1  AND
 "groups_membership"."user_id" = 17  AND
 "groups_membership"."status" != 99  AND
 "groups_group"."status" != 3  AND
 "groups_membership"."subscription" != 0  AND
 "groups_membership"."subscription" IS NOT NULL
 }}}

-- 
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] #4094: databrowse calendars do not translate the month back to english resulting in an error

[Django]

#4094: databrowse calendars do not translate the month back to english resulting
in an error
-+-
   Reporter:  lawgon |Owner:  nickefford
   |Milestone:
 Status:  new|  Version:  SVN
  Component: | Keywords:  sprintsept14
  django.contrib.databrowse  |Has patch:  1
 Resolution: |  Needs tests:  0
   Triage Stage:  Accepted   |
Needs documentation:  0  |
Patch needs improvement:  1  |
-+-

Comment (by burzak):

 I updated to the latest trunk. I just aplied the same changes and the last
 patch. This is my first contribution so sorry if I make some mistake.

-- 
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] #6989: Inability to define DNS_NAME in django.core.mail results in e-mail messages being rejected or marked as spam

[Django]

#6989: Inability to define DNS_NAME in django.core.mail results in e-mail 
messages
being rejected or marked as spam
-+-
   Reporter:  Franklin   |Owner:  nobody
 Status:  new|Milestone:
  Component: |  Version:  SVN
  django.core.mail   | Keywords:  local_hostname,
 Resolution: |  DNS_NAME, CachedDnsName, smtplib,
   Triage Stage:  Accepted   |  SMTPConnection
Needs documentation:  1  |Has patch:  1
Patch needs improvement:  1  |  Needs tests:  0
-+-

Comment (by adrian):

 I'm just skimming this, but my immediate reaction is: introducing a new
 setting is a non-starter. Is there a way to accomplish what you want
 without a setting?

-- 
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] #15632: django-admin.py makemessages failure on ' symbol in templates comment block

[Django]

#15632: django-admin.py makemessages failure on ' symbol in templates comment 
block
+
   Reporter:  andrew@…  |Owner:  nobody
 Status:  new   |Milestone:  1.3
  Component:  Internationalization  |  Version:  SVN
 Resolution:| Keywords:  xgettext
   Triage Stage:  Unreviewed|Has patch:  0
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  0 |
+

Comment (by andrew@…):

 Is there any way to see content of ./templates/admin/base_site.html.py
 file? Does django any change in template before passing it to xgettext?

-- 
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] #15632: django-admin.py makemessages failure on ' symbol in templates comment block

[Django]

#15632: django-admin.py makemessages failure on ' symbol in templates comment 
block
+
   Reporter:  andrew@…  |Owner:  nobody
 Status:  new   |Milestone:  1.3
  Component:  Internationalization  |  Version:  SVN
 Resolution:| Keywords:  xgettext
   Triage Stage:  Unreviewed|Has patch:  0
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  0 |
+
Changes (by andrew@…):

 * keywords:   => xgettext


Comment:

 Same situation with gettext 0.17.

 {{{
 [grad@grad-book core]$ LANG=C xgettext --version
 xgettext (GNU gettext-tools) 0.17
 ...

 [grad@grad-book core]$ LANG=C PYTHONPATH=/home/grad/repos/django
 /home/grad/repos/django/django/bin/django-admin.py --version
 1.3 rc 1 SVN-15876
 [grad@grad-book core]$ LANG=C PYTHONPATH=/home/grad/repos/django
 /home/grad/repos/django/django/bin/django-admin.py makemessages -l ru
 processing language ru
 Error: errors happened while running xgettext on base_site.html
 ./templates/admin/base_site.html.py:15: warning: unterminated string
 ./templates/admin/base_site.html.py:16: warning: unterminated string
 ./templates/admin/base_site.html.py:21: warning: unterminated string

 [grad@grad-book core]$ LANG=C django-admin.py --version
 1.2.5
 [grad@grad-book core]$ LANG=C django-admin.py makemessages -l ru
 processing language ru
 [grad@grad-book core]$ echo $?
 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] #15636: django.contrib.staticfiles - "collectstatic" makes all files names lowercase.

[Django]

#15636: django.contrib.staticfiles - "collectstatic" makes all files names
lowercase.
-+-
   Reporter:  drakaar|Owner:  jezdez
 Status:  closed |Milestone:  1.3
  Component: |  Version:  SVN
  django.contrib.staticfiles | Keywords:
 Resolution:  needsinfo  |Has patch:  0
   Triage Stage: |  Needs tests:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by jezdez):

 * keywords:  blocker =>
 * status:  assigned => closed
 * resolution:   => needsinfo


Comment:

 What kind of deployment do you use?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #15644: django.core.files.base.File enhancement / fix

[Django]

#15644: django.core.files.base.File enhancement / fix
---+---
 Reporter:  nickname123| Owner:  nobody
   Status:  new| Milestone:  1.3
Component:  Uncategorized  |   Version:  1.2
 Keywords:  file   |  Triage Stage:  Unreviewed
Has patch:  1  |
---+---
 Hi,

 I think that django.core.files.base.File should be expanded to handle a
 wider range of file objects.  In my specific case, StringIO/cStringIO and
 tempfile.SpooledTemporaryFile objects.

 Here is a simple demonstration of where the File class breaks:
 {{{
 from tempfile import SpooledTemporaryFile
 from django.core.files import File
 f = SpooledTemporaryFile(
 max_size= 1024,# 1kb
 mode= 'w+b',# must be open in binary mode
 bufsize = -1,
 suffix  = '',
 prefix  = 'tmp',
 dir = None
 )
 f.write("hello")
 print len(File(f))
 }}}

 Here is the result (on Windows using Python2.6):
 {{{
 Traceback (most recent call last):
   File "", line 1, in 
   File "C:\...\django\core\files\base.py", line 33, in __len__
 return self.size
   File "C:\...\django\core\files\base.py", line 39, in _get_size
 elif os.path.exists(self.file.name):
   File "C:\...\lib\tempfile.py", line 559, in name
 return self._file.name
 AttributeError: 'cStringIO.StringO' object has no attribute 'name'
 }}}

 It should be noted that not only does the current implementation fail, but
 it breaks in the wrong code block because it doesn't verify that the name
 attribute is available.

 I propose that the file objects seek and tell method be used as an
 additional fallback before throwing the attribute error as follows:
 {{{
 def _get_size(self):
 if not hasattr(self, '_size'):
 if hasattr(self.file, 'size'):
 self._size = self.file.size
 elif hasattr(self.file, 'name') and
 os.path.exists(self.file.name):
 self._size = os.path.getsize(self.file.name)
 elif hasattr(self.file, 'tell') and hasattr(self.file,
 'seek'):
 pos = self.file.tell()
 self.file.seek(0,os.SEEK_END)
 self._size = self.file.tell()
 self.file.seek(pos)
 else:
 raise AttributeError("Unable to determine the
 file's size.")
 return self._size
 }}}

 My proposed patch fixes the problems mentioned above.

-- 
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] #15632: django-admin.py makemessages failure on ' symbol in templates comment block

[Django]

#15632: django-admin.py makemessages failure on ' symbol in templates comment 
block
+--
   Reporter:  andrew@…  |Owner:  nobody
 Status:  new   |Milestone:  1.3
  Component:  Internationalization  |  Version:  SVN
 Resolution:| Keywords:
   Triage Stage:  Unreviewed|Has patch:  0
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  0 |
+--

Comment (by jezdez):

 Hm, this is probably related to #14045 and #15495. Can you check with
 gettext 0.17?

-- 
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] #13577: New Polish L10N formats file

[Django]

#13577: New Polish L10N formats file
+
   Reporter:  ludwik|Owner:  lrekucki
 Status:  closed|Milestone:  1.3
  Component:  Translations  |  Version:  1.2
 Resolution:  fixed | Keywords:
   Triage Stage:  Accepted  |Has patch:  1
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  1 |
+
Changes (by jezdez):

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


Comment:

 Uh, closing, this shouldn't have been reopened in the first place because
 there was a commit already.

-- 
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] #15632: django-admin.py makemessages failure on ' symbol in templates comment block

[Django]

#15632: django-admin.py makemessages failure on ' symbol in templates comment 
block
+--
   Reporter:  andrew@…  |Owner:  nobody
 Status:  new   |Milestone:  1.3
  Component:  Internationalization  |  Version:  SVN
 Resolution:| Keywords:
   Triage Stage:  Unreviewed|Has patch:  0
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  0 |
+--

Comment (by andrew@…):

 xgettext (GNU gettext-tools) 0.18.1

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

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

Re: [Django] #15636: django.contrib.staticfiles - "collectstatic" makes all files names lowercase.

[Django]

#15636: django.contrib.staticfiles - "collectstatic" makes all files names
lowercase.
-+-
   Reporter:  drakaar|Owner:  jezdez
 Status:  assigned   |Milestone:  1.3
  Component: |  Version:  SVN
  django.contrib.staticfiles | Keywords:  blocker
 Resolution: |Has patch:  0
   Triage Stage: |  Needs tests:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by jezdez):

 This seems related to #8593.

-- 
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] #3214: [patch] raw sql file doesn't recognize quotes correctly

[Django]

#3214: [patch] raw sql file doesn't recognize quotes correctly
-+-
   Reporter:  shaunc |Owner:  nobody
|Milestone:
 Status:  reopened   |  Version:  SVN
  Component:  Database   | Keywords:  rawsql
  layer (models, ORM)|Has patch:  1
 Resolution: |  Needs tests:  1
   Triage Stage:  Accepted   |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by vzima):

 * cc: vlastimil.zima@… (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] #15643: Custom SQL can not be executed in any way

[Django]

#15643: Custom SQL can not be executed in any way
---+--
   Reporter:  vzima|Owner:  nobody
 Status:  new  |Milestone:
  Component:  django-admin.py  |  Version:  SVN
 Resolution:   | Keywords:
   Triage Stage:  Unreviewed   |Has patch:  0
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+--
Changes (by vzima):

 * needs_better_patch:   => 0
 * component:  Uncategorized => django-admin.py
 * 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.

[Django] #15643: Custom SQL can not be executed in any way

[Django]

#15643: Custom SQL can not be executed in any way
---+---
 Reporter:  vzima  | Owner:  nobody
   Status:  new| Milestone:
Component:  Uncategorized  |   Version:  SVN
 Keywords: |  Triage Stage:  Unreviewed
Has patch:  0  |
---+---
 According to documentation it should be possible to use custom SQL for
 databases. But there is no way how we can "create SQL functions, views,
 triggers, etc." as documentation says.

 When you try to use initial SQL it parses and messes what is in file
 unless it is some basic statement like INSERT. You can not really add
 trigger, because django messes your SQL by running what is between
 semicolons separately.

 When you try to use post_syncdb signal to run your custom SQL then you can
 not use flush command, because it fails on database errors that your
 triggers/functions/constraints/... already exists and it is not possible
 to write IF NOT EXISTS everywhere.


 Best solution for all is to remove the parser for custom SQL, it can not
 prevent errors anyway, we can still insert wrong values. Just let us
 upload our SQLs without messing them up and let us handle our SQL
 ourselves.

-- 
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] #15642: Dead code in http.__init__.py

[Django]

#15642: Dead code in http.__init__.py
---+---
 Reporter:  jammon | Owner:  nobody
   Status:  new| Milestone:
Component:  HTTP handling  |   Version:  SVN
 Keywords: |  Triage Stage:  Unreviewed
Has patch:  0  |
---+---
 In `http.__init__.py` the lines 329-331 read

 {{{#!python
 # *Important*: do not import settings any earlier because of
 note
 # in core.handlers.modpython.
 from django.conf import settings
 }}}
 and the same in lines 341-343. But it says `from django.conf import
 settings` already in line 124.
 Lines 329-331 have been introduced in rev. 5609, and lines 341-343 in rev.
 8460. The import in line 124 has been introduced in rev. 7814 three years
 ago.

 So I cannot tell if the lines can be deleted or if the mentioned note in
 `core.handlers.modpython` should be obeyed.

-- 
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] #15641: Allow FileSystemStorage(base_url=None) to disable url access

[Django]

#15641: Allow FileSystemStorage(base_url=None) to disable url access
-+---
 Reporter:  Harm Geerts   | Owner:  nobody
   Status:  new  | Milestone:
Component:  File uploads/storage |   Version:  SVN
 Keywords:   |  Triage Stage:  Unreviewed
Has patch:  1|
-+---
 changeset:9946 changed the behaviour of passing base_url=None to the
 FileSystemStorage contructor.
 Before the change it would disable url access whereas now it enables
 access through MEDIA_URL

 The attached patch restores the old behaviour.

-- 
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] #15634: Malformed Plural-Forms for HR locale

[Django]

#15634: Malformed Plural-Forms for HR locale
+---
   Reporter:  bmihelac  |Owner:  nobody
 Status:  closed|Milestone:  1.3
  Component:  Translations  |  Version:  SVN
 Resolution:  fixed | Keywords:  blocker
   Triage Stage:  Accepted  |Has patch:  0
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  0 |
+---
Changes (by ramiro):

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


Comment:

 Transifex team reports this also has been fixed in transifex.net. Closing.

-- 
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] #14609: __or__ method of queries does not return a correctly combined query.

[Django]

#14609: __or__ method of queries does not return a correctly combined query.
-+-
   Reporter:  melinath   |Owner:  nobody
 Status:  new|Milestone:
  Component:  Database   |  Version:  1.2
  layer (models, ORM)| Keywords:
 Resolution: |Has patch:  0
   Triage Stage:  Accepted   |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by hvdklauw):

 Ran into this problem two, tried to work around it with Q objects; still
 didn't work

 {{{
 class EntityManager(models.Manager):

 def between(self, entity1, entity2):
 """
 Returns a queryset that shows entities between the two given
 entities
 """

 result =
 
self.get_query_set().filter(related_to__to_entity=entity1).filter(related_from__from_entity=entity2)
 | \
 
self.get_query_set().filter(related_to__to_entity=entity2).filter(related_from__from_entity=entity1)
 | \
 
self.get_query_set().filter(related_from__from_entity=entity1).filter(related_from__from_entity=entity2)
 | \
 
self.get_query_set().filter(related_to__to_entity=entity1).filter(related_to__to_entity=entity2)
 return result

 def between2(self, entity1, entity2):
 from django.db.models import Q
 result = self.get_query_set().filter(
 (
 Q(
 related_to__to_entity=entity1
 ) & Q(
 related_from__from_entity=entity2
 )
 ) |
 (
 Q(
 related_to__to_entity=entity2
 ) & Q(
 related_from__from_entity=entity1
 )
 ) |
 (
 Q(
 related_from__from_entity=entity1
 ) & Q(
  related_from__from_entity=entity1
 )
 ) |
 (
 Q(
 related_to__to_entity=entity1
 ) & Q(
 related_to__to_entity=entity2
 )
 )
 )
 return result

 class Entity(models.Model):
 """
 Entity
 """
 name = models.CharField(_('naam'), max_length=250)

 objects = EntityManager()

 class Relation(models.Model):
 """
 Relation
 """
 from_entity = models.ForeignKey(Entity, related_name='related_to',
 verbose_name=_('van entiteit'))
 to_entity = models.ForeignKey(Entity, related_name='related_from',
 verbose_name=_('naar entiteit'))
 }}}

 Resulting query for between is:

 {{{

 SELECT "entities_entity"."id", "entities_entity"."name",
 "entities_entity"."entity_type_id"
 FROM "entities_entity"
 INNER JOIN "entities_relation" ON ("entities_entity"."id" =
 "entities_relation"."from_entity_id")
 INNER JOIN "entities_relation" T4 ON ("entities_entity"."id" =
 T4."to_entity_id")
 LEFT OUTER JOIN "entities_relation" T6 ON ("entities_entity"."id" =
 T6."to_entity_id")
 LEFT OUTER JOIN "entities_relation" T7 ON ("entities_entity"."id" =
 T7."from_entity_id")
 WHERE (("entities_relation"."to_entity_id" = 1  AND T4."from_entity_id" =
 3 )
 OR ("entities_relation"."to_entity_id" = 3  AND
 T4."from_entity_id" = 1 )
 OR (T4."from_entity_id" = 1  AND T6."from_entity_id" = 3 )
 OR ("entities_relation"."to_entity_id" = 1  AND T7."to_entity_id"
 = 3 ))
 }}}
 The problem are the two INNER JOINS I get the expected result when they
 are also LEFT (OUTER) JOINS


 The Q solution gives me this query:

 {{{
 SELECT "entities_entity"."id", "entities_entity"."name",
 "entities_entity"."entity_type_id"
 FROM "entities_entity"
 LEFT OUTER JOIN "entities_relation" ON ("entities_entity"."id" =
 "entities_relation"."from_entity_id")
 LEFT OUTER JOIN "entities_relation" T4 ON ("entities_entity"."id" =
 T4."to_entity_id")
 WHERE (("entities_relation"."to_entity_id" = 1  AND T4."from_entity_id" =
 3 )
 OR ("entities_relation"."to_entity_id" = 3  AND
 T4."from_entity_id" = 1 )
 OR (T4."from_entity_id" = 1  AND T4."from_entity_id" = 1 )
 OR ("entities_relation"."to_entity_id" = 1  AND
 "entities_relation"."to_entity_id" = 3 ))
 }}}
 Which gives me too many results

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

[Django] #15640: New initial digit in Spain phone numbers

[Django]

#15640: New initial digit in Spain phone numbers
+---
 Reporter:  fenikso | Owner:  nobody
   Status:  new | Milestone:
Component:  django.contrib.localflavor  |   Version:  1.3-rc1
 Keywords:  phone digit |  Triage Stage:  Unreviewed
Has patch:  0   |
+---
 In django/contrib/localflavor/es/forms.py, the '''ESPhoneNumberField'''
 class allow only phone numbers where first digit is 6, 8 or 9.
 Before ending year 2011 Spain will start to use cell numbers where first
 digit is '''7''' (in addition of actual '''6''').

-- 
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] #15632: django-admin.py makemessages failure on ' symbol in templates comment block

[Django]

#15632: django-admin.py makemessages failure on ' symbol in templates comment 
block
+--
   Reporter:  andrew@…  |Owner:  nobody
 Status:  new   |Milestone:  1.3
  Component:  Internationalization  |  Version:  SVN
 Resolution:| Keywords:
   Triage Stage:  Unreviewed|Has patch:  0
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  0 |
+--
Changes (by jezdez):

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


Comment:

 Which version of gettext do you use? Running `xgettext --version` should
 give you that info.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #6124: need a non-pickled locmem cache backend

[Django]

#6124: need a non-pickled locmem cache backend
-+-
   Reporter:  lukerl@…   |Owner:  nobody
 Status:  closed |Milestone:
  Component:  Cache  |  Version:  SVN
  system | Keywords:  cache, locmem, pickle
 Resolution:  wontfix|Has patch:  1
   Triage Stage:  Accepted   |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  1  |
-+-

Comment (by akaihola):

 Replying to [comment:4 mtredinnick]:
 > Since using external cache backends has been possible and
 straightforwards for quite a while now (before Django 1.0, from memory),
 there's no reason something like this has to be included. If anybody has a
 reason to use a particular cache implementation, they can do just that and
 reference it via a path in the settings. There's no need for it to be in
 Django.

 See [http://djangosnippets.org/snippets/2396/ django snippet #2396] for an
 implementation of a non-pickling locmem external cache backend.

-- 
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] #15636: django.contrib.staticfiles - "collectstatic" makes all files names lowercase.

[Django]

#15636: django.contrib.staticfiles - "collectstatic" makes all files names
lowercase.
-+-
   Reporter:  drakaar|Owner:  jezdez
 Status:  assigned   |Milestone:  1.3
  Component: |  Version:  SVN
  django.contrib.staticfiles | Keywords:  blocker
 Resolution: |Has patch:  0
   Triage Stage: |  Needs tests:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by jezdez):

 * owner:   => jezdez
 * 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] #15636: django.contrib.staticfiles - "collectstatic" makes all files names lowercase.

[Django]

#15636: django.contrib.staticfiles - "collectstatic" makes all files names
lowercase.
-+-
   Reporter:  drakaar|Owner:
 Status:  new|Milestone:  1.3
  Component: |  Version:  SVN
  django.contrib.staticfiles | Keywords:  blocker
 Resolution: |Has patch:  0
   Triage Stage: |  Needs tests:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by jezdez):

 * keywords:  collectstatic, lowercase => blocker
 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * milestone:   => 1.3


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