why can't a minor version change not be goddamn backward compatible ffs.
-
why can't a minor version change not be goddamn backward compatible ffs.
-
why can't a minor version change not be goddamn backward compatible ffs.
@stf Python never used semantic versioning so the part you call minor is more like the calendar version. It's just unfortunate it looks like semantic versioning. I know they considered changing it to look more calendar-like but that was rejected.
-
why can't a minor version change not be goddamn backward compatible ffs.
@stf
What are you using that is so sensitive to version changes?I've been maintaining a Python app since 2007 that requires 34 standard library packages and optionally uses an additional 21 standard and third-party packages, and the only revisions that have been required were for the Python 2/3 transition and the changes to the openpyxl and xlrd libraries.
-
@stf
What are you using that is so sensitive to version changes?I've been maintaining a Python app since 2007 that requires 34 standard library packages and optionally uses an additional 21 standard and third-party packages, and the only revisions that have been required were for the Python 2/3 transition and the changes to the openpyxl and xlrd libraries.
@rdnielsen besides python itself, nothing (& that is exactly the problem). i don't understand this question. probably you don't understand what my problem is? the problem is python changing and expecting deps to be in a different versioned directory than the previous version. and i have no control over the distro updating python to a newer minor version (which i now understand has nothing to do with semantic versioning)
-
R relay@relay.infosec.exchange shared this topic
