There are probably more examples throughout the codebase, but this is the
one I've run into.
--
Ticket URL: <https://code.djangoproject.com/ticket/22712>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Unfortunately, I think changing this is not going to be worth it,
backwards compatibility wise. Will leave it open for a second opinion
though.
--
Ticket URL: <https://code.djangoproject.com/ticket/22712#comment:1>
* cc: Naddiseo (added)
Comment:
Couldn't the arguments undergo the normal django deprecation cycle? For
two version accept both, but issue a warning if the builtin version is
used.
--
Ticket URL: <https://code.djangoproject.com/ticket/22712#comment:2>
* type: Uncategorized => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
The `all` kwarg is a private API, so we can change it. However, we should
check whether this is going to break popular third-party addons. (I don't
know the staticfiles landscape very well.)
--
Ticket URL: <https://code.djangoproject.com/ticket/22712#comment:3>
Old description:
> Currently the staticfiles finders' `find` function has a paramter `all`
> which is also a built-in function. Personally, I consider using built-ins
> as parameters/variables to be bad form, and would usually just rename the
> parameter in my subclasses. Unfortunately, `find` is explicitly called
> with `all=all` in `django.contrib.staticfiles.finders.find()`. So, to use
> the built in `all()` one needs to use `from __builtin__ import all as
> all_`.
>
> There are probably more examples throughout the codebase, but this is the
> one I've run into.
New description:
Currently the staticfiles finders' `find` function has a parameter `all`
which is also a built-in function. Personally, I consider using built-ins
as parameters/variables to be bad form, and would usually just rename the
parameter in my subclasses. Unfortunately, `find` is explicitly called
with `all=all` in `django.contrib.staticfiles.finders.find()`. So, to use
the built in `all()` one needs to use `from __builtin__ import all as
all_`.
There are probably more examples throughout the codebase, but this is the
one I've run into.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/22712#comment:4>