-
Notifications
You must be signed in to change notification settings - Fork 2
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
Merge develop into main, for release (2.0.0) #300
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1. module paths 2. new version number in pyproject.toml 3. location of test script
Co-authored-by: Matthew Thompson <[email protected]>
…-installable Make mepo a pip-installable Python project
Fix small typo
* Code reorganization to address #273 * Fixed issues with renaming config_file as registry * Removed a print statement left in by mistake * On our way to more robust testing * Added nocolor option to 'git branch list' * It's enough to chdir to the fixture dir at the beginning of a test * Added 'mepo branch' tests * Added tests for mepo tag, fetch, pull, pull-all * multiprocessing library supports the context management protocol * Added tests for mepo push, diff, whereis and reset * component.py - using Python3's relative import * Suppressing test outputs to terminal * Turning off testing 'mepo reset' and checking why 'mepo diff' is failing Maybe 'mepo reset' is causing issues with testing 'mepo tag create' * For testing 'mepo diff', ignore the last line '---' * Ignore the last line of both stdout and saved outputs * Escaping the string message of 'git tag create' * Create regular (non-annotated) tag instead * Testing 'mepo reset' is back on - this was not the issue * Code from src/mepo/command/command.py included in src/mepo/__main__.py * Small edits * Updated GEOSfvdycore version for testing * Minor quote changes * Using SimpleNamespace to construct arguments to mepo commands * Multiprocessing lib supports context manager protocol * Removed tests/input/args.py - using SimpleNamespace now * Updated README and CHANGELOG * Moved duplicate code to get GIT_EDITOR, in commit.py and tag_create.py, to git.py * Lint code as part of GitHub actions workflow only for the case where OS is ubuntu-latest and Python version is 3.9 * Added __init__.py in cmdline, command and utilities directories * Linting updates 1. Linting is a separate job now 2. Disabling some error codes, for now 3. Always return a zero status code * Hardcoding Python version * Renaming * Adding ability to create a mepo binary that can uploaded as an artifact of a Github actions workflow. Pyinstaller requires that the top level script not use relative imports * Added fix for reading mepo1 state * Added a mepo command, update-state, to permanently update mepo1 state to mepo2 * Formatting changes to update-state.py * Slightly different printable representation of component * Added an optional argument one-per-line for 'list' * component.py::MepoComponent - renamed to_dict to to_registry_format. Added to_dict * Fixed test test_list * Fixed a bug in update-state - need to switch to the fixture dir first * Implemented a context manager for os.chdir * Reformatted using black * Separate GitHub workflows for running linter and formatter * Added black to requirements * Using poetry to manage dependencies and packaging * Added creation of a top level script to build * Added pylint as (poetry) dependency * Added pylint to requirements.txt * Updated pyproject.toml * Small changes to the test script for consistency in mepo commands * Enabled previously disabled Pylint (C)onvention and (E)rror codes * Added directory containing mepo to PYTHONPATH * Using contextlib.redirect_stdout instead * Can't switch to contextlib.chdir as this exists only in 3.11+ * Run 'black --check' instead. Non-zero return code indicates that some files need to be formatted * Formatted using black * Config file is now called registry * Moved fixture/component validation from MepoComponent to Registry * Reformat using black * Switched from pkl state file to json * print() has a flush argument * Trivial changes * If mepo1 style state, print warning to run 'mepo update-state'. Updated update-state code. * Removing hashes from requirements.txt * Fixed bug in string formatting * Update comment in registry.py * Store full path to the fixture dir in state file * Revert "Store full path to the fixture dir in state file". We want relocability. This reverts commit 1bc8330. * Local path saved to state file is relative to fixture directory
* Switch from poetry to rye (#287) * mdutils is a production requirement * pyproject.toml - packages for sdist and wheel builds * Getting hatch to build mepo wheel correctly * Updated CHANGELOG.md * Added colorama as a dependency. Updated tests * Made linter a little happier
* Added pre-commit hook to run Black * Removed unused imports etc.
…lowing the codepath for the case when mepo state does not exist. (#295)
…#296) * Another, hopefully last, bug with old-style state fixed - Convert the local path of the repos from relative to absolute after reading the state, in case of old-style state as well * Running 'mepo status' on a mac seems to cause issues for the case of an old style state. Somehow the patch to read the old style state, modification of sys.modules, does not percolate down to the processes spawned by multiprocessing. To work around this issue, added a '--serial' option to the status command. * Same issue with 'mepo restore-state' as we experienced with 'mepo status' earlier (81020ef). To work around this issue, added a '--serial' option. * Updated test to account for new option (--serial) for status and restore-state
* Ready to release 2.0.0 * Updated CHANGELOG.md --------- Co-authored-by: Matt Thompson <[email protected]>
mathomp4
approved these changes
Aug 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.