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 rant about
precisely how much I do or don't like it, but it means you'll use it like
this:
import `
github.com/apache/incubator-trafficcontrol/traffic_ops/clients/go-to`
func foo() {
to.DoThings()
}
Half the time I see the import overriden as "to" anyway. Note, we'd need to
update the package line to be "package to" in the folder.
golang.org/x/tools/cmd/gorename may be of use for the transition.
On Thu, Jun 15, 2017 at 9:16 AM, Hank Beatty <[email protected]> wrote:
> 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
>> ‘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 the root of the client directory. I am proposing to
>> move the golang code to a newly created ‘golang’ directory and add a
>> ‘python’ directory for my Python client. I will fix any references to code
>> using the client from within the ‘incubator-trafficcontrol’ repository. If
>> anyone has any insight/objections/comments about this please respond. I
>> will take your silence as approval...
>>
>> Thank you,
>> -Robert
>>
>>
