[Django] #29360: collectstatic docs reference Python2-only Fabric

4 views
Skip to first unread message

Django

unread,
Apr 24, 2018, 8:39:55 PM4/24/18
to django-...@googlegroups.com
#29360: collectstatic docs reference Python2-only Fabric
-------------------------------------+-------------------------------------
Reporter: stvsmth | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: | Version: 2.0
Documentation | Keywords: staticfiles,
Severity: Normal | collectstatic, fabric
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
[https://docs.djangoproject.com/en/2.0/howto/static-files/deployment
/#serving-the-site-and-your-static-files-from-the-same-server Serving the
site and your static files from the same 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 [http://www.fabfile.org/roadmap.html roadmap] for Python 3
support, last updated May 2015. They propose moving eventually to a
Fabric2 ... unfortunately there already exists a
[https://pypi.org/project/Fabric3/ Fabric3] fork, so keeping Fabric in the
docs could (eventually) lead to confusion.

I searched for existing tickets, #15080 is about the same area of
documentation, but a completely different problem.

If the Django devs want to recommend a particular package I would be
willing to update the docs.

--
Ticket URL: <https://code.djangoproject.com/ticket/29360>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Apr 24, 2018, 8:40:39 PM4/24/18
to django-...@googlegroups.com
#29360: collectstatic docs reference Python2-only Fabric
-------------------------------------+-------------------------------------
Reporter: stvsmth | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Documentation | Version: 2.0
Severity: Normal | Resolution:
Keywords: staticfiles, | Triage Stage:
collectstatic, fabric | Unreviewed
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by stvsmth):

* cc: stvsmth (added)


--
Ticket URL: <https://code.djangoproject.com/ticket/29360#comment:1>

Django

unread,
Apr 24, 2018, 8:49:26 PM4/24/18
to django-...@googlegroups.com
#29360: collectstatic docs reference Python2-only Fabric
-------------------------------------+-------------------------------------
Reporter: stvsmth | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Documentation | Version: 2.0
Severity: Normal | Resolution:
Keywords: staticfiles, | Triage Stage:
collectstatic, fabric | Unreviewed
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Description changed by stvsmth:

Old description:

> [https://docs.djangoproject.com/en/2.0/howto/static-files/deployment
> /#serving-the-site-and-your-static-files-from-the-same-server Serving the
> site and your static files from the same 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 [http://www.fabfile.org/roadmap.html roadmap] for Python 3
> support, last updated May 2015. They propose moving eventually to a
> Fabric2 ... unfortunately there already exists a
> [https://pypi.org/project/Fabric3/ Fabric3] fork, so keeping Fabric in
> the docs could (eventually) lead to confusion.
>
> I searched for existing tickets, #15080 is about the same area of
> documentation, but a completely different problem.
>
> If the Django devs want to recommend a particular package I would be
> willing to update the docs.

New description:

The [https://docs.djangoproject.com/en/2.0/howto/static-files/deployment
/#serving-the-site-and-your-static-files-from-the-same-server Serving the
site and your static files from the same server] and the
[https://docs.djangoproject.com/en/2.0/howto/static-files/deployment
/#serving-static-files-from-a-dedicated-server 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 [http://www.fabfile.org/roadmap.html roadmap] for Python 3
support, last updated May 2015. They propose moving eventually to a
Fabric2 ... unfortunately there already exists a
[https://pypi.org/project/Fabric3/ Fabric3] fork, so keeping Fabric in the
docs could (eventually) lead to confusion.

I searched for existing tickets, #15080 is about the same area of
documentation, but a completely different problem.

If the Django devs want to recommend a particular package I would be
willing to update the docs.

--

--
Ticket URL: <https://code.djangoproject.com/ticket/29360#comment:2>

Django

unread,
Apr 25, 2018, 1:43:16 PM4/25/18
to django-...@googlegroups.com
#29360: collectstatic docs reference Python2-only Fabric
-------------------------------------+-------------------------------------
Reporter: stvsmth | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Documentation | Version: 2.0
Severity: Normal | Resolution:
Keywords: staticfiles, | Triage Stage: Accepted
collectstatic, fabric |
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):

* stage: Unreviewed => Accepted


Comment:

I [https://groups.google.com/d/topic/django-
developers/GLNuVW1S_yk/discussion asked on django-developers] about how to
proceed.

--
Ticket URL: <https://code.djangoproject.com/ticket/29360#comment:3>

Django

unread,
Apr 29, 2018, 10:26:22 PM4/29/18
to django-...@googlegroups.com
#29360: collectstatic docs reference Python2-only Fabric
-------------------------------------+-------------------------------------
Reporter: stvsmth | Owner: nobody
Type: | Status: closed

Cleanup/optimization |
Component: Documentation | Version: 2.0
Severity: Normal | Resolution: fixed

Keywords: staticfiles, | Triage Stage: Accepted
collectstatic, fabric |
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):

* status: new => closed
* resolution: => fixed


Comment:

In [changeset:"d0b04c6308fdd0909630fc1ed9f466082ed1d38f" d0b04c63]:
{{{
#!CommitTicketReference repository=""
revision="d0b04c6308fdd0909630fc1ed9f466082ed1d38f"
Fixed #29360 -- Removed Fabric examples in docs.
}}}

--
Ticket URL: <https://code.djangoproject.com/ticket/29360#comment:4>

Django

unread,
Apr 29, 2018, 10:26:34 PM4/29/18
to django-...@googlegroups.com
#29360: collectstatic docs reference Python2-only Fabric
-------------------------------------+-------------------------------------
Reporter: stvsmth | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: 2.0
Severity: Normal | Resolution: fixed
Keywords: staticfiles, | Triage Stage: Accepted
collectstatic, fabric |
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Tim Graham <timograham@…>):

In [changeset:"670ebccfef6a1f1850a29120cfe893bcf852718c" 670ebccf]:
{{{
#!CommitTicketReference repository=""
revision="670ebccfef6a1f1850a29120cfe893bcf852718c"
[2.0.x] Fixed #29360 -- Removed Fabric examples in docs.

Backport of d0b04c6308fdd0909630fc1ed9f466082ed1d38f from master
}}}

--
Ticket URL: <https://code.djangoproject.com/ticket/29360#comment:5>

Reply all
Reply to author
Forward
0 new messages