Xavier Olive

[Attached](https://github.com/user-attachments/files/19361918/tunnel.rs.txt) is a draft of my (working) implementation. It was not direct (you don't code AsyncRead/AsyncWrite traits yourself every day...), so I guess it would be helpful to other users,...

Thank you for the feedback :) Looking forward to seeing how you will adapt it! Please keep me posted In the meantime there are two other things I'm contemplating adding:...

Thank you, the commit looks reasonable to me. Happy to see I somehow contributed :) If you want to release before my feedback, go ahead (and close the issue). I...

Forced release by CI, was cheap to try: it works! :) Will look into the rest later

Yes I reached the same conclusion: - on most architectures you will see _eccodes.cc and _eccodes.cpython-313-x86_64-linux-gnu.so or _eccodes.cpython-313-darwin.so - on Linux/aarch64 seems not supported so falls back to a version...

No, not yet, I finished working on it late yesterday... I think the best way I have in mind is to compile a version of eccodes for aarch64 on a...

Few thoughts: - it is easy to get those columns when you build a query using the flight table (and usually, filter flights based on origin/destination), because you first get...

> See [comment on issue #87](https://github.com/open-aviation/pyopensky/issues/87#issuecomment-2149092210) for a solution to the request to retrieve the (estimated) aerodrome of departure and destination like in the old API. This works in your...

Thank you for the feedback @raph-p I will try to reply to all items, there are a lot of comments in your message: - dataframes behind Flight and Traffic structures...

I am not really sure, I had issues in the past when settings the engine explicitly. Maybe it would be smarter in general (in the whole code base) to add...