Closed cadenmyers13 closed 1 month ago
looks good, thanks so much!
some things I see:
- delete LICENSE.txt (its replaced with the LICENSE.rst)
- please merge the old README.md into the README.rst and delete the old README.md
- check through the README for broken links and missing things
- I think the
bg_mpl_stylesheet/__init__.py
needs to be updated. We are not using hard-coded version numbers any more. It should have been replaced with a cookiecutter generated version.- if possible, build the docs and see what they look like....
- delet requirements/README.txt when you have read and done everything
- delete setup.py
- fix init in src (see how it is handled in diffpy.pdfmorph for example)
- remove bg_mpl_stylesheet tree after checking it has all been moved to
src/bg-mpl-stylesheet
tree- remove everything except
bg-mpl-stylesheets
and__init__.py
fromsrc
Make sure to test things after all this work. Make an env of a program that imports the stylesheet currently and verify it works (I think pdfmorph does?) then make a new env that installs the stylesheet from your new branch and make sure nothing breaks, something like that.
Are LICENSE.txt and README.md not removed in this? Same with setup.py. When i look in 'files changed' it looks likes they've been deleted.
@sbillinge In the "Support and Contribute" section of the README, the cookiecutter put information about diffpy. Since this not a diffpy package I assume we don't want this. Is there something you'd like me replace this with?
I made the init.py files dynamic by coping the format in src/bg-mpl-stylesheets/__init__.py
.
@sbillinge Okay, I made all the suggested edits. I ran pip install .
and it install successfully. The only things I feel shaky on are the init.py files i edited in the above commits. Also, check the above comment i tagged you in regarding the README.rst. Let me know if anything else needs to be done!
Please don't force-push. I don't really want to merge anything with a force-push, it is too dangerous. Why are you force-pushing?
@cadenmyers13 this PR is getting a bit messy. I wonder if we should make use of what we learned in the process, and just start over.... I think it could go quickly and we would be more satisfied with the outcome. Perhaps we can do a PR that does the pre-commit things before the cookiecutter, following the new instructions?
@cadenmyers13 this PR is getting a bit messy. I wonder if we should make use of what we learned in the process, and just start over.... I think it could go quickly and we would be more satisfied with the outcome. Perhaps we can do a PR that does the pre-commit things before the cookiecutter, following the new instructions?
I agree especially since I've done it once by myself. I will start fresh.
Messed up in editing the README.rst... working on fixing things