Re: Binding LiveServerTestCase bind to port 0

[charettes]

I've never personally used DJANGO_LIVE_TEST_SERVER_ADDRESS for another 
purpose than preventing port conflicts which binding to port 0 solves.

It always looked strange to me to rely on an environment variable to 
achieve this. It feels like it was done this way to avoid introducing yet 
another setting.

I suppose we could deprecate DJANGO_LIVE_TEST_SERVER_ADDRESS and use a 
LiveServerTestCase.server_thread_class = LiveServerThread attribute to 
create the thread and suggest overriding it in the deprecation warning 
message if new behavior is problematic.

Simon

Le jeudi 16 juin 2016 21:23:05 UTC-4, Tim Graham a écrit :
>
> In IRC the other day, Donald pointed out 
> https://www.dnorth.net/2012/03/17/the-port-0-trick/ and suggested that 
> Django might be able to take advantage of that technique.
>
> I put together a proof of concept that seems to work: 
> https://github.com/django/django/pull/6791
>
> I'm wondering if anyone sees any problems with this approach and if 
> there's any use case for continuing to support customizing the address 
> using the DJANGO_LIVE_TEST_SERVER_ADDRESS environment variable.
>

-- 
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/26e39c6f-74ea-4256-82a2-fe32ad3b87fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Binding LiveServerTestCase bind to port 0

[Daryl]

Wow : +8 −100 for that commit - that's a great re-factoring :)

On 17 June 2016 at 13:23, Tim Graham  wrote:

> In IRC the other day, Donald pointed out
> https://www.dnorth.net/2012/03/17/the-port-0-trick/ and suggested that
> Django might be able to take advantage of that technique.
>
> I put together a proof of concept that seems to work:
> https://github.com/django/django/pull/6791
>
> I'm wondering if anyone sees any problems with this approach and if
> there's any use case for continuing to support customizing the address
> using the DJANGO_LIVE_TEST_SERVER_ADDRESS environment variable.
>
> --
> 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/148d1019-0e5b-4078-88f0-74adc92db08e%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/CALzH9qtN2rnFVbsm9Vrox%2BMv2qi-TJrJftTrRp4gBcUYs3FLHg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Binding LiveServerTestCase bind to port 0

[Tim Graham]

In IRC the other day, Donald pointed out 
https://www.dnorth.net/2012/03/17/the-port-0-trick/ and suggested that 
Django might be able to take advantage of that technique.

I put together a proof of concept that seems to work: 
https://github.com/django/django/pull/6791

I'm wondering if anyone sees any problems with this approach and if there's 
any use case for continuing to support customizing the address using the 
DJANGO_LIVE_TEST_SERVER_ADDRESS 
environment variable.

-- 
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/148d1019-0e5b-4078-88f0-74adc92db08e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Django Sprint in Amsterdam, The Netherlands (July 2-3)

[Floris den Hengst]

Hello all, 

We're very happy to announce that a two-day Django sprint will take place on
July 2-3 in Amsterdam, Netherlands. This event is organized by the Dutch 
Django
Association in collaboration with Crunchr. Sign up and more information on:
http://www.meetup.com/dutch-django-assocation/events/231212783/.

The venue is the offices of Crunchr, who is hosting this edition. The 
sprint will
start on Saturday, July 2nd at 10:00 CET and finish on Sunday, July 3rd 
around
22:00 CET.

With the help of the Dutch Django Association and Crunchr we will have core
developers on site: Baptiste Mispelon, Erik Romijn, Florian Apolloner, 
Markus
Holtermann and (tentative) Daniele Procida. One of our main goals is to
kickstart new contributors for which we have various ideas.

If you’re unable to come to Amsterdam, you're welcome to contribute to the
sprint online. Sprinters and core developers will be available in the
#django-sprint IRC channel on FreeNode. 

We hope you can join us and help make the sprint as successful as possible! 
If
you have any further questions, don't hesitate to contact me directly. 

cheers,
Floris

-- 
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/c8eb3e9d-0d85-4bd4-b6fd-2117b22d6cb9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.