---
# System prepended metadata

title: DIALS core meeting 2020-07-16

---

# DIALS core meeting 2020-07-16

#### Agenda
1.	Python 3.7/3.8 compatibility update, rollout discussion, [dials#1236](https://github.com/dials/dials/issues/1236)
    * can be merged
3.	Python 3.6 deprecation proposal / [NEP-29](https://numpy.org/neps/nep-0029-deprecation_policy.html) / [dials#1327](https://github.com/dials/dials/issues/1327)
    * GW is waiting for some reaction to the ongoing 2.7 deprecation process.
    * We agreed that we have an understanding of the problem
5.	Moving to Python 3.8 as the next default, skipping 3.7 (cf. [#1328-comment](https://github.com/dials/dials/pull/1328#issuecomment-655812577)
    * DW suggests retaining backwards-compatibility
    * ND suggests build server to 3.7, default to 3.8
    * GW: In a PR-guided workflow environment we run testing on all platforms via Azure anyway, so likely a non-problem?

## Actions

* [ ] ND: rewrite contribution guidelines (as PR) to include towncrier/newsfragments
* [ ] GW: ask cctbx-bb who uses Python 2 development environment
* [ ] MG: set up next meeting in 'few weeks time'


## Not discussed

4.	Overall architecture discussion - full conda or alternatives?
5.	Following from that: How should a new installer look like

If you have anything else let me know.

Since all our meetings are on Zoom anyway we should also consider open up these DIALS core meetings to DIALS-W and the world in an effort to [move DIALS towards a stage 3 project](http:/urssi.us/blog/2019/02/25/software-incubator-workshop-a-synthesis/)
