Log file Viewer

[12:12:11] <dstufft> tomprince: https://github.com/pypa/pip/pull/2749

[21:29:01] <lifeless> dstufft: does 'packaging' have a stable API ? e.g. is it semver?

[21:30:47] <dstufft> It uses YY.N release numbers

[21:31:20] <lifeless> so, so serials... but API stability?

[21:31:43] <lifeless> if we used it somewhere, will it break suddenly, or is there a commitment to compat?

[21:32:44] <lifeless> the context is I'm considering using it from a tool in openstack, and a concern has been raised about api stability there

[21:33:39] <dstufft> It doesn't really have a defined policy, probably it should. Pretty much it's "while we're figuring out an API and functionality for a new feature we might cut a release and then break it in the next release, but once it settles down it's not breakable". If someone other than pip/setuptools is going to use it, that's probably best encoded as new APIs are added with a provisional status until the major stakeholders have made sure it functions

[21:33:40] <dstufft> for them

[21:34:08] <dstufft> but like, I wouldn't break API compatability for the APIs that are there since they are known to be workable now

[21:35:08] <dstufft> lifeless: I'm happy to have a defined policy fwiw

[21:35:13] <dstufft> I just hadn't bothered yet

[21:35:26] <dstufft> the intent is that projects like openstack can consume this without worry

[21:36:25] <lifeless> so yeah

[21:36:34] <lifeless> the initial thing would be packaging.version.parse

[21:36:42] <lifeless> documenting that as supported indefinitely would be nice

[21:40:09] <dstufft> lifeless: I'll probably just document it that anything documented that isn't explicitly marked provisional is supported indefinitely

[22:02:59] <lifeless> yak shave. sigh