Add Python 3.7

[gaiar]

Requires for building:

• libffi library for CPython extensions
• adding add_pip_as_python_dependency: False in conda.rc

Then:

• Rebuilding setuptools
• Rebuilding PIP

[kylebolstad]

I was able to get Python 3.7 built to berryconda3/pkgs/python-3.7.0-0/bin/python. Any chance you can expand upon what it means to rebuild setuptools and pip?

[gaiar]

You need to pull pip and setuptools feedstocks and build them defining python version 3.7 via conda build variants https://docs.conda.io/projects/conda-build/en/latest/resources/variants.html?highlight=variants

Please consider, that all recipes have to be rebuilt with Python 3.7 for full support.

[sebastienvercammen]

It's August 2019, a full year since the original PR, and wheels on piwheels.org are only built for py3.5.x or py3.7.x, not py3.6.x.

pywheels py3.6.x support was intentionally canceled in March, without berryconda support for py3.7.x: piwheels/piwheels#27 (comment)

berryconda not supporting py3.7.x breaks support for projects running latest python via conda (berryconda, latest available is 3.6.6) that have implemented static typing (available since py3.6.x) and need large libraries (in our case: numpy, scipy, pillow).

I'm not familiar w/ berryconda's inner workings, so what is missing to officially support py3.7.x in berryconda?

CC @jjhelmus

[Dawars]

I'm also interested, can I help somehow?

[jjhelmus]

I've been taking some time away from berryconda to work on other projects and explore ways in which berryconda development can be more collaborative. Specifically, I bootstrapped support for the 64-bit ARM architecture in conda. conda-forge is now building packages for this platform with most of the core packages covered. Help is always appreciated to complete the "migrations" to this platform. These packages will work on Raspberry Pi 2, 3 and 4s if they run a 64-bit operating system but 32-bit packages are required on Raspbian.

With a little more work conda-forge can also build 32-bit ARM packages for the linux-armv7l platform. I have done some work on this front, building out an initial set of packages (include python 3.7), adding an armv7l docker image, and making the necessary modification to conda-smithy. I think a release of conda-smithy and a migrator are needed to start the process. If anyone wants to help these would be great places to contribute.

[gaiar]

Hi, @jjhelmus. Happy to see that armv7l work is getting mainstreamed. I would be happy to help to make that happen, but I don't think I fully understood the missing steps. What kind of help is needed?

[franva]

Hi it's year 2020.

I'm facing problem when using Berry Conda.
Once it is installed, it breaks my PyTorch (1.3.1) and I cannot fix the problem, I cannot uninstall Berry Conda either.

Not familiar with Linux, I am highly appreciate that if someone could make an Uninstall.sh

Thanks

[sebastienvercammen]

Real life has other plans for me as well, so this is not something I could/can pick up in the short term.

Hi it's year 2020.

But @franva, just like in 2019 and the years before, open source is open. You can learn to become more familiar with what you don't yet know, and add your own contributions to the work of the maintainers.

Your phrasing was (perhaps unintentionally?) not what it could have been.

[kanglue]

When berryconda can support python 3.7?

[wisehackermonkey]

bump "when berryconda can support python 3.7?"

[jjhelmus]

bump "when berryconda can support python 3.7?"

See the discussion of the future of berryconda in #83. If this is something you are interested please consider contributing to the future development.