Support linking to Pyston rather than CPython
- Lenguaje dominante
- Julia
- Estrellas
- 1.5k
- Forks
- 186
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
I'm not putting any pressure on supporting Pyston [or any other JIT Python], just think of this as a FYI on the interesting thing I discovered; the read on e.g. ref counting vs. former full GC.
[It seems Numba is supported now: https://github.com/stevengj/PyCall.jl/issues/220
I wander if other than Numba JIT, such as Pyston, or more than one JIT Python implementation, is a good idea to support.]
https://blog.pyston.org/2016/05/25/pyston-0-5-released/
"Pyston is now using reference counting.
[..]
We used a GC initially to try to get more performance. But applying a tracing GC to a refcounting C API, such as the one that Python has, is risky and comes with many performance pitfalls. And most challengingly, Pyston wants to support the large amount of code that has been written that relies on the special properties that refcounting provides (predictable immediate destruction). We found that we had to go to greater and greater lengths to support these programs
[..]
We are very happy to announce: we can run NumPy, unmodified."
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Línea de trabajo
El issue menciona PyCall.jl y Pyston, y enlaza a la publicación del lanzamiento de Pyston 0.5 y al issue #220 de PyCall sobre Numba. Empieza revisando esas referencias y el enfoque actual para enlazar con CPython; para darlo por terminado harían falta un plan de compatibilidad concreto y el acuerdo de los maintainers.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- julia, python
- Área
- backend
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 25/100