bump python requirement for 3.5

[bavardage]

cloudpickle dropped support for python 2.x as of cloudpipe/cloudpickle#342 (i.e. cloudpickle 1.4.0)

Checklist

• Used a fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe:

• License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

[bavardage]

Sorry, not sure if this is the best way to do this - but the conda package for cloudpickle 1.4.0 incorrectly doesn't specify that it's only python 3.x compatible which causes problems in some python 2.7 environments.

I think ideally the existing package for 1.4.0 (noarch/cloudpickle-1.4.0-pyh9f0ad1d_0.tar.bz2) should be removed

[bavardage]

@conda-forge-admin, please rerender

[pierreglaser]

This closes #37. Thank you so much for this.

[ogrisel]

This LGTM. Maybe deleting the old package is not required as this new package with the correct metadata targets the same version only with a different build number (1 instead of 0) so maybe the previous package with build number 0 will automatically be discarded by conda on Python 2.

Let's try to merge this to see if this is the case.

[ogrisel]

Thanks very much @bavardage.

[ogrisel]

Build 1 is online but unfortunately conda still picks up the broken build 0 for Python 2.7 environments.