Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestions for development workflow #3

Closed
sgbaird opened this issue Aug 12, 2021 · 2 comments
Closed

Suggestions for development workflow #3

sgbaird opened this issue Aug 12, 2021 · 2 comments

Comments

@sgbaird
Copy link

sgbaird commented Aug 12, 2021

I'm trying to add a function for which I plan to submit a pull request, but I'm having some trouble with the workflow for developing. For example, I can use pip install -e . after cloning, or python setup.py install, etc. but I've been running into odd errors like the computation seeming to stall out. I was wondering what your workflow is and what you would suggest.

@sgbaird
Copy link
Author

sgbaird commented Aug 14, 2021

I think I've got a reasonable workflow in Spyder with the working directory being the directory of a local copy of a forked repository of ElM2D. If I make changes, then it seems to reflect automatically when I run a test script (see #1).

@sgbaird sgbaird changed the title Suggestions for development Suggestions for development workflow Aug 14, 2021
@SurgeArrester
Copy link
Collaborator

Typically I make my changes to the file then once it's working run python setup.py install to check, push to git/pip then double check it by pip installing the latest in a separate python environment, I'm not sure why the computation would stall out though sorry

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants