On Thu, Mar 24, 2016 at 4:14 PM, Ben Pfaff <b...@ovn.org> wrote: > On Thu, Mar 24, 2016 at 03:35:33PM -0400, Russell Bryant wrote: > > I think the python directory should be limited to what we consider the > ovs > > Python library. That's largely what it is, except for the build/ and > > ovstest/ directories. > > Going off on a tangent: should those be somewhere else, then, too? I > don't know Python norms very well. >
Ideally, yes. I just never got around to it. I think we should view the python/ directory as something that we could split out into another git repo and distribute independently as "python-ovs". There have been occasions that I wished we could make Python lib releases more frequently than ovs itself. The structure I'd expect for such a thing is roughly what's there, minus the build/ and ovstest/ directories: - ovs/ directory, containing all code for the "ovs" Python library - setup.py - README and friends - other directories directly related to and in support of the ovs/ library, like docs or CI scripts and configs -- Russell Bryant _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
