However, it should also be noted that those same larger applications are the
ones that are likely to run into this problem eventually, so perhaps forcing
the migration is the best path moving forward.
Interested in hearing thoughts about this.
--
Kenneth Reitz
> On Jun 9, 2017, at 3:54
My initial thought was to just have this apply to *new* Django applications, if
that's possible.
Running this migration could take quite some time on some larger apps, and
would require a non-trivial amount of time to execute.
--
Kenneth Reitz
> On Jun 9, 2017, at 3:53 PM, Tom Forbes
and I think it will save a lot of developers a lot
of pain in the long run.
Many thanks,
Kenneth Reitz
Heroku Python
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe fr
My thoughts are the same as Shai's below.
On Monday, May 29, 2017 at 4:00:09 PM UTC-4, Shai Berger wrote:
>
> If I understand things correctly, registration of new url-schemas to
> enable
> something like dj-database-url to support 3rd parties should be a trivial
> matter; just add an entry
Ah, I see what you're saying about third-party backends.
I imagine that you'd have to be able to merge a url string with a settings dict
(one overrides the other). This is how usage of that functionality is manually
provided in dj-database-url.
--
You received this message because you are
I don't think the code will be able to be re-used as much as the
idea/ux/functionality that it provides.
I can imagine any backend being able to convert from a url string with some
methods (e.g. `detect_url` (bool return) and `parse_url` (settings dict return
type).)
Perhaps the same scheme
information.
I think this change would vastly improve the usability of Django, and would be
an excellent and simple move for the project.
Many thanks for your consideration. <3
--
Kenneth Reitz
https://code.djangoproject.com/ticket/28236
--
You received this message because
Enjoy: http://guide.couchdb.org/draft/why.html
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-developers/-/vQegCKmfVvAJ.
To post to this group, send email to
