Dave Rawks
Dave Rawks
It's sort of disappointing that adopting a protocol compliant parser which, by all appearances, causes only a very small performance regression in favor of much more easy to read/understand/maintain parser...
Happy birthday to this issue! @sleepybishop any chance you've worked on this at all?
In the meantime the 0.8.0 "release" builds "0.7.1" which seems not very "releasy" ;)
Any word on when this might happen? I see it was marked with some labels shortly after being posted back in February
> Yeah, this is good - I expect this might end up dropping TypeScript support for folks - any chance that dependency can be added manually to the build process....
> Perhaps it can be added inside the dockerfile? Gotcha, I can do that
That was my fault, I switched computers on my last update and accidentally rebased on my own fork which has dependabot enabled. Apologies.
I just tested and it looks like yumsync respects `http_proxy` and `https_proxy` from the environment as long as your underlying libcurl and urllib2 from the executing python respect those vars....
This feature would be great, however all of the last several messages in this issue direct to resources off site and or refer to various commercial support contracts and/or tangental...
I suppose it could, but I really like the code being a sort of general lru for file-like objects. It's the classic generic container problem of go.