date:20160430

Re: [Django] #26562: Introduce Storage and FileSystemStorage alternate save behaviour

2016-04-30 Thread Django

Comment (by freshquiz):

Tim, are you referring to changing the default behaviour of `Storage`?
If so, I never said to make this alternative behaviour default. I
suggested the current behaviour be kept default, but just to have this
alternative behaviour as a configurable option.

If you are saying this behaviour shouldn't exist in Django at all, I would
like justification as to why, please.

Your argument about allowing users to clobber existing files, it doesn't
make sense to me.

If you believe you need to be that protective, why does Django offer a
`delete()` method on models?
Why aren't you overly protective of existing database records?
The answer is, because it makes no sense to natively not allow the ability
for database records to be deleted.
Why should countless Django client devs have to duplicate the behaviour
themselves, just because you think they are too careless to be able to
prevent misuse?

That might be a bit of an extreme analogy, but the ability to make raw
queries in Django, is less extreme, but still a valid analogy.
Yes it has the potential to be more risky than using model queries in the
traditional way, but you still enable the clients to be able to utilise it
if they need it (albeit with a lot of warnings).
Why not the same here?

I understand your (and other core devs') reservations, but I don't agree
that they are justification for not allowing the behaviour to exist
natively, at all.

--
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.e3a849e13922da001ae9bf252a9f9def%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26440: Add check that all items in url patterns are url instances

2016-04-30 Thread Django

#26440: Add check that all items in url patterns are url instances
-+-
 Reporter:  alasdairnicol|Owner:  burhan
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Core (System |  Version:  master
  checks)|
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"eb5d7bc2f465b055f4eb54a3d238502bdddb6d7e" eb5d7bc2]:
 {{{
 #!CommitTicketReference repository=""
 revision="eb5d7bc2f465b055f4eb54a3d238502bdddb6d7e"
 Fixed #26440 -- Added a warning for non-url()s in urlpatterns.

 Thanks Burhan Khalid for the initial patch and knbk/timgraham
 for review.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.d91aa4798aa57dadd22a1ae43b1561c4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26058: Custom storage backend's not entirely decoupled from FileField

2016-04-30 Thread Django

#26058: Custom storage backend's not entirely decoupled from FileField
-+-
 Reporter:  Korijn   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  File |  Version:  1.9
  uploads/storage|
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  custom storage   | Triage Stage:  Accepted
  filefield  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"914c72be2abb1c6dd860cb9279beaa66409ae1b2" 914c72b]:
 {{{
 #!CommitTicketReference repository=""
 revision="914c72be2abb1c6dd860cb9279beaa66409ae1b2"
 Fixed #26058 -- Delegated os.path bits of FileField's filename generation
 to the Storage.
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.c24d95698d835b5b330ca6700c627179%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22822: Javascript en_* translations ignored if no en or en_us translations exist

2016-04-30 Thread Django

#22822: Javascript en_* translations ignored if no en or en_us translations 
exist
-+-
 Reporter:  pforth@… |Owner:  anonymous
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.6
  Internationalization   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

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


Comment:

 I suspect and hope [11c60b529816] will have fixed this also.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/078.0ce53ec10c6483f11df1dd750d2f9e5f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #14370: Adding support for Autocomplete in contrib.admin

2016-04-30 Thread Django

#14370: Adding support for Autocomplete in contrib.admin
-+-
 Reporter:  tyrion   |Owner:  codingjoe
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  autocomplete,| Triage Stage:  Accepted
  jquery, javascript, widgets,   |
  admin  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by timgraham):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.e996d854391be641810923af1fd0bf69%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26515: trim_joins bug with nested related models using ForeignObject

2016-04-30 Thread Django

#26515: trim_joins bug with nested related models using ForeignObject
-+-
 Reporter:  ornoone  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ForeignObject,   | Triage Stage:  Accepted
  trim_join, orm |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  1 => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.3f05f6cdee6e3c84e3c80a4352024d10%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26440: Add check that all items in url patterns are url instances

2016-04-30 Thread Django

#26440: Add check that all items in url patterns are url instances
-+-
 Reporter:  alasdairnicol|Owner:  burhan
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Core (System |  Version:  master
  checks)|
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  1 => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.b238f29f22978d0b22e8bf7d49a1dfdd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26562: Introduce Storage and FileSystemStorage alternate save behaviour

2016-04-30 Thread Django

Comment (by timgraham):

Maybe I'm misunderstanding but I don't think changing the default to
overwriting files of the same name is acceptable. Allowing untrusted users
(or even trusted users, accidentally) to clobber existing files is
dangerous.

This isn't a concern if you're using a callable `FileField.upload_to` and
generating a file name instead of using the one provided by the user, but
we can't assume that.

The use case needs a bit more explanation for me to buy into the idea of
including another `Storage` class in Django.

--
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.350cbf23a62353b1562ae7eef18c5800%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21379: class AbstractUser: validators should compile re with Unicode

2016-04-30 Thread Django

#21379: class AbstractUser: validators should compile re with Unicode
--+
 Reporter:  anonymous |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by claudep):

 The [https://groups.google.com/forum/#!topic/django-developers/MBSWXcQBP3k
 django-developers] discussion.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.082fb4b764706ae0c15b45d0eb19d1c3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26563: Overwriting files with default_storage.save()

2016-04-30 Thread Django

#26563: Overwriting files with default_storage.save()
--+--
 Reporter:  MikiSoft  |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  Core (Other)  |  Version:  1.9
 Severity:  Normal|   Resolution:  duplicate
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by aaugustin):

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


Comment:

 I believe this question is adequately covered by #26562, where possible
 implementations are being discussed.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.cd66ce0eb4698e6e28f26855d9b331dc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26562: Introduce Storage and FileSystemStorage alternate save behaviour

2016-04-30 Thread Django

#26562: Introduce Storage and FileSystemStorage alternate save behaviour
-+-
 Reporter:  freshquiz|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  File |  Version:  master
  uploads/storage|
 Severity:  Normal   |   Resolution:
 Keywords:  file FileField   | Triage Stage:  Accepted
  storage overwrite filepath |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 Ah, indeed, my proposal wouldn't solve the "change the behavior of
 Storage.get_available_name()" part of the problem.

 Perhaps we can make a backwards-incompatible change there and move the
 "try to find an available name" logic in a mixin? This would make it
 reasonably easy for projets that extend `Storage` and depend on that logic
 to keep 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.1cd5d82dd16bbc5413f26ce874b972e3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26483: Change docs.python.org links to point to Python 3

2016-04-30 Thread Django

#26483: Change docs.python.org links to point to Python 3
--+
 Reporter:  timgraham |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by SachitNayak):

 * owner:  SachitNayak =>
 * status:  assigned => new


--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.02508e77733fb178d3ab24af89176d81%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26483: Change docs.python.org links to point to Python 3

2016-04-30 Thread Django

#26483: Change docs.python.org links to point to Python 3
-+-
 Reporter:  timgraham|Owner:
 Type:   |  SachitNayak
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by SachitNayak):

 * owner:  kaifeldhoff => SachitNayak


--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.5df63d5d337fe966a66fd051bb302303%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26496: AdminEmailHandler can produce mails violating RFC2822

2016-04-30 Thread Django

#26496: AdminEmailHandler can produce mails violating RFC2822
-+---
 Reporter:  nijel|Owner:  SachitNayak
 Type:  Bug  |   Status:  assigned
Component:  Error reporting  |  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+---
Changes (by SachitNayak):

 * owner:   => SachitNayak
 * 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.1921150a0925f0c2b23be0c18e55b93f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26359: explain dual ticket tracking system

2016-04-30 Thread Django

#26359: explain dual ticket tracking system
--+
 Reporter:  beckastar |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by SachitNayak):

 * owner:  SachitNayak =>
 * status:  assigned => new


--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.3700677ecf85c8b7b73744126fe93bbb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26359: explain dual ticket tracking system

2016-04-30 Thread Django

#26359: explain dual ticket tracking system
-+-
 Reporter:  beckastar|Owner:
 Type:   |  SachitNayak
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by SachitNayak):

 * status:  new => assigned
 * owner:   => SachitNayak


--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.b41d79c4497065fdf3a0f0aa7791babd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21379: class AbstractUser: validators should compile re with Unicode

2016-04-30 Thread Django

#21379: class AbstractUser: validators should compile re with Unicode
--+
 Reporter:  anonymous |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

 * needs_better_patch:  1 => 0
 * version:  1.5 => master


Comment:

 Should be ready for review.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.74edfae4f92110af0c21044940d10d96%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26563: Overwriting files with default_storage.save()

2016-04-30 Thread Django

#26563: Overwriting files with default_storage.save()
--+
 Reporter:  MikiSoft  |  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  Core (Other)  |Version:  1.9
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 I'm using `django.core.files.storage.default_storage` function for saving
 files, but I don't see an option where I would specify that existing ones
 have to be overwritten. For now I have to write my own function for
 checking if file exists, and if it does to delete it before saving. I
 propose in the next version that I could specify the parameter for
 overwriting files so that can be done easily i.e. in one line.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.480d94585d793c64dfc0b133648015bd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26058: Custom storage backend's not entirely decoupled from FileField

2016-04-30 Thread Django

#26058: Custom storage backend's not entirely decoupled from FileField
-+-
 Reporter:  Korijn   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  File |  Version:  1.9
  uploads/storage|
 Severity:  Normal   |   Resolution:
 Keywords:  custom storage   | Triage Stage:  Accepted
  filefield  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  1 => 0


Comment:

 [https://github.com/django/django/pull/6538 Updated PR]

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.e08593529c2152b4b0094b820ade1e00%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26562: Introduce Storage and FileSystemStorage alternate save behaviour

2016-04-30 Thread Django

Comment (by freshquiz):

A "native" `OverwritingFileSystemStorage` class would be all well and good
for file-system storage backends, but then what about other kinds of
backends (e.g. key-value cloud stores like Amazon S3)?

Half of the problem (as far as I see it), would still exist in the
`Storage.get_available_name()` method.

Please refer to #26058 for another issue which relates to my concerns
about coupling `Storage` with `FileSystemStorage`.

--
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.36bc7e2788ec1647af49f81ffe123cf4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18149: Form.prefix example gives wrong separator between prefix and field name

2016-04-30 Thread Django

#18149: Form.prefix example gives wrong separator between prefix and field name
---+--
 Reporter:  matt@… |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by Claude Paroz ):

 In [changeset:"d9a00ad16bdc2d52be3e61973dd4821c3a738305" d9a00ad1]:
 {{{
 #!CommitTicketReference repository=""
 revision="d9a00ad16bdc2d52be3e61973dd4821c3a738305"
 Removed deprecated Chinese language codes for contrib apps

 Refs #18149.
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/078.ee5c48db49d7d16812aebd7d12282ed9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26562: Introduce Storage and FileSystemStorage alternate save behaviour

2016-04-30 Thread Django

#26562: Introduce Storage and FileSystemStorage alternate save behaviour
-+-
 Reporter:  freshquiz|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  File |  Version:  master
  uploads/storage|
 Severity:  Normal   |   Resolution:
 Keywords:  file FileField   | Triage Stage:  Accepted
  storage overwrite filepath |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by claudep):

 +1 from 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.dbc13f76fd5923cd6eabf834c11e6ac8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26561: SelectBox Too Slow With Thousands of Options

2016-04-30 Thread Django

#26561: SelectBox Too Slow With Thousands of Options
-+-
 Reporter:  dsanders11   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  selectbox admin  | Triage Stage:  Accepted
  many-to-many m2m   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * needs_tests:   => 0
 * 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.994cda22b8fff64993d3cdb065b5c9c8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18149: Form.prefix example gives wrong separator between prefix and field name

2016-04-30 Thread Django

#18149: Form.prefix example gives wrong separator between prefix and field name
---+--
 Reporter:  matt@… |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by Claude Paroz ):

 In [changeset:"dd73908f25bf9b5accd3f055682eed56e37a5e5e" dd73908f]:
 {{{
 #!CommitTicketReference repository=""
 revision="dd73908f25bf9b5accd3f055682eed56e37a5e5e"
 [1.9.x] Removed deprecated Chinese language codes for contrib apps

 Refs #18149.
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/078.c0434a01ef37dae66c6b742d9dee%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26562: Introduce Storage and FileSystemStorage alternate save behaviour

2016-04-30 Thread Django

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

Comment:

I don't see why a new configurability mechanism would be needed. There's
already [https://docs.djangoproject.com/en/1.9/ref/settings/#default-file-
storage DEFAULT_FILE_STORAGE] for this purpose.

Even if it's entirely doable to subclass `FileSystemStorage` to implement
this behavior and configure it in DEFAULT_FILE_STORAGE, I think Django
could provide such a storage backend natively e.g. as
`django.core.files.storage.OverwritingFileSystemStorage`. (Better names
welcome.)

`OverwritingFileSystemStorage` would likely be a superclass of
`FileSystemStorage` because it has fewer features.

I'm accepting the ticket but I'd like another core dev to confirm before
we move forwards with 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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.3a8db5a4695f681cef5a66dc738b1971%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26559: Way to specify length in IntegerField

2016-04-30 Thread Django

#26559: Way to specify length in IntegerField
-+-
 Reporter:  monusurana   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * status:  new => closed
 * component:  Uncategorized => Database layer (models, ORM)
 * resolution:   => needsinfo


--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.938ccd465f880cfc51851c62432a4c46%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26341: Weird comments in PO files (.html.py filenames)

2016-04-30 Thread Django

#26341: Weird comments in PO files (.html.py filenames)
-+-
 Reporter:  sylvain-garancher|Owner:  veranika-
 |  sab
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.9
  Internationalization   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"004fa09d5b2f4dac45d4b3f43a1157007382d7b3" 004fa09d]:
 {{{
 #!CommitTicketReference repository=""
 revision="004fa09d5b2f4dac45d4b3f43a1157007382d7b3"
 [1.9.x] Fixed source path in contrib.admin translation catalog

 Refs #26341.
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/075.66b862f18c24ade519a79bbaa0c066b5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26341: Weird comments in PO files (.html.py filenames)

2016-04-30 Thread Django

#26341: Weird comments in PO files (.html.py filenames)
-+-
 Reporter:  sylvain-garancher|Owner:  veranika-
 |  sab
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.9
  Internationalization   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"b0068af5ffc279c281eca3ee078585076e1c7328" b0068af]:
 {{{
 #!CommitTicketReference repository=""
 revision="b0068af5ffc279c281eca3ee078585076e1c7328"
 Fixed source path in contrib.admin translation catalog

 Refs #26341.
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/075.b126ba5ee19a7a5ba590106ab63afbf9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26341: Weird comments in PO files (.html.py filenames)

2016-04-30 Thread Django

#26341: Weird comments in PO files (.html.py filenames)
-+-
 Reporter:  sylvain-garancher|Owner:  veranika-
 |  sab
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.9
  Internationalization   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"4a6bdff43047acbf8743ad8b332e37e529898c27" 4a6bdff4]:
 {{{
 #!CommitTicketReference repository=""
 revision="4a6bdff43047acbf8743ad8b332e37e529898c27"
 [1.9.x] Fixed #26341 -- Fixed makemessages breaking location comments for
 HTML files

 Thanks Sylvain Garancher for the report and Veranika Sabiashchanskaya for
 the
 initial patch.
 Backport of b16b124996 from 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/075.c83a4d3b315ad9e684f835e83368ae66%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17375: 'makemessages' ignores plural from 'blocktrans'

2016-04-30 Thread Django

#17375: 'makemessages' ignores plural from 'blocktrans'
-+-
 Reporter:  ahagenbruch  |Owner:
 |  sergeykolosov
 Type:  Bug  |   Status:  closed
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"185f90c45f4398f186ee9dffe1c9bd7392a47686" 185f90c]:
 {{{
 #!CommitTicketReference repository=""
 revision="185f90c45f4398f186ee9dffe1c9bd7392a47686"
 Adapted _assertPoLocComment for multi-file source lines in po files

 Refs #17375.
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.6589531b947cd812adf3464d411e9eb2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26341: Weird comments in PO files (.html.py filenames)

2016-04-30 Thread Django

#26341: Weird comments in PO files (.html.py filenames)
-+-
 Reporter:  sylvain-garancher|Owner:  veranika-
 |  sab
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.9
  Internationalization   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"b16b124996b8f5c1f922cec688d32553b8ab94b8" b16b1249]:
 {{{
 #!CommitTicketReference repository=""
 revision="b16b124996b8f5c1f922cec688d32553b8ab94b8"
 Fixed #26341 -- Fixed makemessages breaking location comments for HTML
 files

 Thanks Sylvain Garancher for the report and Veranika Sabiashchanskaya for
 the
 initial 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/075.86a489fd7a0565c82e45e2c9034c5aab%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26562: Introduce Storage and FileSystemStorage alternate save behaviour

2016-04-30 Thread Django

#26562: Introduce Storage and FileSystemStorage alternate save behaviour
-+-
 Reporter:  freshquiz|  Owner:  nobody
 Type:  New feature  | Status:  new
Component:  File |Version:  master
  uploads/storage|   Keywords:  file FileField storage
 Severity:  Normal   |  overwrite filepath
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 I have read through many discussions about justifying why uploaded files
 should not be deleted or overwritten, but I don't agree with them at all
 (I can get into that if needed) and I think the current implementation of
 `django.core.files.storage.Storage.get_available_name()` and
 `django.core.files.storage.FileSystemStorage._save()` are quite
 undesirable.

 The behaviour I am referring to is the fact that the
 `Storage.get_available_name()` method is so crucial to the whole storage
 and `FileField` game and yet its implementation is susceptible to race
 conditions and that it is the root cause of a dev not being granted total
 control of the '''final''' file/storage path when saving a file using the
 storage API.

 Flow on from that, the fact that the `FileSystemStorage._save()` method
 infinitely loops until a file path collision does not occur (to open a
 file) and then uses low-level locking mechanisms to try and retain
 ownership of the file for writing.

 If the core devs are keen on retaining this behaviour, so be it.
 However, can we please build upon Django's reputation of configurability
 and allow for an alternative (and non-default, to appease backwards
 compatibility) behaviour where `Storage.get_available_name()` effectively
 does nothing (except maybe length truncation) and
 `FileSystemStorage._save()` does not have the infinite loop and does not
 have the low-level file lock.

 My proposals for configurability are:
 * Global setting in the settings file
 * Static attribute of the `Storage` class, which can be overridden

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.0aa2b123f0ceeb25ca1f9b1f1626f777%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26562: Introduce Storage and FileSystemStorage alternate save behaviour

Re: [Django] #26440: Add check that all items in url patterns are url instances

Re: [Django] #26058: Custom storage backend's not entirely decoupled from FileField

Re: [Django] #22822: Javascript en_* translations ignored if no en or en_us translations exist

Re: [Django] #14370: Adding support for Autocomplete in contrib.admin

Re: [Django] #26515: trim_joins bug with nested related models using ForeignObject

Re: [Django] #26440: Add check that all items in url patterns are url instances

Re: [Django] #26562: Introduce Storage and FileSystemStorage alternate save behaviour

Re: [Django] #21379: class AbstractUser: validators should compile re with Unicode

Re: [Django] #26563: Overwriting files with default_storage.save()

Re: [Django] #26562: Introduce Storage and FileSystemStorage alternate save behaviour

Re: [Django] #26483: Change docs.python.org links to point to Python 3

Re: [Django] #26483: Change docs.python.org links to point to Python 3

Re: [Django] #26496: AdminEmailHandler can produce mails violating RFC2822

Re: [Django] #26359: explain dual ticket tracking system

Re: [Django] #26359: explain dual ticket tracking system

Re: [Django] #21379: class AbstractUser: validators should compile re with Unicode

[Django] #26563: Overwriting files with default_storage.save()

Re: [Django] #26058: Custom storage backend's not entirely decoupled from FileField

Re: [Django] #26562: Introduce Storage and FileSystemStorage alternate save behaviour

Re: [Django] #18149: Form.prefix example gives wrong separator between prefix and field name

Re: [Django] #26562: Introduce Storage and FileSystemStorage alternate save behaviour

Re: [Django] #26561: SelectBox Too Slow With Thousands of Options

Re: [Django] #18149: Form.prefix example gives wrong separator between prefix and field name

Re: [Django] #26562: Introduce Storage and FileSystemStorage alternate save behaviour

Re: [Django] #26559: Way to specify length in IntegerField

Re: [Django] #26341: Weird comments in PO files (.html.py filenames)

Re: [Django] #26341: Weird comments in PO files (.html.py filenames)

Re: [Django] #26341: Weird comments in PO files (.html.py filenames)

Re: [Django] #17375: 'makemessages' ignores plural from 'blocktrans'

Re: [Django] #26341: Weird comments in PO files (.html.py filenames)

[Django] #26562: Introduce Storage and FileSystemStorage alternate save behaviour

32 matches

Site Navigation

Mail list logo

Footer information