If you're lazy, you could distribute the server package to everyone
and just make sure that if someone tries to import it on python 2 then
they get a useful error.
On Thu, Apr 26, 2018 at 9:17 AM, Skip Montanaro
wrote:
> Yeah, splitting client and server packages is on
Yeah, splitting client and server packages is on my to-do list. Was
just hoping to keep Python2 users from shooting themselves in the foot
with a server subpackage which wouldn't work.
S
On Thu, Apr 26, 2018 at 10:59 AM, Chris Barker wrote:
> frankly, I'd give up n
frankly, I'd give up n find_packages -- it's not that magic, it's just a
convenience function so you don't need to hand-specify them.
But in this case, you're doing something weird, so I"d just be explicit.
Though what I'd probably really do is make the client and server completely
separate