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

import metplotpy.contributed... instead of relative import #478

Open
14 tasks
ahijevyc opened this issue Dec 17, 2024 · 0 comments · May be fixed by #479
Open
14 tasks

import metplotpy.contributed... instead of relative import #478

ahijevyc opened this issue Dec 17, 2024 · 0 comments · May be fixed by #479
Assignees
Labels
priority: low Low Priority type: bug Fix something that is not working

Comments

@ahijevyc
Copy link
Contributor

Replace italics below with details for this issue.

Describe the Problem

when running program it complains about relative import

python planview_fv3.py -h
Traceback (most recent call last):
  File "/glade/derecho/scratch/ahijevyc/METplotpy/metplotpy/contributed/fv3_physics_tend/planview_fv3.py", line 11, in <module>
    from . import physics_tend
ImportError: attempted relative import with no known parent package

Expected Behavior

Show help page.

Environment

Describe your runtime environment:

  1. Machine: casper login node
  2. conda environment with metplotpy 2.1.0 installed

To Reproduce

Describe the steps to reproduce the behavior:

  1. Follow instructions in https://metplotpy.readthedocs.io/en/latest/Users_Guide/fv3_physics.html
  2. setenv METPLOTPY_BASE
  3. Scroll down to 'Run from the Command Line' and run commands listed there.

Relevant Deadlines

June 2025 grant runs out

Funding Source

NOAA JTTI UFS

Define the Metadata

Bugfix Checklist

See the METplus Workflow for details.

  • Complete the issue definition above, including the Time Estimate and Funding Source.
  • Fork this repository or create a branch of main_<Version>.
    Branch name: bugfix_<Issue Number>_main_<Version>_<Description>
  • Fix the bug and test your changes.
  • Add/update log messages for easier debugging.
  • Add/update unit tests.
  • Add/update documentation.
  • Add any new Python packages to the METplus Components Python Requirements table.
  • Push local changes to GitHub.
  • Submit a pull request to merge into main_<Version>.
    Pull request: bugfix <Issue Number> main_<Version> <Description>
  • Define the pull request metadata, as permissions allow.
    Select: Reviewer(s) and Development issue
    Select: Milestone as the next bugfix version
    Select: Coordinated METplus-X.Y Support project for support of the current coordinated release
  • Iterate until the reviewer(s) accept and merge your changes.
  • Delete your fork or branch.
  • Complete the steps above to fix the bug on the develop branch.
    Branch name: bugfix_<Issue Number>_develop_<Description>
    Pull request: bugfix <Issue Number> develop <Description>
    Select: Reviewer(s) and Development issue
    Select: Milestone as the next official version
    Select: METplotpy-X.Y.Z Development project for development toward the next official release
  • Close this issue.
@ahijevyc ahijevyc added type: bug Fix something that is not working priority: low Low Priority labels Dec 17, 2024
@ahijevyc ahijevyc self-assigned this Dec 17, 2024
@ahijevyc ahijevyc linked a pull request Dec 17, 2024 that will close this issue
10 tasks
@ahijevyc ahijevyc removed a link to a pull request Dec 17, 2024
10 tasks
@ahijevyc ahijevyc linked a pull request Dec 17, 2024 that will close this issue
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: low Low Priority type: bug Fix something that is not working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant