Closed marthacryan closed 3 months ago
Oh I'm also noticing that there is no setup-tests.py
file but that's the actual command in the package.json. Not sure if other people agree but I found that very confusing and I was looking for a file called setup-tests.py
. Why wouldn't we call it something like setup-python-tests
?
Also: should we be including specific virtual environment instructions? I use conda right now so I haven't tested whether it actually works with venv, but I would expect people to use their preferred python env. We could link to the docs for venv and conda instead?
Also: should we be including specific virtual environment instructions? I use conda right now so I haven't tested whether it actually works with venv, but I would expect people to use their preferred python env. We could link to the docs for venv and conda instead?
We could say something along the lines of "instructions provided here for venv
but you can use your preferred Python virtual environment manager (e.g. conda
)".
I'm also OK with leaving as-is for now since the venv
instructions were already there and you're just reformatting.
Nice updates here! :confetti_ball:
Any chance of helping get https://github.com/plotly/dash/pull/2893 over the finish line since you're in the neighborhood?
Updates the CONTRIBUTING.md file to split out a large list of bash commands separated by comments into smaller code chunks separated by text. This is easier to read because the comments blend in with the bash commands.