List view
- No due date
- No due date•19/19 issues closed
- No due date•7/12 issues closed
It should be possible to use imap-codec from Python. The challenge is to define a Pythonic API (including well-designed Python types) that aligns with imap-codec's principles, such as misuse-resistance and correctness. Newer versions of Python (>3.10) support stronger typing that could help define a robust API. That's why we aim to support Python 3.10 but will take all possibilities to further increase compatibility. We must also answer how to make imap-codec easily accessible through Python and distribute imap-codec. Furthermore, we must add new CI jobs and initial documentation. The final outcome of this milestone is a pip-installable prototype package similar to IMAPclient¹ based on imap-codec and the higher-level async library. This prototype is a great way to put the required bindings in place and is a usability-first landmark for full-fledged bindings.
Overdue by 1 year(s)•Due by July 31, 2024•25/25 issues closedimap-codec supports common IMAP extensions, such as SASL-IR, LITERAL+, or QUOTA.¹ Still, projects such as Himalaya², meli³, and Aerogramme⁴ may need additional extensions. We want to implement them. The implementation of new extensions will follow the library's principle of misuse-resistance. Furthermore, all extensions will be fuzz-tested subject to randomized structural tests, and the overall test coverage should remain the same due to the inclusion of these new extensions. The extensions will be adequately documented and feature-gated to not break SemVer compatibility. We prioritize IMAP extensions that are actively used. We prioritize extensions improving performance, latency, and data usage. ¹ https://docs.rs/imap-types/latest/imap_types/#supported-imap-extensions ² https://github.com/soywod/himalaya ³ https://meli.delivery/ (uses imap-codec, client) ⁴ https://aerogramme.deuxfleurs.fr/ (uses imap-codec, server)
Overdue by 1 year(s)•Due by July 31, 2024•17/17 issues closed