Re: Potential suspension of Channels development

2019-01-20 Thread Shrawan Poudel 
Hello, i am interested in helping in this project. Please guide thought the
process for helping .
I have been using these projects in many of my Production app .



On Sun, Jan 20, 2019 at 1:58 AM Carlton Gibson 
wrote:

> Hey Andrew.
>
> I've been thinking a lot about this. You clearly shouldn't be maintaining
> Channels single-handedly indefinitely.
>
> On Thursday, 17 January 2019 19:07:06 UTC+1, Andrew Godwin wrote:
>>
>> Given that, if nobody else can step forward to take over, I'll have to
>> put those three projects (Channels, channels-redis, and Daphne) into an
>> explicit maintenance mode where they only accept security requests via the
>> normal security@ route, and start the process of retiring them as active
>> Django projects, as I don't want to give the impression they're still
>> maintained if they're not.
>>
>> (note: the asgiref project is still fine and should probably move out of
>> Django to its own effort at some point giving the growing set of ASGI tools)
>>
>
> I know Channels started out separately, but, it's time to think about
> what, if anything of channels, is to be brought into core, or become THE
> WAY we do things or... Yes, we need more hands, but there's a bunch of
> people who can help out, and at least part of the problem is your out there
> in the wings by yourself (with not much visibility.)
>
> Q: How does Channels fit into the "Django Async Roadmap"?
>
> To the extent that it does, I think there's a case for asking the board
> and the DSF more widely to throw everything we've got behind making sure
> it's properly resourced.
>
> Once I recover a bit from the burnout I'll be able to come back and help
>> with the really complex bugs; the main thing I need out of is the seemingly
>> endless support requests and weird WebSocket client bugs.
>>
>
> I presume you DON'T offer support on the issue tracker, and point people
> to other channels? I'd be happy to "straight-bat" obvious tickets away.
> (Michael's offer to recieve is valuable there.)
>
> "...and weird WebSocket client bugs."
>
> Can I ask you to explain what you mean there? (Point to a ticket maybe.)
> What kind of query do you get? Is there a particular knack to working out
> if it's a valid bug or not? (Or is it apparent?)
>
> Thanks for all you work here. Legend. 🙂
>
> Kind Regards,
>
> Carlton
>
> --
> 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/68626427-d97d-4053-8836-5382483f63af%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/CAPD6Jmnz9uE1jUhe5FYUMoJ7CUcDuwAru2S9p9UVKT4VMoyiOQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Messages without text in the messages framework

2019-01-20 Thread Adam Johnson 
This mailing list is for the development of Django itself, not for support
using Django. Please use the django-users mailing list for that, or IRC
#django on freenode, or a site like Stack Overflow.

On Sat, 19 Jan 2019 at 16:00, Sebastian Lechner  wrote:

> Dear Django developer community,
>
> often I would like to trigger a message to the user with the message
> rendered dynamically in the client-side JS code. I use the message
> framework's tags to differentiate between the different messages in JS.
>
> Usually, I will define the message's text on the client side as well,
> making it unnecessary to define the message text in the Django backend. My
> first idea was to set the message text parameter to "None" or the empty
> string when calling add_message.
>
> Unfortunately, it seems that this will lead to the message beging
> discarded. Is there are another way to send a message without text (but a
> number of tags) with the messages framework?
>
> Best 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/044afeb0-8ad5-82f4-7b9f-75ea6c5db44b%40seble.info
> 
> .
> 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/CAMyDDM19QZvRGBP7U%3D2g6yrFO6wBp42gT%3DrivcEA4h%3D0Nm0Gow%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

static templatetag: adding default argument blank

2019-01-20 Thread Mohammad Etemaddar 
in the conversion of HTML template to Django template, sometimes it is hard 
to find&remplce static paths.
In current Django template we should change for example this:


to


as you see we add two parts to the href:



We can also do in this order:


(2) 

In this way, we need to do only one find/replace. But in the previous way, 
we should first do find/replace on beginning and then add "%}" to the end. 
Maybe with some find/replace on every suffix (jpg,jpeg,css,js,png...)
But in way (2) We need only one find/replace if we have one asset directory 
in template.
In this way, We can give the static function default value blank in order 
to put just *{% static %}*.

-- 
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/b891d179-a6da-4150-8ebd-a966e5af9567%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: static templatetag: adding default argument blank

2019-01-20 Thread Adam Johnson 
I would be against adding this. Most text editors support a
find-and-replace with regex option that would let you capture the asset
path and place it within the {% static '' %} tag; additionally, you could
always change your templates to include STATIC_URL globally and just do
{{ STATIC_URL }} if you wanted to avoid using the static tag with the path
to the asset.

On Sun, 20 Jan 2019 at 17:47, Mohammad Etemaddar <
mohammad.etemad...@gmail.com> wrote:

> in the conversion of HTML template to Django template, sometimes it is
> hard to find&remplce static paths.
> In current Django template we should change for example this:
>
> 
> to
> 
>
> as you see we add two parts to the href:
>
> 
>
> We can also do in this order:
>
>
> (2) 
>
> In this way, we need to do only one find/replace. But in the previous way,
> we should first do find/replace on beginning and then add "%}" to the end.
> Maybe with some find/replace on every suffix (jpg,jpeg,css,js,png...)
> But in way (2) We need only one find/replace if we have one asset
> directory in template.
> In this way, We can give the static function default value blank in order
> to put just *{% static %}*.
>
> --
> 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/b891d179-a6da-4150-8ebd-a966e5af9567%40googlegroups.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/CAMyDDM2ffNLrD-ARSnwDdMms6__RU1MJ-q2V09SDpPVheO%3DBAg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: static templatetag: adding default argument blank

2019-01-20 Thread Mohammad Etemaddar 
You are right. This is a better option, {{ STATIC_URL }}.
Mohammad Etemaddar

*  in   *
Programming services: *Python* & *Linux*



On Sun, Jan 20, 2019 at 9:46 PM Adam Johnson  wrote:

> I would be against adding this. Most text editors support a
> find-and-replace with regex option that would let you capture the asset
> path and place it within the {% static '' %} tag; additionally, you could
> always change your templates to include STATIC_URL globally and just do
> {{ STATIC_URL }} if you wanted to avoid using the static tag with the path
> to the asset.
>
> On Sun, 20 Jan 2019 at 17:47, Mohammad Etemaddar <
> mohammad.etemad...@gmail.com> wrote:
>
>> in the conversion of HTML template to Django template, sometimes it is
>> hard to find&remplce static paths.
>> In current Django template we should change for example this:
>>
>> 
>> to
>> 
>>
>> as you see we add two parts to the href:
>>
>> 
>>
>> We can also do in this order:
>>
>>
>> (2) 
>>
>> In this way, we need to do only one find/replace. But in the previous
>> way, we should first do find/replace on beginning and then add "%}" to the
>> end. Maybe with some find/replace on every suffix (jpg,jpeg,css,js,png...)
>> But in way (2) We need only one find/replace if we have one asset
>> directory in template.
>> In this way, We can give the static function default value blank in order
>> to put just *{% static %}*.
>>
>> --
>> 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/b891d179-a6da-4150-8ebd-a966e5af9567%40googlegroups.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/CAMyDDM2ffNLrD-ARSnwDdMms6__RU1MJ-q2V09SDpPVheO%3DBAg%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/CALJt1nvTy5x6DDUuf2pC-KOwxoR5kh8jADzLv%3DrfgPF6W2j6dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Potential suspension of Channels development

2019-01-20 Thread Andrew Godwin 
On Sat, Jan 19, 2019 at 12:13 PM Carlton Gibson 
wrote:

> Hey Andrew.
>
> I've been thinking a lot about this. You clearly shouldn't be maintaining
> Channels single-handedly indefinitely.
>
> I know Channels started out separately, but, it's time to think about
> what, if anything of channels, is to be brought into core, or become THE
> WAY we do things or... Yes, we need more hands, but there's a bunch of
> people who can help out, and at least part of the problem is your out there
> in the wings by yourself (with not much visibility.)
>
> Q: How does Channels fit into the "Django Async Roadmap"?
>
> To the extent that it does, I think there's a case for asking the board
> and the DSF more widely to throw everything we've got behind making sure
> it's properly resourced.
>

The main problem with Channels, I feel, is that is solves the wrong problem
- it's focused on WebSockets, which is a niche feature that a few people
are happy we provide but most people have no practical use for.

Instead, I think Django should focus on a good async path for HTTP - views,
ORM, templates, and the like. This is what I want to get done if I can get
my time and energy back!


> I presume you DON'T offer support on the issue tracker, and point people
> to other channels? I'd be happy to "straight-bat" obvious tickets away.
> (Michael's offer to recieve is valuable there.)
>

I do try to do this - I wrote a standard page last year to help out with
batting away (https://channels.readthedocs.io/en/latest/support.html) - but
sometimes it's hard to triage the bug from the support request. Your help
there would be most appreciated, and yes, I should add Michael's offer to
that support page.


>
> "...and weird WebSocket client bugs."
>
> Can I ask you to explain what you mean there? (Point to a ticket maybe.)
> What kind of query do you get? Is there a particular knack to working out
> if it's a valid bug or not? (Or is it apparent?)
>

I don't want to single anyone out, as it's not their fault, but bugs like
this: https://github.com/django/daphne/issues/244

This person did the work and figured it out for the most part, but lots of
bugs that complex and confusing come in with just the first part of the
issue and I'm left wondering if it's their browser, their server, their
Python install or actually Channels.

At some point, I wake up every morning to 5-6 emails from the various
projects and it overwhelms, as I'm sure you've encountered. Even the bugs
are nasty enough that I don't feel like fixing them once I've figured out
they're actually bugs.


>
> Thanks for all you work here. Legend. 🙂
>

And thank you for your response and help :)

Andrew

-- 
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/CAFwN1upg1yzYmN2KA989PSUpoPNy-B2Pyo3FmQb9%3D5qA9K6i%2BA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Introduction GSoC

2019-01-20 Thread noumbissivalere 
Hello Everyone! Am Noumbissi Valere, a student from Cameroon. Am skilled in 
python and have used django to build some web apps. Am new to open source 
and will love to contribute to django, hoping to participate for GSoC this 
Year. Please can anyone help me on how to get started?

-- 
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/5801f106-9beb-43d9-b8d0-7d1f91fb9a63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.