Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

[Mario Frasca]

was this rejected?
my use case is: I have a single django program, which I run in multiple 
instances, each on a different port and connecting to a different 
database.  for each instance, I have a separate `config_INSTANCE.py` file.  
the database settings fit in the `config` file, but I have to put the port 
in a batch file, or something else, outside the config file.  it feels as 
if I were doing something which isn't allowed...
I don't need to run the program on a single different port, I need 
different config files each stating a different port.

On Tuesday, 17 January 2017 02:21:46 UTC-5, Shai Berger wrote:
>
> I am -1 on adding a setting to handle a use-case that can be handled by 
> users 
> with a 6-line file: 
>
> On Monday 28 November 2016 16:05:39 Shai Berger wrote: 
> > 
> > It seems all you need in the overridden runserver is: 
> > 
> > from (...)runserver import Command as BaseCommand 
> > 
> > class Command(BaseCommand): 
> > def handle(self, *args, **options): 
> > options.setdefault('addrport', '0.0.0.0:8000') 
> > super(Command, self).handle(*args, **options) 
> > 
> > What am I missing? 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/02fd8076-a850-4455-b2ae-f065a2d8e98f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: #30646 - close_if_unusable_or_obsolete fails to close unusable connections

[Aymeric Augustin]

Hello Daniel,

In the PR you propose to ping all database connections at the beginning and at 
the end of every HTTP request. I'm positive that this will have a significant 
performance impact. It's quite common to have secondary database connections 
that are rarely used, not scaled to be pinged twice per HTTP request, and 
sometimes slow to connect to.

I understand that you solved this problem in the context of Zalando. It's 
unclear to me that your solution easily generalizes to every Django-based 
system.

Surely, a serious, concrete proposal will be seriously considered. What we're 
missing at this point is a proposal that we can discuss!

As you know, currently, Django handles disconnects optimistically. It accepts 
to return one 500 error every time a worker loses its database connection. You 
can reduce this to one 500 error every time a worker loses its database 
connection while it's processing a request (rather than waiting for the next 
request) by disabling persistent connections with CONN_MAX_AGE = 0 but the 
performance hit is likely not worth the reliability improvement. On the ticket 
you say that you're seeing "a number of requests failing with 500s on every 
failover". Is that one request per thread or several requests in the same 
thread? The latter would be a bug.

You'd like to handle disconnects pessimistically. Since middleware runs outside 
of per-view transaction handling (when ATOMIC_REQUESTS is enabled), I think you 
can do anything you need in a middleware, which is likely what you have done 
(unless you had to patch Django?) A third-party package would be a good way to 
demonstrate the feature and also to document its pros and cons.

Best regards,

-- 
Aymeric.



> On 18 Jul 2019, at 19:03, Daniel Neuhaeuser  
> wrote:
> 
> Hello,
> 
> I'd like to start a discussion about the ticket I created 
> https://code.djangoproject.com/ticket/30646 
>  that was closed as won't fix.
> 
> Essentially the ticket is about how to handle database disconnects. These can 
> happen for a variety of reasons such as network problems or failover from a 
> master to a replica. It took us quite some time until we figured out how to 
> handle this reasonably and we now do this through a combination of:
> 
> * Checking whether connection is usable (what the ticket and the associated 
> PR do)
> * Exponential backoff and retry
> * A middleware that detects database errors that are likely transient and 
> turns them into 503 with Retry-After in situations where retrying would 
> introduce unreasonably high latency
> 
> Given that Django aims to be a full-stack framework for "perfectionists with 
> deadlines", I think this is complexity that should move into the framework. 
> At the very least it should be seriously considered.
> 
> SQLAlchemy, while not addressing the problem fully, covers this problem in 
> detail in their documentation 
> https://docs.sqlalchemy.org/en/13/core/pooling.html#dealing-with-disconnects 
> .
>  The "pre ping" approach mentioned there would correspond to what I've 
> proposed in the ticket and the associated PR. 
> 
> 
> Kind regards,
> Daniel
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to django-developers+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to django-developers@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/django-developers 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-developers/cc0bd0bb-38f9-4ce3-84f5-d45c415d390c%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/C65D803B-9A3E-454B-A609-8CB248C2B28C%40polytechnique.org.
For more options, visit https://groups.google.com/d/optout.

Re: Pre-proposal: adopt dj-database-url as a DEP 7 official project

[Aymeric Augustin]

Hello,

In the short term, I'm in favor of moving dj-database-url to the Django 
organization.

I have only one concern. dj-database-url supports a few third-party database 
backends: 
https://github.com/jacobian/dj-database-url/blob/004150c17e1519be408f87e0a2d16a8633cad89f/dj_database_url.py#L34-L45
 

 I wouldn't want this to be interpreted as an official recommendation about 
which backend is best for MSSQL. This isn't enough to make dj-database-url 
unsuitable as an official project but it's worth keeping in mind. Perhaps 
"mssql" should be deprecated in favor of "mssql-X", "mssql-Y" and "mssql-Z" to 
put every alternative on an equal footing?

In the long term, I agree that dj-database-url could be deprecated if Django 
gets equivalent functionality built-in. This will require a bit of creativity 
to avoid hardcoding mappings for third-party database backends. Probably users 
of third-party backends will have to add a line to register a URL scheme with a 
third-party backend.

Best regards,

-- 
Aymeric.



> On 18 Jul 2019, at 18:45, Jacob Kaplan-Moss  wrote:
> 
> Hi folks -
> 
> I’d like to gauge interest in adopting dj-database-url
> (http://github.com/jacobian/dj-database-url 
> ) as an official project
> (https://github.com/django/deps/blob/master/final/0007-official-projects.rst 
> ).
> This is my pre-proposal. I think dj-database-url is very widely-used, and
> scratches a specific but annoying itch. Maintenance burden is minimal, but
> important.
> 
> What do other folks think? DEP 7 asks us to
> 
> > solicit feedback from the community and work out if there is rough agreement
> > that the project is a good thing for Django to adopt, particularly focusing 
> > on
> > any alternative approaches to the same problem and the relative merits of 
> > them,
> > including code design, scalability, alignment with existing Django design 
> > and
> > philosophy, and having an available development and maintenance team.
> 
> So - thoughts?
> 
> I'm volunteering to be the shepherd, but do intend to form a larger team.
> 
> I've also opened https://github.com/jacobian/dj-database-url/issues/120 
> 
> as another place for this discussion. Please feel free to comment either
> place.
> 
> [Backstory, and why this is living on my github right now. @kennethreitz was
> looking for a new maintainer, and reached out to me to see if Django might be
> interested. I thought perhaps so, and offered to take over maintainership in 
> the
> meantime while we work through the DEP 7 process. If it turns out that an
> Official Project is the wrong home for this, I'll either maintain it long-term
> or transfer it again.]
> 
> Jacob
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to django-developers+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to django-developers@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/django-developers 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-developers/c4044098-d97f-44be-8859-b05cb594a7be%40Spark
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/1879FD6A-D91B-4759-8E32-E4E719BC2928%40polytechnique.org.
For more options, visit https://groups.google.com/d/optout.

Re: Pre-proposal: adopt dj-database-url as a DEP 7 official project

[Jacob Kaplan-Moss]

Puling together a few things:

On Jul 18, 2019, 3:13 PM -0400, Kevin Grinberg , 
wrote:
> I've more commonly found myself using pypi.org/project/dsnparse/ more often
> than dj-database-url, due to support for DSNs in setting CACHES (with Heroku 
> Redis
> for example, you get a REDIS_URL exposed the same way).

On Jul 18, 2019, 3:32 PM -0400, Raffaele Salmaso , wrote:
> I'm working on https://github.com/django/django/pull/10786 which is an
> "evolution" of dj-database-url which handle more settings types (by default
> even the email settings, but it is possible to handle any other type).
> I'll happy to finish it.

On Jul 18, 2019, 3:49 PM -0400, Jani Tiainen , wrote:
> Apparently there has been few attempts to integrate dj-database-url or
> some other url parser.
> But what happened to them since so far none of them were completed?

I suspect this is a "good enough is good enough" situation. Something like what
Raffaele is talking about, or dsnparse, or whatever would probably be ideal. And
for something to be merged into core, I think it'd need to be a more full
solution than just dj-database-url.

But, because dj-database-url is Good Enough, it's pretty popular, and that sucks
away some of the impetus to work on something better.

That said: were 10786 (or similar) to be merged into core, I'd think the best
thing to do wth dj-database-url would be to put it into maintenance mode, and
just fix serious issues until all of the supported version of Django have the
new thing.

I think that's somewhat unrelated to whether it becomes an official project --
just as easy to deprecate django/dj-database-url as it is to deprecate
jacobian/dj-database-url. But happy to make that an explicit caveat for
official-dom: if something better lands in core, I'd look to deprecate
and migrate.

Jacob

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/7f9457fa-9589-4cc0-a664-0b35d758927b%40Spark.
For more options, visit https://groups.google.com/d/optout.

#30646 - close_if_unusable_or_obsolete fails to close unusable connections

[Daniel Neuhaeuser]

Hello,

I'd like to start a discussion about the ticket I created 
https://code.djangoproject.com/ticket/30646 that was closed as won't fix.

Essentially the ticket is about how to handle database disconnects. These 
can happen for a variety of reasons such as network problems or failover 
from a master to a replica. It took us quite some time until we figured out 
how to handle this reasonably and we now do this through a combination of:

* Checking whether connection is usable (what the ticket and the associated 
PR do)
* Exponential backoff and retry
* A middleware that detects database errors that are likely transient and 
turns them into 503 with Retry-After in situations where retrying would 
introduce unreasonably high latency

Given that Django aims to be a full-stack framework for "perfectionists 
with deadlines", I think this is complexity that should move into the 
framework. At the very least it should be seriously considered.

SQLAlchemy, while not addressing the problem fully, covers this problem in 
detail in their documentation 
https://docs.sqlalchemy.org/en/13/core/pooling.html#dealing-with-disconnects. 
The "pre ping" approach mentioned there would correspond to what I've 
proposed in the ticket and the associated PR. 


Kind regards,
Daniel

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/cc0bd0bb-38f9-4ce3-84f5-d45c415d390c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pre-proposal: adopt dj-database-url as a DEP 7 official project

[Raffaele Salmaso]

On Thu, Jul 18, 2019 at 9:49 PM Jani Tiainen  wrote:

> But what happened to them since so far none of them were completed?
>
For my case: life :D
Anyway, I'll be happy to finish it.

-- 
| Raffaele Salmaso
| https://salmaso.org
| https://bitbucket.org/rsalmaso
| https://github.com/rsalmaso

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CABgH4Ju%2BRBcGx%2BadqnH%2BdRKSMf%2BRD7G96Xi7F_52Pq7yA-fJ_Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pre-proposal: adopt dj-database-url as a DEP 7 official project

[Jani Tiainen]

Apparently there has been few attempts to integrate dj-database-url or some
other url parser.

But what happened to them since so far none of them were completed?


to 18. heinäk. 2019 klo 22.32 Raffaele Salmaso 
kirjoitti:

> Hi
> I'm working[¹] on https://github.com/django/django/pull/10786 which is an
> "evolution" of dj-database-url which handle more settings types (by default
> even the email settings, but it is possible to handle any other type).
> I'll happy to finish it.
>
> [¹] well, in my really little free time
>
> On Thu, Jul 18, 2019 at 6:45 PM Jacob Kaplan-Moss 
> wrote:
>
>> Hi folks -
>>
>> I’d like to gauge interest in adopting dj-database-url
>> (http://github.com/jacobian/dj-database-url) as an official project
>> (
>> https://github.com/django/deps/blob/master/final/0007-official-projects.rst
>> ).
>> This is my pre-proposal. I think dj-database-url is very widely-used, and
>> scratches a specific but annoying itch. Maintenance burden is minimal, but
>> important.
>>
>> What do other folks think? DEP 7 asks us to
>>
>> > solicit feedback from the community and work out if there is rough
>> agreement
>> > that the project is a good thing for Django to adopt, particularly
>> focusing on
>> > any alternative approaches to the same problem and the relative merits
>> of them,
>> > including code design, scalability, alignment with existing Django
>> design and
>> > philosophy, and having an available development and maintenance team.
>>
>> So - thoughts?
>>
>> I'm volunteering to be the shepherd, but do intend to form a larger team.
>>
>> I've also opened https://github.com/jacobian/dj-database-url/issues/120
>> as another place for this discussion. Please feel free to comment either
>> place.
>>
>> [Backstory, and why this is living on my github right now. @kennethreitz
>> was
>> looking for a new maintainer, and reached out to me to see if Django
>> might be
>> interested. I thought perhaps so, and offered to take over maintainership
>> in the
>> meantime while we work through the DEP 7 process. If it turns out that an
>> Official Project is the wrong home for this, I'll either maintain it
>> long-term
>> or transfer it again.]
>>
>> Jacob
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django developers (Contributions to Django itself)" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to django-developers+unsubscr...@googlegroups.com.
>> To post to this group, send email to django-developers@googlegroups.com.
>> Visit this group at https://groups.google.com/group/django-developers.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-developers/c4044098-d97f-44be-8859-b05cb594a7be%40Spark
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> | Raffaele Salmaso
> | https://salmaso.org
> | https://bitbucket.org/rsalmaso
> | https://github.com/rsalmaso
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/CABgH4JvLhqgd7VPPAdaCoJ3VidZ-JaPZVbU2gMiK3_Rycxnekw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAHn91ocT86%2Bkz9dL0Rr6zKNOMXq9Ge%3Djj-%2B-bC4-jDyffbo9Sw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pre-proposal: adopt dj-database-url as a DEP 7 official project

[Raffaele Salmaso]

Hi
I'm working[¹] on https://github.com/django/django/pull/10786 which is an
"evolution" of dj-database-url which handle more settings types (by default
even the email settings, but it is possible to handle any other type).
I'll happy to finish it.

[¹] well, in my really little free time

On Thu, Jul 18, 2019 at 6:45 PM Jacob Kaplan-Moss 
wrote:

> Hi folks -
>
> I’d like to gauge interest in adopting dj-database-url
> (http://github.com/jacobian/dj-database-url) as an official project
> (
> https://github.com/django/deps/blob/master/final/0007-official-projects.rst
> ).
> This is my pre-proposal. I think dj-database-url is very widely-used, and
> scratches a specific but annoying itch. Maintenance burden is minimal, but
> important.
>
> What do other folks think? DEP 7 asks us to
>
> > solicit feedback from the community and work out if there is rough
> agreement
> > that the project is a good thing for Django to adopt, particularly
> focusing on
> > any alternative approaches to the same problem and the relative merits
> of them,
> > including code design, scalability, alignment with existing Django
> design and
> > philosophy, and having an available development and maintenance team.
>
> So - thoughts?
>
> I'm volunteering to be the shepherd, but do intend to form a larger team.
>
> I've also opened https://github.com/jacobian/dj-database-url/issues/120
> as another place for this discussion. Please feel free to comment either
> place.
>
> [Backstory, and why this is living on my github right now. @kennethreitz
> was
> looking for a new maintainer, and reached out to me to see if Django might
> be
> interested. I thought perhaps so, and offered to take over maintainership
> in the
> meantime while we work through the DEP 7 process. If it turns out that an
> Official Project is the wrong home for this, I'll either maintain it
> long-term
> or transfer it again.]
>
> Jacob
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/c4044098-d97f-44be-8859-b05cb594a7be%40Spark
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
| Raffaele Salmaso
| https://salmaso.org
| https://bitbucket.org/rsalmaso
| https://github.com/rsalmaso

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CABgH4JvLhqgd7VPPAdaCoJ3VidZ-JaPZVbU2gMiK3_Rycxnekw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pre-proposal: adopt dj-database-url as a DEP 7 official project

[Mariusz Felisiak]

See a ticket [1] and previous discussion [2] for reference.

[1] - https://code.djangoproject.com/ticket/28236
[2] - 
https://groups.google.com/forum/#!topic/django-developers/G0TtlhH2RUE/discussion

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/b65b8875-aed0-4eb0-89dc-ceea3bccb155%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pre-proposal: adopt dj-database-url as a DEP 7 official project

[Kevin Grinberg]

I've more commonly found myself using https://pypi.org/project/dsnparse/ more 
often than dj-database-url, due to support for DSNs in setting CACHES (with 
Heroku Redis for example, you get a REDIS_URL exposed the same way).

I don't think the maintainer is offering to do take dsnparse under DEP 7, 
so "blessed dj-database-url" may be better than the status quo, but I worry 
if blessing a partial solution is liable to send some folks down a 
less-than-ideal path (I'm imagining a new user finding dj-database-url as 
then "official" solution, and then getting stuck trying to wrestle with it 
to do "almost the same thing" with configuring CACHES).

That's not to say that dj-database-url couldn't grow into a more generic 
DSN parser, and maybe that's the plan - in which case, enthuastically +1! 
But AFAICT the diffs are not altogether trivial, and I'm not presently able 
to volunteer to do it, so I'm working on the assumption that 
dj-database-url retains more or less its present scope.

Kevin


On Thursday, July 18, 2019 at 12:46:13 PM UTC-4, Jacob Kaplan-Moss wrote:
>
> Hi folks -
>
> I’d like to gauge interest in adopting dj-database-url
> (http://github.com/jacobian/dj-database-url) as an official project
> (
> https://github.com/django/deps/blob/master/final/0007-official-projects.rst
> ).
> This is my pre-proposal. I think dj-database-url is very widely-used, and
> scratches a specific but annoying itch. Maintenance burden is minimal, but
> important.
>
> What do other folks think? DEP 7 asks us to
>
> > solicit feedback from the community and work out if there is rough 
> agreement
> > that the project is a good thing for Django to adopt, particularly 
> focusing on
> > any alternative approaches to the same problem and the relative merits 
> of them,
> > including code design, scalability, alignment with existing Django 
> design and
> > philosophy, and having an available development and maintenance team.
>
> So - thoughts?
>
> I'm volunteering to be the shepherd, but do intend to form a larger team.
>
> I've also opened https://github.com/jacobian/dj-database-url/issues/120
> as another place for this discussion. Please feel free to comment either
> place.
>
> [Backstory, and why this is living on my github right now. @kennethreitz 
> was
> looking for a new maintainer, and reached out to me to see if Django might 
> be
> interested. I thought perhaps so, and offered to take over maintainership 
> in the
> meantime while we work through the DEP 7 process. If it turns out that an
> Official Project is the wrong home for this, I'll either maintain it 
> long-term
> or transfer it again.]
>
> Jacob
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/2d00b471-5408-460a-8b20-9520d2a04f07%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pre-proposal: adopt dj-database-url as a DEP 7 official project

[Jani Tiainen]

I'm definitely +1 too.


to 18. heinäk. 2019 klo 20.41 Adam Johnson  kirjoitti:

> +1 from me too.
>
> On Thu, 18 Jul 2019 at 17:55, Tobias McNulty 
> wrote:
>
>> I think it's a great idea.
>>
>> On Thu, Jul 18, 2019, 12:46 PM Jacob Kaplan-Moss 
>> wrote:
>>
>>> Hi folks -
>>>
>>> I’d like to gauge interest in adopting dj-database-url
>>> (http://github.com/jacobian/dj-database-url) as an official project
>>> (
>>> https://github.com/django/deps/blob/master/final/0007-official-projects.rst
>>> ).
>>> This is my pre-proposal. I think dj-database-url is very widely-used, and
>>> scratches a specific but annoying itch. Maintenance burden is minimal,
>>> but
>>> important.
>>>
>>> What do other folks think? DEP 7 asks us to
>>>
>>> > solicit feedback from the community and work out if there is rough
>>> agreement
>>> > that the project is a good thing for Django to adopt, particularly
>>> focusing on
>>> > any alternative approaches to the same problem and the relative merits
>>> of them,
>>> > including code design, scalability, alignment with existing Django
>>> design and
>>> > philosophy, and having an available development and maintenance team.
>>>
>>> So - thoughts?
>>>
>>> I'm volunteering to be the shepherd, but do intend to form a larger team.
>>>
>>> I've also opened https://github.com/jacobian/dj-database-url/issues/120
>>> as another place for this discussion. Please feel free to comment either
>>> place.
>>>
>>> [Backstory, and why this is living on my github right now. @kennethreitz
>>> was
>>> looking for a new maintainer, and reached out to me to see if Django
>>> might be
>>> interested. I thought perhaps so, and offered to take over
>>> maintainership in the
>>> meantime while we work through the DEP 7 process. If it turns out that an
>>> Official Project is the wrong home for this, I'll either maintain it
>>> long-term
>>> or transfer it again.]
>>>
>>> Jacob
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Django developers (Contributions to Django itself)" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to django-developers+unsubscr...@googlegroups.com.
>>> To post to this group, send email to django-developers@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/django-developers.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/django-developers/c4044098-d97f-44be-8859-b05cb594a7be%40Spark
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django developers (Contributions to Django itself)" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to django-developers+unsubscr...@googlegroups.com.
>> To post to this group, send email to django-developers@googlegroups.com.
>> Visit this group at https://groups.google.com/group/django-developers.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-developers/CAMGFDKRakWoQYehp_ccnhTvbQWY3a2CN2k_iob2fsL7bwv%2BRcQ%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> Adam
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/CAMyDDM3jWBjZVyFw-KmLRvuYaFO3p6KmYnF%3DoQNjTPR2NN%3D8Bg%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAHn91ofUn-wQrurR2jM772jvGVxizXzAkZjzqr6PUutvM6xrLg%40mail.gmail.com.
For more options, visit 

Re: Pre-proposal: adopt dj-database-url as a DEP 7 official project

[Adam Johnson]

+1 from me too.

On Thu, 18 Jul 2019 at 17:55, Tobias McNulty  wrote:

> I think it's a great idea.
>
> On Thu, Jul 18, 2019, 12:46 PM Jacob Kaplan-Moss 
> wrote:
>
>> Hi folks -
>>
>> I’d like to gauge interest in adopting dj-database-url
>> (http://github.com/jacobian/dj-database-url) as an official project
>> (
>> https://github.com/django/deps/blob/master/final/0007-official-projects.rst
>> ).
>> This is my pre-proposal. I think dj-database-url is very widely-used, and
>> scratches a specific but annoying itch. Maintenance burden is minimal, but
>> important.
>>
>> What do other folks think? DEP 7 asks us to
>>
>> > solicit feedback from the community and work out if there is rough
>> agreement
>> > that the project is a good thing for Django to adopt, particularly
>> focusing on
>> > any alternative approaches to the same problem and the relative merits
>> of them,
>> > including code design, scalability, alignment with existing Django
>> design and
>> > philosophy, and having an available development and maintenance team.
>>
>> So - thoughts?
>>
>> I'm volunteering to be the shepherd, but do intend to form a larger team.
>>
>> I've also opened https://github.com/jacobian/dj-database-url/issues/120
>> as another place for this discussion. Please feel free to comment either
>> place.
>>
>> [Backstory, and why this is living on my github right now. @kennethreitz
>> was
>> looking for a new maintainer, and reached out to me to see if Django
>> might be
>> interested. I thought perhaps so, and offered to take over maintainership
>> in the
>> meantime while we work through the DEP 7 process. If it turns out that an
>> Official Project is the wrong home for this, I'll either maintain it
>> long-term
>> or transfer it again.]
>>
>> Jacob
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django developers (Contributions to Django itself)" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to django-developers+unsubscr...@googlegroups.com.
>> To post to this group, send email to django-developers@googlegroups.com.
>> Visit this group at https://groups.google.com/group/django-developers.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-developers/c4044098-d97f-44be-8859-b05cb594a7be%40Spark
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/CAMGFDKRakWoQYehp_ccnhTvbQWY3a2CN2k_iob2fsL7bwv%2BRcQ%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Adam

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMyDDM3jWBjZVyFw-KmLRvuYaFO3p6KmYnF%3DoQNjTPR2NN%3D8Bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pre-proposal: adopt dj-database-url as a DEP 7 official project

[Tobias McNulty]

I think it's a great idea.

On Thu, Jul 18, 2019, 12:46 PM Jacob Kaplan-Moss  wrote:

> Hi folks -
>
> I’d like to gauge interest in adopting dj-database-url
> (http://github.com/jacobian/dj-database-url) as an official project
> (
> https://github.com/django/deps/blob/master/final/0007-official-projects.rst
> ).
> This is my pre-proposal. I think dj-database-url is very widely-used, and
> scratches a specific but annoying itch. Maintenance burden is minimal, but
> important.
>
> What do other folks think? DEP 7 asks us to
>
> > solicit feedback from the community and work out if there is rough
> agreement
> > that the project is a good thing for Django to adopt, particularly
> focusing on
> > any alternative approaches to the same problem and the relative merits
> of them,
> > including code design, scalability, alignment with existing Django
> design and
> > philosophy, and having an available development and maintenance team.
>
> So - thoughts?
>
> I'm volunteering to be the shepherd, but do intend to form a larger team.
>
> I've also opened https://github.com/jacobian/dj-database-url/issues/120
> as another place for this discussion. Please feel free to comment either
> place.
>
> [Backstory, and why this is living on my github right now. @kennethreitz
> was
> looking for a new maintainer, and reached out to me to see if Django might
> be
> interested. I thought perhaps so, and offered to take over maintainership
> in the
> meantime while we work through the DEP 7 process. If it turns out that an
> Official Project is the wrong home for this, I'll either maintain it
> long-term
> or transfer it again.]
>
> Jacob
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/c4044098-d97f-44be-8859-b05cb594a7be%40Spark
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMGFDKRakWoQYehp_ccnhTvbQWY3a2CN2k_iob2fsL7bwv%2BRcQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Pre-proposal: adopt dj-database-url as a DEP 7 official project

[Jacob Kaplan-Moss]

Hi folks -

I’d like to gauge interest in adopting dj-database-url
(http://github.com/jacobian/dj-database-url) as an official project
(https://github.com/django/deps/blob/master/final/0007-official-projects.rst).
This is my pre-proposal. I think dj-database-url is very widely-used, and
scratches a specific but annoying itch. Maintenance burden is minimal, but
important.

What do other folks think? DEP 7 asks us to

> solicit feedback from the community and work out if there is rough agreement
> that the project is a good thing for Django to adopt, particularly focusing on
> any alternative approaches to the same problem and the relative merits of 
> them,
> including code design, scalability, alignment with existing Django design and
> philosophy, and having an available development and maintenance team.

So - thoughts?

I'm volunteering to be the shepherd, but do intend to form a larger team.

I've also opened https://github.com/jacobian/dj-database-url/issues/120
as another place for this discussion. Please feel free to comment either
place.

[Backstory, and why this is living on my github right now. @kennethreitz was
looking for a new maintainer, and reached out to me to see if Django might be
interested. I thought perhaps so, and offered to take over maintainership in the
meantime while we work through the DEP 7 process. If it turns out that an
Official Project is the wrong home for this, I'll either maintain it long-term
or transfer it again.]

Jacob

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/c4044098-d97f-44be-8859-b05cb594a7be%40Spark.
For more options, visit https://groups.google.com/d/optout.