The current version (Jul 2021) still demonstrates issues with nonstandard type declarations (see https://github.com/mdolab/pyfriction/pull/34 for some discussion). These issues will be solved locally per repo through a postprocessing step. The current version requres a very recent GLIBC, meaning that tapenade might not run on older platforms, e.g., U20.
This PR updates the pinned tapenade version to the latest released (Aug 2023).
Expected time until merged
1 day
Type of change
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (non-backwards-compatible fix or feature)
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Documentation update
[x] Maintenance update
[ ] Other (please describe)
Testing
Checklist
[ ] I have run flake8 and black to make sure the Python code adheres to PEP-8 and is consistently formatted
[ ] I have formatted the Fortran code with fprettify or C/C++ code with clang-format as applicable
[ ] I have run unit and regression tests which pass locally with my changes
[ ] I have added new tests that prove my fix is effective or that my feature works
Purpose
The current version (Jul 2021) still demonstrates issues with nonstandard type declarations (see https://github.com/mdolab/pyfriction/pull/34 for some discussion). These issues will be solved locally per repo through a postprocessing step. The current version requres a very recent
GLIBC
, meaning that tapenade might not run on older platforms, e.g., U20.This PR updates the pinned tapenade version to the latest released (Aug 2023).
Expected time until merged
1 day
Type of change
Testing
Checklist
flake8
andblack
to make sure the Python code adheres to PEP-8 and is consistently formattedfprettify
or C/C++ code withclang-format
as applicable