Andreas Stenius
Andreas Stenius
This hit me again in another project.. ;) And yea, the "known first party" config option seems like a reasonable way to resolve this. Putting it in a generated isort...
I'm not sure if I tried with the "known first party" config option. I only tried the "src paths" one, from what I can read in my issue/PR. The suggested...
@thejcannon how do you capture that trace?
How would this work, technically? As `setup_py()` (or, `python_artifact()` which I'd actually prefer to use, from now on) accepts any fields on it (`**kwargs`) but the target `python_distribution()` is not...
But I get the nagging feeling that we simply rename stuff, that way... hmm.. but maybe not so bad after all, if `provides` would become `extra_kwargs` or `additional_kwargs`, and the...
On a second thought on the field name for those extra args.. what it would look like when used, I think simply `setup` might fit well.. ```python python_distribution( name="my-distro", version="1.2.4",...
I felt like it was a little too simple, so I ran a little test in the example-docker repo to increase my confidence in that my test tested the right...
@stevepentland merged today it would go into 2.14.0. I've been away for a while, so not sure in what phase the 2.14 dev cycle is right now, but I guess...
@Eric-Arellano thx 🙏🏽
I see your reasoning for this. I don't know if there's a "cron standard" that dictates what is right or wrong here, but could I suggest to translate a non-range...