Fabric examples in documentation

[Tim Graham]

>From https://code.djangoproject.com/ticket/29360:

  "The ​Serving the site and your static files from the same server 

 
and the ​Serving static files from a dedicated server 

 
documentation references Fabric and fabfiles. Fabric (as linked in the 
docs) is a Python 2.5-2.7 only project. This should probably change since 
Django 2.0+ is Python3 only.
Fabric has a ​roadmap  for Python 3 
support, last updated May 2015. They propose moving eventually to a Fabric2 
... unfortunately there already exists a ​Fabric3 
 fork, so keeping Fabric in the docs 
could (eventually) lead to confusion."

What do you think is the best way to proceed here?

-- 
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/e39b0e47-98b2-4c5a-96cc-f4520c249e67%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fabric examples in documentation

[Florian Apolloner]

I'd just drop the paragraph

On Wednesday, April 25, 2018 at 7:42:45 PM UTC+2, Tim Graham wrote:
>
> From https://code.djangoproject.com/ticket/29360:
>
>   "The ​Serving the site and your static files from the same server 
> 
>  
> and the ​Serving static files from a dedicated server 
> 
>  
> documentation references Fabric and fabfiles. Fabric (as linked in the 
> docs) is a Python 2.5-2.7 only project. This should probably change since 
> Django 2.0+ is Python3 only.
> Fabric has a ​roadmap  for Python 3 
> support, last updated May 2015. They propose moving eventually to a Fabric2 
> ... unfortunately there already exists a ​Fabric3 
>  fork, so keeping Fabric in the docs 
> could (eventually) lead to confusion."
>
> What do you think is the best way to proceed here?
>

-- 
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/8bcf106a-03a6-4d88-893f-fc37482af262%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fabric examples in documentation

[Collin Anderson]

A little bit more information: Fabric2 has been actively developed over the
last year, but is still Alpha (may get api changes):
https://github.com/fabric/fabric/tree/v2
http://bitprophet.org/blog/2017/04/17/fabric-2-alpha-beta/

I agree removing references to fabric might be the way to go. There are
lots of ways to deploy files.

On Wed, Apr 25, 2018 at 1:55 PM, Florian Apolloner 
wrote:

> I'd just drop the paragraph
>
> On Wednesday, April 25, 2018 at 7:42:45 PM UTC+2, Tim Graham wrote:
>>
>> From https://code.djangoproject.com/ticket/29360:
>>
>>   "The ​Serving the site and your static files from the same server
>> 
>> and the ​Serving static files from a dedicated server
>> 
>> documentation references Fabric and fabfiles. Fabric (as linked in the
>> docs) is a Python 2.5-2.7 only project. This should probably change since
>> Django 2.0+ is Python3 only.
>> Fabric has a ​roadmap  for Python 3
>> support, last updated May 2015. They propose moving eventually to a Fabric2
>> ... unfortunately there already exists a ​Fabric3
>>  fork, so keeping Fabric in the docs
>> could (eventually) lead to confusion."
>>
>> What do you think is the best way to proceed here?
>>
> --
> 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/8bcf106a-03a6-4d88-893f-
> fc37482af262%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/CAFO84S6JhvQtnJEdTZzM5_Loi%2B6LWCxgA4aM366AgMfsN2WDFA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

#django-dev IRC channel

[Kenneth Yang]

Hello,

I was just curious about the #django-dev IRC Channel.
Currently, the only mention for this channel is on the Code of Conduct FAQ 
 page.
Should it also be mentioned on the Contributing to Django 
 page?

-- 
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/65d173d8-d827-46ea-988e-8718bf56b7a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

ExceptionMiddleware still necessary in documentation?

[Shiyang Wang]

Hello!

Following up from this issue: https://code.djangoproject.com/ticket/29359

I am currently working on this issue with Jessica and I was wondering if 
ExceptionMiddleware is still necessary in the documentation, or can it 
simply be removed? It is not referenced anywhere else in the Django code 
files, only in the documentation. 

Regards,

Shiyang 

-- 
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/ce4003d1-c2a7-4e85-999d-4fc8bf4400c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ExceptionMiddleware still necessary in documentation?

[Florian Apolloner]

It got removed in 
https://github.com/django/django/commit/7d1b69dbe7f72ac04d2513f0468fe2146231b286
 
-- as such it can also be removed from the documentation.

On Wednesday, April 25, 2018 at 9:34:07 PM UTC+2, Shiyang Wang wrote:
>
> Hello!
>
> Following up from this issue: https://code.djangoproject.com/ticket/29359
>
> I am currently working on this issue with Jessica and I was wondering if 
> ExceptionMiddleware is still necessary in the documentation, or can it 
> simply be removed? It is not referenced anywhere else in the Django code 
> files, only in the documentation. 
>
> Regards,
>
> Shiyang 
>

-- 
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/e6c6a57d-b55b-4e92-92b4-e6ac53961bd1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

ModelAdmin.prepopulated_fields removes stop words

[Kelly]

Hello,

I am working on ticket 29351  
and I am documenting that ModelAdmin.prepopulated_fields removes stop 
words. I have looked in the codebase, but I am having trouble finding 
exactly where this logic is so that I can made the documentation as 
specific as possible.

Can anyone help pinpoint where the stop words are being filtered out or is 
just stating that stop words are filtered out sufficient?

Cheers,

Kelly

-- 
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/706f3bb8-0e91-4123-be85-960383843c30%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ModelAdmin.prepopulated_fields removes stop words

[Collin Anderson]

Hi Kelly,

I believe it's in urlify.js
https://github.com/django/django/blob/master/django/contrib/admin/static/admin/js/urlify.js#L172-L175

Collin


On Wed, Apr 25, 2018 at 4:51 PM, Kelly  wrote:

> Hello,
>
> I am working on ticket 29351 
> and I am documenting that ModelAdmin.prepopulated_fields removes stop
> words. I have looked in the codebase, but I am having trouble finding
> exactly where this logic is so that I can made the documentation as
> specific as possible.
>
> Can anyone help pinpoint where the stop words are being filtered out or is
> just stating that stop words are filtered out sufficient?
>
> Cheers,
>
> Kelly
>
> --
> 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/706f3bb8-0e91-4123-be85-
> 960383843c30%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/CAFO84S7ZBwjYsufzo8j6eFJotaYtTUobb783q2Lv%2Bj%3D%3DvHbf8Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: ModelAdmin.prepopulated_fields removes stop words

[Kelly]

Thank you for your help Collin!

On Wednesday, April 25, 2018 at 4:57:17 PM UTC-4, Collin Anderson wrote:
>
> Hi Kelly,
>
> I believe it's in urlify.js 
> https://github.com/django/django/blob/master/django/contrib/admin/static/admin/js/urlify.js#L172-L175
>
> Collin
>
>
> On Wed, Apr 25, 2018 at 4:51 PM, Kelly > 
> wrote:
>
>> Hello,
>>
>> I am working on ticket 29351 
>>  and I am documenting 
>> that ModelAdmin.prepopulated_fields removes stop words. I have looked in 
>> the codebase, but I am having trouble finding exactly where this logic is 
>> so that I can made the documentation as specific as possible.
>>
>> Can anyone help pinpoint where the stop words are being filtered out or 
>> is just stating that stop words are filtered out sufficient?
>>
>> Cheers,
>>
>> Kelly
>>
>> -- 
>> 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-develop...@googlegroups.com .
>> To post to this group, send email to django-d...@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/706f3bb8-0e91-4123-be85-960383843c30%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/13698be6-8c93-41b0-a8ae-81a793afc5d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ExceptionMiddleware still necessary in documentation?

[Tim Graham]

There may be portions of that documentation that could be relocated as some 
of the information is still relevant to new-style middleware. By the way, 
it's better to ask this type of question on the ticket as it doesn't 
require the attention of everyone reading this mailing list.

On Wednesday, April 25, 2018 at 4:03:31 PM UTC-4, Florian Apolloner wrote:
>
> It got removed in 
> https://github.com/django/django/commit/7d1b69dbe7f72ac04d2513f0468fe2146231b286
>  
> -- as such it can also be removed from the documentation.
>
> On Wednesday, April 25, 2018 at 9:34:07 PM UTC+2, Shiyang Wang wrote:
>>
>> Hello!
>>
>> Following up from this issue: https://code.djangoproject.com/ticket/29359
>>
>> I am currently working on this issue with Jessica and I was wondering if 
>> ExceptionMiddleware is still necessary in the documentation, or can it 
>> simply be removed? It is not referenced anywhere else in the Django code 
>> files, only in the documentation. 
>>
>> Regards,
>>
>> Shiyang 
>>
>

-- 
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/3094b38f-0ff9-4fe9-9596-89579910fe1c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.