search

planetarypy / TC

PlanetaryPy Project Technical Committee
https://planetarypy.org/
1 stars 2 forks source link

Updates to review guidelines. #46

Closed rbeyer closed 3 years ago

rbeyer commented 3 years ago

Yeah, I thought about that, but that's not the requirement that we had discussed (more than a year ago, now). Technically, if a package was compatible only with Python 3.8, it won't work with 3.6, which was our "minimum common version" target. Such a package would match the ">=3.6" so I think this compatibility factor is a single version. We want the largest number of users to be able to use the PlanetaryPy packages, so our dev target is going to always be an older--but supported--version, but it is a single version.

Over time, we will move this version requirement forward, and will have to re-evaluate our affiliated packages.

AndrewAnnex commented 3 years ago

ah, I was thinking >= for this case would just imply it is compatible with 3.6 and everything above but I see your point.