python 3.5 support for build system

[pohmelie]

Since build system use cpython 3.4 I can't build documentation for my 3.5 only project. https://readthedocs.org/projects/aioftp/builds/3722703
Is there some plans about 3.5?

[jakirkham]

+1

[agjohnson]

Python 3.5 will definitely come with the april ubuntu 16.04 release, we haven't discussed an interim plan -- though installing from the deadsnakes ppa could be an easy path forward. Another option is to use conda

[ian-ross]

+1 from me too: https://readthedocs.org/projects/django-tutelary/builds/3795496/ (problem caused by yield from in my case).

[agjohnson]

Conda support can target python 3.5, that might be the best bet.

[jakirkham]

I expect there will be the same situation when Python 3.6 comes around too. So, using conda seems reasonable for this problem.

[AndreLouisCaron]

On many Linux distros and on OSX, multiple versions of Python are often aliased to python3.4, python3.5, etc.

Can't we add an option in to select one of these? We can keep the "CPython 2.x" and "CPython 3.x" options, but add "CPython 2.7", "CPython 3.4" and "CPython 3.5" in the choices too.

[agronholm]

+1, whatever solution works :) I have plenty of 3.5 only projects coming that I'd like to build docs for.

[evertheylen]

If people are too lazy to set up a conda environment; just use this configuration file: http://stackoverflow.com/a/36144269/2678118

[agronholm]

Question: how am I supposed to get the project installed in the conda environment?

[agjohnson]

We could use some help beta testing ubuntu 16.04 builders, which will include python 3.5. If anyone is interested, we're collecting a handful of testers here:

https://docs.google.com/forms/d/1YHBXN8LI2RTq6ujV0zENAExtJwbNLja0QKJUHyfUvrE/viewform

[algorys]

+1 for my project too. For https://readthedocs.org/projects/pycmake/builds/4247460/

Problems appears with import enum and typed parameters def foo(param: MyObj)

[AndreLouisCaron]

FWIW, I now host my docs for Python 3.5 projects on Python Hosted solely because of this issue, but the flow there is manual, error prone and doesn't easily allow me to host docs for multiple versions, which is really annoying. I'd really appreciate if this were fixed...

Let me know if there's anything I can do to help.

[jakirkham]

Does the answer given by @evertheylen not work for you @AndreLouisCaron?

[AndreLouisCaron]

Sorry, must has missed that email! Will try it ASAP :-)

André

On Fri, Jul 29, 2016 at 10:43 AM, jakirkham [email protected]
wrote:

Does the answer
#1990 (comment)
given by @evertheylen https://github.com/evertheylen not work for you
@AndreLouisCaron https://github.com/AndreLouisCaron?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#1990 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAITJivVxiGEL5VJTNtuxXM8iJZxTwl5ks5qahGRgaJpZM4HZAZX
.

[numberoverzero]

Any update? I filled out the beta testing form above but haven't heard back.

[c-bata]

+1 my project uses typing module. So autodoc doesn't work :-(

[benjaminweb]

My docs are built without autodoc statements due to lack of Python 3.5:

ImportError: cannot import name 'gcd'

https://docs.python.org/3/library/math.html#math.gcd

What's the timeline?

[pohmelie]

I think it's time to support 3.6, since f-strings will be "syntax error" even for 3.5.

[ashwin31]

👍

[jagadeeshv16]

+1

[druuu]

+1

[chaitu210]

👍

[vidyasagar-r]

👍

[ghost]

👍

[udduu]

👍

[agronholm]

I'm helping the RTD staff create a better build image that allows for selecting the preferred Python version for the build. Python 3.5 and 3.6 are already included.

[vineeshan]

👍

[nikhila05]

👍

[agronholm]

You can stop the reactions now, it's distracting and does not really help.

[agjohnson]

Just a quick update here, as I'm pushing out some updates this week.

First, through a pile of work, support for non-system Python versions has been added. The new beta build container image is now ready for testing (readthedocs/readthedocs-docker-images#18). This will support versions: 2.7, 3.3, 3.4, 3.5, and 3.6. This image uses pyenv to install multiple versions of Python, instead of relying on the distribution's versions.

This will be the new beta image going forward. If you'd like to continue testing our beta images, or would like support for python 3.6, be sure to sign up here:
https://goo.gl/forms/ai9u6jpIhpEpmMRx1

If you've been looking for python 3.5 support, and have not been added to the beta list, we are going to be switching over everyone this week to an image with python 3.5 support. You shouldn't need to do anything, but adding a readthedocs.yml file specifying the correct python version might help if you run into problems.

I am going to write up some docs on using the feature tonight, we'll be announcing changes later this week.

[c-bata]

Great updates! I've just signed up the beta support for python3.6. 👍

[humitos]

This issue was create to support Python 3.5 and it was added in the readthedocs/build:2.0 image so I think the work on this issue is already done and working properly (I saw many projects using python3.5 without problem).

Shouldn't we close this one and move the discussion regarding Python 3.6 to another one?

[Granitosaurus]

For anyone who ends up here for py3.6 support it's officially available:
http://blog.readthedocs.com/python-36-support/

TL;DR:
create file readthedocs.yaml with contents in your project root:

build:
    image: latest

python:
    version: 3.6

[RichardLitt]

I wonder if there is a place in the documentation to include this note from @Granitosaurus. @humitos What do you think?