Maybe support PyPy using cpyext?
- Lingua principale
- Julia
- Stelle
- 1.5k
- Fork
- 186
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
Maybe this is helping:
https://doc.pypy.org/en/latest/release-v7.3.1.html
>Conda Forge now supports PyPy as a python interpreter.
I'm not pushing for this (it's not high-priority, would only make faster, maybe more secure), I just noticed they use UTF-8 (and CPython does Unicode, still, differently), like Julia so might be a no-copy to/from Python if it's PyPy.
Even if we do not do this, their UTF-8 implementation is intriguing with optional O(1) indexing, into variable length UTF-8 (something Julia should consider doing, possibly PyPy [code] could help?).
https://doc.pypy.org/en/latest/faq.html#what-about-numpy-numpypy-micronumpy
Depending on status of this, PyPy could be safer:
https://doc.pypy.org/en/latest/sandbox.html
I think they also use ordered Dicts, not sure (either way should work, with it we need to consider changing PyCall, need to anyway, see my other issue on that):
https://twitter.com/pypyproject/status/942070907715182592?lang=en
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
Start by reading the linked PyPy release notes, cpyext documentation, FAQ, and sandbox documentation, then compare their Unicode, NumPy, and dictionary behavior with PyCall's current assumptions. Done would require a defined PyPy support plan, including compatibility and safety boundaries, rather than only confirming that PyPy uses UTF-8.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- julia, python
- Ambito
- backend
- Tipo di issue
- Funzionalità
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 20/100