Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

Your target breaks via action at a distance

...because it is step one toward parsing dependencies rather than declaring them

when the dep-provider removes the dep later

So - at the end of the day I think this usually boils down to correct vs convenient arguments

And Stu's point gets towards not having to compromise in either direction

ps: <@U07J10LLW> is working with <@U054MQUPL> on the server atm

FWIW, go support currently hits correct and convenient

Because of go itself, which enforces this with a simple scheme and fast tools

Ah - sorry <@U07J10LLW> read personally and inserted don't personally

I'm too expecting folks going the other way, need to unlearn my prejudices

Yeah <@U06A03HV1> completely don't see what type inference has to do with anything but import statements in java

<@U053H6LQS>: that's unfortunate,   <@U06A03HV1> do you have any ideas?

<@U098ZNTCN>: how about instead of expecting a list, it expects a dictionary; then the key in said dict containing the list of servers is parameterizable via options with some sane default (e.g. ‘host_list’).

At that point why not just an option pointing to a fqcn of a strategy interface

this would be wrapped as part of the ‘rest’ strategy

(afaik there’s already a strategy interface planned?)

Just saying REST loses meaning at this point if you call get_list() that may be backed with - who knows, maybe rest, maybe not

GoFetch uses Fetchers with pluggableness like this fwiw

sure, rest probably a bad name - ‘json’ perhaps more appropriate

Just saying if there is an interface it could return a native python type

and who cares if that was slurped in from JSON

It just sounded like things were headed all knobby, but 1/2 way

Questining whther it should just go all the way

I thought that was all already there tho, at least in plan

I’m just saying specifically for the generic JSON-API strategy (which under the hood should use something like HostMap etc), the best interface might be to extract a named key from the received JSON dict