These are chat archives for cherrypy/cherrypy

15th
Apr 2018
Sviatoslav Sydorenko
@webknjaz
Apr 15 2018 08:50 UTC
well, i don't yet have in on my computers, only phone and mobile app doesn't support browsing files. but i'll get it at some point.
i'm thinking of using email with tag
Sviatoslav Sydorenko
@webknjaz
Apr 15 2018 09:03 UTC
@jaraco cherrypy/cheroot@26313a8 this enabled GitHub to show additional CoC links in the right panel's "Helpful links" section when creating issue or PR.
I think, we should also link it in README and docs.
Sviatoslav Sydorenko
@webknjaz
Apr 15 2018 11:07 UTC
@jaraco to be on the same page, do you still want to revert cherrypy/cheroot#85 after my explanations?
Jason R. Coombs
@jaraco
Apr 15 2018 12:22 UTC
My feeling is if a system packager requires different builds of a package for Python 2 and Python 3, it’s the responsibility of that system to provide packages for each. And it definitely shouldn’t be the responsibility of intermediate packages like CherryPy (or the unbounded potential others) to facilitate the filtering of these. The packages are designed to be required and possibly imported on Python 3, so should be included for simplicity.
But if you’re not convinced, or you think their use case trumps ours, then we should leave it merged.
Sviatoslav Sydorenko
@webknjaz
Apr 15 2018 20:10 UTC
@jaraco I do not care a lot since we never announced this kind of packaging support
Sviatoslav Sydorenko
@webknjaz
Apr 15 2018 20:21 UTC
@jaraco it looks like there's some issues with that email +tag. Could you please check what I forwarded you?