Ok, if we're going to bite the bullet and break all the traffic ops client
imports, here's my vote:
traffic_ops/clients/go-to/*.go
traffic_ops/clients/py-to/*.py
This is because the last part of the name of the end directory is, by
convention, the name of the library in go. I'll skip the long
I started a Traffic Control Client in python.
You can find it here:
https://github.com/hbeatty/traffic-control-python
Still needs a lot of work!
Thanks,
Hank
On 06/14/2017 11:35 AM, Scrimo, Robert (Contractor) wrote:
All,
I would like to add a Python Traffic Ops Client to the
How about we leave all of the golang stuff in the client directory and then
add a "python_client" directory (or whatever you want to call it)?
That way we don't break everyone using the client and we still get the
python client in there.
On Thu, Jun 15, 2017 at 8:42 AM, Dan Kirkwood
Also +1 to having more TO clients, and classifying them into
language-specific directories. Other suggestions welcome, though.
For instance, longer term, should we target a "Traffic Control" client,
with sub-modules for each component? Should the code for these clients live
in the
All,
I would like to add a Python Traffic Ops Client to the
‘apache/incubator-trafficcontrol’ repository but while I am in there I should
probably re-organize the golang client that resides in there too. This will
most definitely break other code dependent on its current location, which is
