Loading...

​​AnacondaCon agenda

​​

​​conda-forge sustainability: 

• ​​CIs

• ​​anaconda.org — What is the future of hosting conda-forge packages on anaconda.org?

• ​​new recipes

• ​​updates

• ​​standardize recipe style to facilitate merges between aggregate and conda-forge

​​

​​Should we sprint to get new maintainers?

​​

​​TODOs

• ​​a few slides

• ​​https://github.com/ocefpaf/talk_pycon2017

• ​​https://github.com/python-packaging-tutorial/python-packaging-tutorial/pull/3

• ​​bit.ly/scipy16cf

• ​​example of tracking metrics over time: https://github.com/parente/nbestimate

• ​​https://docs.google.com/presentation/d/18d5uGYUc7ZVrgABmz8wH4XdD8B8nAhCzRYwienPtZFE/edit?usp=sharing

• ​​communication on API breaks

• ​​packaging tools should be boring!

• ​​move slowly and never brzeak (not move quickly and break things)

• ​​noarch?

• ​​does not work with constructor

• ​​entry points do not work with noarch: python​ (really? I think it is scripts folders that currently donw

• ​​conda-forge installer (as opposed to the miniconda installer)

• ​​This saves time on CIs if we can just use the CF-built packages instead of installing miniconda and then replacing most/all of them with their CF cousins

• ​​Avoids spending time dealing with breakage in staged-recipes/all feedstocks and focuses fixes in one place (the installer itself). Thus making it easier to fix problems that crop up and improve reproducibility

• ​​Update bot

​​