intake / intake/python-snappy

Use Rust implementation instead?

Abierto
#91 4 comentarios 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
Python
Estrellas
490
Forks
104
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

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:

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
c, python, rust
Área
backend, build-system
Tipo de issue
Nueva funcionalidad
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Necesita aclaración
Aptitud para principiantes
25/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.