Re: Will asgi become a PEP like wsgi is ?

[James Pic]

I do not see myself using Django without Channels anymore, it's become a
basic Django feature for me and I just love it. Despite my perhaps lack of
knowledge about the protocol internals, such features seem like it would
certainly benefit the Python community and anyway I'd say it's worth a try
just to see what the python-ideas list has to say.

-- 
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/CAC6Op1-p6O4pzUHcgZEE%2Bap8ZAdkQqeaC_bSi0%3DvF8GH%2BZBc4A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Will asgi become a PEP like wsgi is ?

[James Pic]

On Mon, Mar 13, 2017 at 12:26 PM, Etienne Robillard  wrote:
> ASGI is for building platform-oriented web applications in Django.

Could you elaborate on this ? The only mention of Django I found in
the spec linked by the OT is "Django Channels ships with a no-op
consumer attached by default; we recommend other implementations do
the same", so it doesn't look really coupled with Django overall:
http://channels.readthedocs.io/en/stable/asgi.html

-- 
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/CAC6Op1_H%2BRhz-zoC_x49tYMqSQksmjdNGZwXPdLRfX4aUG0RAQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Will asgi become a PEP like wsgi is ?

[James Pic]

On Mon, Mar 13, 2017 at 12:58 PM, Etienne Robillard  wrote:
>
> As far I know Django channels is a Django framework enforcing a specific 
> messaging protocol in mind.

Honnestly I thought the messaging protocol was just msgpack.

> I don't see how implementing ASGI could help to build more scalable apps
> without breaking compatibility with WSGI.
>

I thought ASGI could sit below WSGI without breaking compatibility.

-- 
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/CAC6Op190DqGD2Tw3rLVEWihEY9LxALuBZsQKYhmuJDjzFkpJ9A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Will asgi become a PEP like wsgi is ?

[James Bennett]

WSGI is a framework-independent protocol to allow HTTP servers to
communicate with Python applications. It defines a standard API and
serialization mechanism to be used by the HTTP server and the Python
application in order to allow them to work together.

WSGI *only* does plain HTTP. And in fact it only does plain HTTP/1.1. It
cannot handle quite a few features of HTTP/2, and provides no support
whatsoever for modern bidirectional web protocols like WebSocket.

ASGI attempts to fill that gap by defining a protocol which allows these
other protocols/features to communicate with Python applications. In much
the same way as WSGI, it defines an API and serialization. There is nothing
Django-specific about ASGI. ASGI is not coupled to Django. ASGI is just a
necessary precondition for being able to build the kinds of things in
Django that Channels aims to provide, in much the same way that WSGI -- or
something like it -- is a necessary precondition for current
request/response HTTP/1.1 Django to exist.

-- 
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/CAL13Cg-xJtxSJ4WyQHdHRacrda9XwQcc8h6FNKr-K_B_kOSK%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Will asgi become a PEP like wsgi is ?

[Etienne Robillard]

WSGI is for building web applications in Python.

ASGI is for building platform-oriented web applications in Django.

I'm -1 on this.

I prefer the ease and flexibility of WSGI draft over asynchronous 
platform choices.


E


Le 2017-03-13 à 07:08, James Pic a écrit :
I do not see myself using Django without Channels anymore, it's become 
a basic Django feature for me and I just love it. Despite my perhaps 
lack of knowledge about the protocol internals, such features seem 
like it would certainly benefit the Python community and anyway I'd 
say it's worth a try just to see what the python-ideas list has to say.

--
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/CAC6Op1-p6O4pzUHcgZEE%2Bap8ZAdkQqeaC_bSi0%3DvF8GH%2BZBc4A%40mail.gmail.com 
.

For more options, visit https://groups.google.com/d/optout.


--
Etienne Robillard
tkad...@yandex.com
http://www.isotopesoftware.ca/

--
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/827eb016-b963-b036-d054-3ed340f848c3%40yandex.com.
For more options, visit https://groups.google.com/d/optout.

Introduction for GSoC 2017

[Gunpreet Ahuja]

Greetings,
I am a Masters in Engineering student at Concordia University, Canada. I 
wish to participate in GSoC 2017. This is my first time and I want to 
contribute in this project.
I have worked on various projects which include three android applications 
named a Textile app, Dawn-to-Dusk (a weather application) and Styllax (a 
wallpaper application). As far as python/django is concerned, I have 
contributed to the project LibreHatti during our undergraduate training. 
The project is entirely based on django framework for python. Besides this, 
I have also worked a data mining project named SocioDAvIS that utilizes 
Facebook data set and Twitter streaming API data to predict different 
trends using R language. The database systems utilized in these projects 
being MySQL and SQLite3.
In addition to this, I have participated in Google Student Ambassador program 
(being listed among the top 400 selected students) and have been a core 
team member of Google Student Club, co-convener at Linux User Group, 
Ludhiana and a member of Android Student Club at my college during my 
undergraduate course. I have worked on Git, Vim, Latex, Doxygen and have 
had a hand on Windows, Linux and Mac Operating Systems. During my 
undergraduate studies only, I won a C++/JAVA event that involved building 
an algorithm to solve a given problem.
As for now, I have working on a JAVA project for metrics analysis of source 
codes. I am currently on the way to polish my python/django skills further.

Regards,
Gunpreet Ahuja
gunpreetahuja.wordpress.com

-- 
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/a881af38-00c2-44db-aeb3-b8e7a2ad87ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Gevent based ASGI server

[Jon Pry]

I modified Daphne and the ASGI layer to get the one of the examples to run 
under gevent. 

Code is here:

https://github.com/jonpry/thyme

Code is not as clean as it needs to be. But imho it works better than 
daphne, none of this hot polling stuff going on anymore. In any case it's 
interesting to see where exactly the ASGI model needs to be tweaked a 
little. 

Cheers,

Jon Pry

-- 
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/5edc94e8-39c8-4d15-aa40-8646c7cc0a2a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Opportunity to contribute in Django

[Jainesh Patel]

Hello,

I am a final year CSE student from PICT, Pune, India. I am very interested 
in contributing to Django.

It would really be very helpful if you suggest any ideas to work on or any 
bugs to resolve from where I can start.

Hoping to hear from you soon, and thanking you in anticipation.

Thank you,
Jainesh Patel

-- 
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/7a96d730-2129-42a3-a64a-15e5d9e915e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Will asgi become a PEP like wsgi is ?

[Etienne Robillard]

As far I know Django channels is a Django framework enforcing a specific 
messaging protocol in mind.


I don't see how implementing ASGI could help to build more scalable apps 
without breaking compatibility with WSGI.


E


Le 2017-03-13 à 07:50, James Pic a écrit :

On Mon, Mar 13, 2017 at 12:26 PM, Etienne Robillard  wrote:

ASGI is for building platform-oriented web applications in Django.

Could you elaborate on this ? The only mention of Django I found in
the spec linked by the OT is "Django Channels ships with a no-op
consumer attached by default; we recommend other implementations do
the same", so it doesn't look really coupled with Django overall:
http://channels.readthedocs.io/en/stable/asgi.html



--
Etienne Robillard
tkad...@yandex.com
http://www.isotopesoftware.ca/

--
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/8362a1d7-a0fa-b48a-4d48-15bdbb651c9f%40yandex.com.
For more options, visit https://groups.google.com/d/optout.

Re: Gevent based ASGI server

[Andrew Godwin]

Hi John,

You are talking about a lot of ideas I want to bring into the main redis
transport (improved polling, connection handling, using the channel name
local part for routing, etc.), which are separate from using gevent,
really; would you be open for contributing this kind of stuff back to the
main asgi_redis transport? It would improve performance on asyncio or
twisted as well.

Andrew

On Sun, Mar 12, 2017 at 9:54 PM, Jon Pry  wrote:

> I modified Daphne and the ASGI layer to get the one of the examples to run
> under gevent.
>
> Code is here:
>
> https://github.com/jonpry/thyme
>
> Code is not as clean as it needs to be. But imho it works better than
> daphne, none of this hot polling stuff going on anymore. In any case it's
> interesting to see where exactly the ASGI model needs to be tweaked a
> little.
>
> Cheers,
>
> Jon Pry
>
> --
> 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/5edc94e8-39c8-4d15-aa40-
> 8646c7cc0a2a%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/CAFwN1uq-Le44BzKty4M1qVzgwMsiANFoB8rSyKyniSNnCppNVw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Will asgi become a PEP like wsgi is ?

[Andrew Godwin]

Right, what James says here is pretty much my thoughts; it has been
designed from the ground up not to be tied to Django, up to and including
the fact that it's in separate packages; all the Django-specific stuff is
in the "channels" package, while daphne, asgi_redis, asgiref etc. are
useable by anything (I need to look into getting another framework like
Flask working on top of it as a proof of concept).

My main sticking point is the design of the ASGI messaging interface, as
that will be the one thing that everyone has to write against - are the
number of calls we have enough? Does async support fit in alright? etc. The
message formats themselves would work on anything that looks remotely
similar.

Andrew

On Mon, Mar 13, 2017 at 5:17 AM, James Bennett 
wrote:

> WSGI is a framework-independent protocol to allow HTTP servers to
> communicate with Python applications. It defines a standard API and
> serialization mechanism to be used by the HTTP server and the Python
> application in order to allow them to work together.
>
> WSGI *only* does plain HTTP. And in fact it only does plain HTTP/1.1. It
> cannot handle quite a few features of HTTP/2, and provides no support
> whatsoever for modern bidirectional web protocols like WebSocket.
>
> ASGI attempts to fill that gap by defining a protocol which allows these
> other protocols/features to communicate with Python applications. In much
> the same way as WSGI, it defines an API and serialization. There is nothing
> Django-specific about ASGI. ASGI is not coupled to Django. ASGI is just a
> necessary precondition for being able to build the kinds of things in
> Django that Channels aims to provide, in much the same way that WSGI -- or
> something like it -- is a necessary precondition for current
> request/response HTTP/1.1 Django to exist.
>
> --
> 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/CAL13Cg-xJtxSJ4WyQHdHRacrda9XwQcc8h6FN
> Kr-K_B_kOSK%3Dg%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/CAFwN1ur01RHWbHS9aR7OQFkBqLktSeOuZwC_gYuqbroWQGii2g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.