Will asgi become a PEP like wsgi is ?

[Sebastian Haase]

(sorry for cross-posting -  post should like be here rather than in 
django-users)
Hi,

wsgi is specified by
PEP 333 -- Python Web Server Gateway Interface v1.0
https://www.python.org/dev/peps/pep-0333/

Django channels rely on asgi instead.
So far ASGI specs appear only here:
http://channels.readthedocs.io/en/stable/asgi.html

How do these two concepts compare in regards to their respect "importance" 
to the python community?
Especially under the consideration that real-time web applications (i.e. 
HTML5 websockets) is getting more and more important.

Regards,
Sebastian

-- 
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/2ee5ce83-1990-457a-b6d8-0b1db84e4b0b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

SQLAlchemy integration - More details

[stamatis . iliass]

Hello.

I would like to request a bit more information about the SQLAlchemy 
integration project listed on the GSoC ideas: 
https://code.djangoproject.com/wiki/SummerOfCode2017#SQLAlchemyNoSQLintegration

Even though, I don't feel that I have the time to prepare a proper GSoC 
application (since it's already too late), I may be interested in 
implementing it anyway (outside GSoC). It seems very promising.

I did a 1-2 day "research" on "use django with SQLAlchemy" back when I 
discovered this specific project, but the results didn't really prove to be 
helpful to me. 

Could I have a bit more information on this project? Previous discussions 
about it (if any)? Any directions? 

Also, could someone explain a little more the following sentence, since 
it's not completely clear to me what is being asked here:  "take a set of 
models defined in a non-Django data store, and define the mechanisms 
necessary to expose those models in Django's contrib.admin interface"

What does "models" mean in this case?

I just want a small push to look into the right direction in order to 
approach this project. 

Thank you very much for your time,
Ilias Stamatis

-- 
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/b7c81284-fc61-47bf-9140-f8dae86ad6f5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Will asgi become a PEP like wsgi is ?

[Andrew Godwin]

Hi Sebastian,

The proposal is certainly written like a PEP, and that is somewhat on
purpose, but the scope and need for it are still a bit up in the air. In
particular, ASGI currently specifies two parts:

 - An interface for talking to channel-based message queues and a set of
guarantees and non-guarantees for them around delivery
 - A specification for encoding HTTP and WebSocket traffic on top of this
interface as a set of messages

Given this, I would probably at a minimum want to separate the two of them
out before thinking about approaching the PEP process with either part. The
message queue abstraction is likely the harder one to get through as it is
(deliberately) quite opinionated, but without it the other doesn't really
make sense.

So, you see the quandry here, really. I just need to take the time and
separate them and then start prodding people for feedback, I suspect, but
anyone else on this list who has an opinion should definitely say something.

Andrew

On Sun, Mar 12, 2017 at 5:44 AM, Sebastian Haase 
wrote:

> (sorry for cross-posting -  post should like be here rather than in
> django-users)
> Hi,
>
> wsgi is specified by
> PEP 333 -- Python Web Server Gateway Interface v1.0
> https://www.python.org/dev/peps/pep-0333/
>
> Django channels rely on asgi instead.
> So far ASGI specs appear only here:
> http://channels.readthedocs.io/en/stable/asgi.html
>
> How do these two concepts compare in regards to their respect "importance"
> to the python community?
> Especially under the consideration that real-time web applications (i.e.
> HTML5 websockets) is getting more and more important.
>
> Regards,
> Sebastian
>
> --
> 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/2ee5ce83-1990-457a-b6d8-
> 0b1db84e4b0b%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/CAFwN1upsr612H0dXs6Qkjc92CFX0t_BxZ%2ByiKxOkUWmtNE%3DZFw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.