intake / intake/python-snappy

Use Rust implementation instead?

Ouverte
#91 4 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
Langage dominant
Python
Étoiles
490
Forks
104
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

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:

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
c, python, rust
Domaine
backend, build-system
Type d'issue
Fonctionnalité
Difficulté
4/5
Temps estimé
3-5 jours
Activité
À l'abandon
Clarté
À clarifier
Accessibilité débutants
25/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.