Abhinav Singh

I usually start proxy locally using this command and looks like it is broken currently. Unsure how tests were working. May be because they had a `_scm_version` generated file. But...

> I usually start proxy locally using this command and looks like it is broken currently. Unsure how tests were working. May be because they had a `_scm_version` generated file....

You mentioned `sphinx` at some point and today I am thinking of having a Wiki/Doc site (probably via GitHub pages). One key reason is the growing `README`. Among other things,...

> I guess you happen to have that one dependency by accident but the normal contributor workflow is to install the deps after cloning the repo Correct, I had `setuptools-scm`...

> It will also build a copy of the docs site for each PR allowing previews of the changes. This will be awesome > I can send a PR with...

> https://packaging.python.org/guides/distributing-packages-using-setuptools/#working-in-development-mode. There's no reason to reinvent the wheel only to maintain own set of scripts that the whole Python ecosystem is unfamiliar with and each person would have to...

> FWIW I recommend getting familiar with RST. Did you know Sphinx was originally invented for upstream docs.python.org? > And now it's a de-facto standard within Python projects. Right, now...

> > Apologies, this was a mistake. I checked logs for upload artifacts by mistake and got confused. I have submitted #741 which should now enable test.pypi.org releases

Observing `lib` workflows are failing after PR merges with `Unable to find any artifact` error.

> Like `2.4.0a0`, for example. Just to test the automation and when the thing gets released on PyPI, the users wouldn't get it automatically by mistake Good point. I am...