Make aerosandbox.numpy a standalone repository

[cdhainaut]

Hi,

I have been using Aerosandbox in my projects and find the aerosandbox.numpy library particularly valuable for handling CasADi and NumPy interactions seamlessly. I have noticed that when starting a new project, there is often a dilemma of whether to make a copy of aerosandbox.numpy or depend on the entire Aerosandbox ecosystem when I only need aerosandbox.numpy. I believe that this functionality could benefit a broader audience if offered as a standalone library.

Proposal

I would like to suggest the creation of a separate repository to house the aerosandbox.numpy library independently. This would allow users to utilize the powerful capabilities of aerosandbox.numpy in various projects without necessarily depending on the entirety of the Aerosandbox ecosystem (e.g., aerodynamics, structure, etc.).

Benefits

1. Increased Flexibility: By having aerosandbox.numpy as a standalone library, users can easily integrate it into projects with diverse requirements, providing greater flexibility in usage.
2. Broader Adoption: A standalone aerosandbox.numpy could attract a wider user base, including those working on projects unrelated to aerodynamics or structural analysis.
3. Ease of Maintenance: Separating aerosandbox.numpy from the main Aerosandbox repository can simplify maintenance and updates, making it more agile and adaptable to evolving needs.
4. Streamlined Project Initialization: Many users, including myself, often face the decision of either creating a copy of aerosandbox.numpy or depending on the entire Aerosandbox ecosystem when starting a new project. A standalone aerosandbox.numpy would offer a solution to this dilemma.

I would be happy to contribute to the creation and maintenance of this standalone repository. I believe it could enhance the overall Aerosandbox ecosystem and make this powerful tool even more accessible to the community.

Looking forward to hearing your thoughts.

[cdhainaut]

@peterdsharpe, any thoughts on this ?