Closed chris-erickson closed 3 years ago
This must be an old version of the code because requirements.txt
is gone and it's all poetry now. Recently releases of pip got stricter about conflicts which was part of the motivation of moving to poetry to make it easier to keep dependencies up to date.
@rowanseymour This still applies with poetry. "^2020.4"
only allows2020.x
above 4. If you changed the pyproject.toml to ">=2020.4"
it would allow ptz versions of 2021.x as well.
Are you seeing dependency conflicts installing from poetry? If we just want to make sure poetry update
always gets the latest pytz, we can change the version to *
.
yeah that works. the issue we hit is we have the newest pytz and rapidpro-python in a project and that's causing the conflict
Ah ok this is installing into another project - made new release at https://pypi.org/project/rapidpro-python/2.8.2/
Could we expand the pytz dependency? Wondering if this is just a consequence of a quasi-semver problem with the year rolling over.