Core meeting agenda 2020-02-03

[mbargull]

@bioconda/core
Please add/edit agenda items below. When relevant, please create an issue for each topic so off-line discussion can occur there.

• Anaconda
  • Bioconda representation at AnacondaCON 2020 (2020-06-03/05)
  • conda + conda-build dev changes
• GCB 2020 (2020-09-14/18)
  • Tutorial deadline 2020-02-12
• Updates from the previous meeting(s)
  • PY 2.7 + 3.6 + 3.8 support
    • News from conda-forge + Anaconda
  • ISMB 2020
    • Acceptance Notification on 2020-01-30
• Handling packages requiring matplotlib rather than matplotlib-base (Xref Add a uses_matplotlib linter check #635)
  • Bulk migration or one at a time?
• Should we update python package recommendations to explicitly mention
  {{ PYTHON }} -m pip install . --ignore-installed --no-deps -vv?
  • conda-build does some "magic" (sets env vars) so we could leave --ignore-installed out
    (@mbargull's personal opinion at update pip command conda-forge/conda-forge.github.io#618 (comment) ff.)

[dpryan79]

With PY 2.7 + 3.6 + 3.8 do you mean 3.6 and 3.7 or 3.7 and 3.8? It appears conda-forge is nearing the end of the 3.8 migration, so I assume the latter.

[mbargull]

No, I meant

• 2.7 phase-out
• 3.6 continued support
• 3.8 general adoption

We talked about it in last week's conda-forge core meeting, but it's still being discussed. We also have another meeting in two days and a https://github.com/conda-forge/cfep/pulls will be created to lay down the plan of which/how many Python versions will be supported concurrently.