https://github.com/haozeke/f2py_derived_nep

Derived type examples and design
https://github.com/haozeke/f2py_derived_nep

Last synced: 22 days ago
JSON representation

Derived type examples and design

• Host: GitHub
• URL: https://github.com/haozeke/f2py_derived_nep
• Owner: HaoZeke
• License: mit
• Created: 2022-03-18T09:51:35.000Z (over 2 years ago)
• Default Branch: main
• Last Pushed: 2023-11-12T23:29:43.000Z (12 months ago)
• Last Synced: 2023-11-13T00:24:31.223Z (12 months ago)
• Size: 92.8 KB
• Stars: 3
• Watchers: 2
• Forks: 0
• Open Issues: 9
• Metadata Files:
  • Readme: readme.org
  • License: LICENSE

Awesome Lists containing this project

README

        
* About

This repository contains self contained examples along with the draft ~NEP~ for

Fortran Derived Types. Changes to the text of the draft file:doc/nep_draft.rst should

ideally be accompanied by examples (and instructions to run them).

For details on the NEP process consult the [[https://numpy.org/neps/nep-0000.html][NumPy documentation]].

** Contributing

All contributions are welcome.

- Concrete implementations --> Pull Requests

- Thoughts / comments / ideas --> as review comments or issues

- Edge cases / examples --> ~examples~ folder

*** Writing bindings

For each example, bindings should utilize the FortranObject files (a copy of

which are provided within this repository).

** FAQ

*** Why a repo?

Large parts of this NEP involve Fortran-C-CPython binding strategies, but implementations within NumPy will require F2PY changes. This does not make for very intuitive PRs and so the design is discussed here before examples are implemented within F2PY.

Essentially, each decision can be split into:

1. Testing / discussing the ~C~ code

2. Generating the ~C~ code with F2PY

This repository is meant to facilitate 1. while PRs to ~numpy/numpy~ must implement both.