Skip to content

Python "FutureWarnings" in EE2 Standards #19

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.

Sign up for GitHub

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

Open
AliciaBentley-NOAA wants to merge 4 commits into
base: develop
Choose a base branch
from
Open

Python "FutureWarnings" in EE2 Standards #19

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
9d9b847
Allow Python FutureWarnings in EE2 standards
Jan 6, 2026
6fe5a9b
Adding context
Jan 6, 2026
17029e5
Adding definition of a FutureWarning
Jan 6, 2026
52cc8a4
Move FutureWarning standard to Standards section C
Jan 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/standards.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -623,6 +623,7 @@ Please also observe the following points:
* All packages that use Python scripts must specify a Python version through the module system, and must only call a Python executable that is from a module, not the system version.
* "``module load python/${python_ver:?}``" or similar must be present in all job files that will lead to python script calls, where the python version is defined in the version file.
* Python version must be at version 3 or higher.
* Python “FutureWarning” messages indicate that a specific feature, function, or syntax that is currently being used will be changed or removed in a future version of Python or in a future version of a Python library. Python “FutureWarning” messages are acceptable messages in operations and should not be suppressed. Developers should make an effort to resolve “FutureWarning” messages, when possible, in order to prevent production jobs from failing in the future.

Reference `Appendix A: Workflow Examples`_ for commented examples of a version file, ecFlow script, J-job, ex-script, modulefile and makefile.

Expand Down Expand Up @@ -1211,4 +1212,4 @@ Appendix B: Variables and Directory Structure Tables
"``$DCOMROOT/YYYYMMDD/bTTT/xxSSS``","BUFR data tanks"


*TTT* and *SSS* correspond to the 3-digit BUFR data category type and sub-type, respectively
*TTT* and *SSS* correspond to the 3-digit BUFR data category type and sub-type, respectively