You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the issue and excitement to work on this! Before getting too far, I think we should have a discussion of whether we'd like the csv library to be part of the standard library (like it is in Python) or a stand-alone, separate library like in Rust.
In general, I see there's a lot of interest in leaning into building Mojo-equivalent of popular Python packages. I think this is great, but we also want to be mindful that we're starting to lean in more with Python bindings to not require this sort of wholesale approach of using Mojo. We'll share more details on that soon, but this will help posit the standard library's positioning on module evolution compared to the Python ecosystem.
Review Mojo's priorities
What is your request?
Implement the Mojo equivalent to Python's csv module
What is your motivation for this change?
I want Mojo's stdlib to match Python's one to attract Python programmers and ease migration.
Any other details?
No response
The text was updated successfully, but these errors were encountered: