intake / intake/python-snappy

Use Rust implementation instead?

Offen
#91 4 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Python
Sterne
490
Forks
104
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

Hi there!

I was curious if you'd be open to having the [Rust implementation of snappy](https://github.com/BurntSushi/rust-snappy) instead of the C dependency which can lead to troubles, especially when using `python-snappy` in environments like AWS Lambda?

I've made [cramjam](https://github.com/milesgranger/pyrus-cramjam) which does just this but would be willing to attempt migrating this project in a similar way. It wouldn't require any system dependencies and packing them in a wheel (OSX, Linux & Windows supported), of course, wouldn't require any compiler for the user. As it is right now, `cramjam` which includes snappy results in about ~1.5MB for linux wheels.

Anyway, let me know what you think and I'd be willing to start messing around with it. :+1:

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Rechercherichtung

No project files or tests are named. Start by reviewing how python-snappy currently declares and builds its C dependency, then compare the linked Rust implementation and cramjam approach. Done would require an agreed migration scope and confirmation that supported macOS, Linux, and Windows wheels need neither system dependencies nor a user compiler.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
c, python, rust
Bereich
backend, build-system
Issue-Typ
Feature
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Veraltet
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
25/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.