Dataset Viewer
repo
stringlengths 8
83
| topic
stringclasses 417
values | issue_number
int64 1
203k
| title
stringlengths 1
1.01k
| problem_statement
stringlengths 0
261k
| state
stringclasses 2
values | created_at
stringlengths 20
20
| updated_at
stringlengths 20
20
| url
stringlengths 36
111
| labels
sequencelengths 0
15
| user_login
stringlengths 2
39
| comments_count
int64 0
2.05k
|
|---|---|---|---|---|---|---|---|---|---|---|---|
TkTech/pysimdjson | python-bindings | 125 | troubleshooting dangling proxy objects | Hello, I was just troubleshooting this following strange situation:
``` python
async def reaper():
reaper_simdjson_parser = simdjson.Parser()
while True:
await asyncio.sleep(1)
text = await get_json_payload()
doc = reaper_simdjson_parser.parse(text)
*results, status = doc
for x in results:
# do something
# del x # forgetting to explicitly delete x would cause intermittent problems
del status
del results
del doc
```
the error is this:
```
doc = reaper_simdjson_parser.parse(text)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "simdjson/csimdjson.pyx", line 435, in csimdjson.Parser.parse
RuntimeError: Tried to re-use a parser while simdjson.Object and/or simdjson.Array objects still exist referencing the old parser.
```
Perhaps specifying which reference is dangling may be helpful? At the very least putting it in the documentation as a potential gotcha might be helpful.
Thank you for pysimdjson and simdjson in general. Huge fan. | open | 2025-03-25T14:58:39Z | 2025-03-25T15:26:17Z | https://github.com/TkTech/pysimdjson/issues/125 | [] | memetb | 1 |
TkTech/pysimdjson | python-bindings | 123 | Python 3.13 Binaries | Hi!
Thanks again for the wonderful library and continued support!
I was just wondering if it would be possible to release py3.13 wheels. Some of my users are starting to migrate to 3.13 so I'm just trying to get some of these issues squared away.
Thanks so much!
Will | open | 2025-02-18T22:56:31Z | 2025-02-18T22:56:31Z | https://github.com/TkTech/pysimdjson/issues/123 | [] | william-silversmith | 0 |
TkTech/pysimdjson | python-bindings | 122 | Check for `None` key fails when using `parse` | ### **Issue Description**
When using `simdjson.Parser.parse`, checking if a `None` key exists in the parsed object results in a `TypeError: expected bytes, NoneType found`.
**Example Code:**
```python
import simdjson
parser = simdjson.Parser()
doc = parser.parse(b'{"res": [{"name": "first"}, {"name": "second"}]}')
if not None in doc: # This line raises the error
pass
```
**Error:**
```
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "simdjson/csimdjson.pyx", line 316, in csimdjson.Object.__contains__
TypeError: expected bytes, NoneType found
```
---
### **Expected Behavior**
The check should return `False` (as it does with `simdjson.loads`), since `None` is not a valid JSON key.
**Working Example with `simdjson.loads`:**
```python
import simdjson
doc = simdjson.loads(b'{"res": [{"name": "first"}, {"name": "second"}]}')
if not None in doc: # Correctly returns False
pass
``` | open | 2025-02-13T14:06:40Z | 2025-02-13T14:06:59Z | https://github.com/TkTech/pysimdjson/issues/122 | [] | silentninja | 0 |
TkTech/pysimdjson | python-bindings | 120 | Can pysimdjson parse in streaming mode? | Hello, thank you for your work! I've just started experimenting with this library.
I am attempting to parse larger-than-memory JSON files, and was wondering if pysimdjson supports stream-based parsing of JSON documents (similar to [jsonslicer](https://pypi.org/project/jsonslicer/)) or [ijson](https://pypi.org/project/ijson/))?
I couldn't find anything in the documentation that suggests this, but am hoping there's some way to do this. | closed | 2024-12-12T17:03:52Z | 2024-12-12T18:22:20Z | https://github.com/TkTech/pysimdjson/issues/120 | [] | theogaraj | 2 |
TkTech/pysimdjson | python-bindings | 118 | Add alias to `json.JSONEncoder` to drop-in API. | The docs explicitly call out a [Drop-in API](https://pysimdjson.tkte.ch/dropin.html) which will "just work". This module covers `json.{load,loads,dump,dumps}`, where `{dump,dumps}` are aliased to the built-in module. I propose adding an alias to `json.JSONEncoder` to make the drop-in API more complete. I don't think this should be problematic as one would only use a `JSONEncoder` for the `dump/s` commands, which are already aliased.
In a current project, I have something like this:
```python
from json import JSONEncoder
try:
import simdjson as json
except ImportError:
import json
class CustomEncoder(JSONEncoder):
...
```
If an alias is added, the above snippet would be:
```python
try:
import simdjson as json
except ImportError:
import json
class CustomEncoder(json.JSONEncoder):
...
```
It's a rather minor tweak, but I think it would be nice for developer experience.
Cheers | open | 2024-08-21T17:07:11Z | 2024-08-21T17:07:11Z | https://github.com/TkTech/pysimdjson/issues/118 | [] | charlesjhill | 0 |
TkTech/pysimdjson | python-bindings | 112 | Python 3.12 Support | When trying to install pysimdjson with Python 3.12 compilation fails with a variety of different errors:
```
Backend subprocess exited when trying to invoke build_wheel
/tmp/tmp01_q5nb4/.venv/lib/python3.12/site-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg`
!!
********************************************************************************
The license_file parameter is deprecated, use license_files instead.
By 2023-Oct-30, you need to update your project and remove deprecated calls
or your builds will no longer be supported.
See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details.
********************************************************************************
!!
parsed = self.parsers.get(option_name, lambda x: x)(value)
running bdist_wheel
running build
running build_py
creating build
creating build/lib.linux-x86_64-cpython-312
creating build/lib.linux-x86_64-cpython-312/simdjson
copying simdjson/__init__.py -> build/lib.linux-x86_64-cpython-312/simdjson
copying simdjson/__init__.pyi -> build/lib.linux-x86_64-cpython-312/simdjson
copying simdjson/py.typed -> build/lib.linux-x86_64-cpython-312/simdjson
running build_ext
building 'csimdjson' extension
creating build/temp.linux-x86_64-cpython-312
creating build/temp.linux-x86_64-cpython-312/simdjson
gcc -pthread -fno-strict-overflow -DNDEBUG -g -O3 -Wall -O2 -O2 -fPIC -I/tmp/tmp01_q5nb4/.venv/include -I/usr/local/include/python3.12 -c simdjson/csimdjson.cpp -o build/temp.linux-x86_64-cpython-312/simdjson/csimdjson.o
simdjson/csimdjson.cpp:25987:19: error: macro "va_start" requires 2 arguments, but only 1 given
25987 | va_start(vargs);
| ^
In file included from /usr/local/include/python3.12/bytesobject.h:10,
from /usr/local/include/python3.12/Python.h:50,
from simdjson/csimdjson.cpp:29:
/usr/lib/gcc/x86_64-linux-gnu/9/include/stdarg.h:47: note: macro "va_start" defined here
47 | #define va_start(v,l) __builtin_va_start(v,l)
|
simdjson/csimdjson.cpp: In function ‘PyObject* __pyx_pf_9csimdjson_6Parser_6load(__pyx_obj_9csimdjson_Parser*, PyObject*, int)’:
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:934:43: note: in definition of macro ‘likely’
934 | #define likely(x) __builtin_expect(!!(x), 1)
| ^
simdjson/csimdjson.cpp:1675:43: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
1675 | (var) = (likely(__pyx_dict_version == __PYX_GET_DICT_VERSION(__pyx_d))) ?\
| ^~~~~~~~~~~~~~~~~~~~~~
simdjson/csimdjson.cpp:7705:3: note: in expansion of macro ‘__Pyx_GetModuleGlobalName’
7705 | __Pyx_GetModuleGlobalName(__pyx_t_2, __pyx_n_s_pathlib); if (unlikely(!__pyx_t_2)) __PYX_ERR(0, 515, __pyx_L1_error)
| ^~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:934:43: note: in definition of macro ‘likely’
934 | #define likely(x) __builtin_expect(!!(x), 1)
| ^
10/10/2023 13:11:09 simdjson/csimdjson.cpp:1675:43: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
1675 | (var) = (likely(__pyx_dict_version == __PYX_GET_DICT_VERSION(__pyx_d))) ?\
| ^~~~~~~~~~~~~~~~~~~~~~
simdjson/csimdjson.cpp:7705:3: note: in expansion of macro ‘__Pyx_GetModuleGlobalName’
7705 | __Pyx_GetModuleGlobalName(__pyx_t_2, __pyx_n_s_pathlib); if (unlikely(!__pyx_t_2)) __PYX_ERR(0, 515, __pyx_L1_error)
| ^~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:934:43: note: in definition of macro ‘likely’
934 | #define likely(x) __builtin_expect(!!(x), 1)
| ^
simdjson/csimdjson.cpp:1675:43: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
1675 | (var) = (likely(__pyx_dict_version == __PYX_GET_DICT_VERSION(__pyx_d))) ?\
| ^~~~~~~~~~~~~~~~~~~~~~
simdjson/csimdjson.cpp:7705:3: note: in expansion of macro ‘__Pyx_GetModuleGlobalName’
7705 | __Pyx_GetModuleGlobalName(__pyx_t_2, __pyx_n_s_pathlib); if (unlikely(!__pyx_t_2)) __PYX_ERR(0, 515, __pyx_L1_error)
| ^~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp: In function ‘PyObject* __pyx_pf___pyx_MemviewEnum___reduce_cython__(__pyx_MemviewEnum_obj*)’:
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:934:43: note: in definition of macro ‘likely’
934 | #define likely(x) __builtin_expect(!!(x), 1)
| ^
simdjson/csimdjson.cpp:1675:43: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
1675 | (var) = (likely(__pyx_dict_version == __PYX_GET_DICT_VERSION(__pyx_d))) ?\
| ^~~~~~~~~~~~~~~~~~~~~~
simdjson/csimdjson.cpp:10834:5: note: in expansion of macro ‘__Pyx_GetModuleGlobalName’
10834 | __Pyx_GetModuleGlobalName(__pyx_t_4, __pyx_n_s_pyx_unpickle_Enum); if (unlikely(!__pyx_t_4)) __PYX_ERR(1, 13, __pyx_L1_error)
| ^~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
| ^~~~~~~~~~~~~~
10/10/2023 13:11:09 simdjson/csimdjson.cpp:934:43: note: in definition of macro ‘likely’
934 | #define likely(x) __builtin_expect(!!(x), 1)
| ^
simdjson/csimdjson.cpp:1675:43: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
1675 | (var) = (likely(__pyx_dict_version == __PYX_GET_DICT_VERSION(__pyx_d))) ?\
| ^~~~~~~~~~~~~~~~~~~~~~
simdjson/csimdjson.cpp:10834:5: note: in expansion of macro ‘__Pyx_GetModuleGlobalName’
10834 | __Pyx_GetModuleGlobalName(__pyx_t_4, __pyx_n_s_pyx_unpickle_Enum); if (unlikely(!__pyx_t_4)) __PYX_ERR(1, 13, __pyx_L1_error)
| ^~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:934:43: note: in definition of macro ‘likely’
934 | #define likely(x) __builtin_expect(!!(x), 1)
| ^
simdjson/csimdjson.cpp:1675:43: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
1675 | (var) = (likely(__pyx_dict_version == __PYX_GET_DICT_VERSION(__pyx_d))) ?\
| ^~~~~~~~~~~~~~~~~~~~~~
simdjson/csimdjson.cpp:10834:5: note: in expansion of macro ‘__Pyx_GetModuleGlobalName’
10834 | __Pyx_GetModuleGlobalName(__pyx_t_4, __pyx_n_s_pyx_unpickle_Enum); if (unlikely(!__pyx_t_4)) __PYX_ERR(1, 13, __pyx_L1_error)
| ^~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:934:43: note: in definition of macro ‘likely’
934 | #define likely(x) __builtin_expect(!!(x), 1)
| ^
simdjson/csimdjson.cpp:1675:43: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
1675 | (var) = (likely(__pyx_dict_version == __PYX_GET_DICT_VERSION(__pyx_d))) ?\
| ^~~~~~~~~~~~~~~~~~~~~~
simdjson/csimdjson.cpp:10880:5: note: in expansion of macro ‘__Pyx_GetModuleGlobalName’
10880 | __Pyx_GetModuleGlobalName(__pyx_t_5, __pyx_n_s_pyx_unpickle_Enum); if (unlikely(!__pyx_t_5)) __PYX_ERR(1, 15, __pyx_L1_error)
| ^~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
10/10/2023 13:11:09 | ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:934:43: note: in definition of macro ‘likely’
934 | #define likely(x) __builtin_expect(!!(x), 1)
| ^
simdjson/csimdjson.cpp:1675:43: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
1675 | (var) = (likely(__pyx_dict_version == __PYX_GET_DICT_VERSION(__pyx_d))) ?\
| ^~~~~~~~~~~~~~~~~~~~~~
simdjson/csimdjson.cpp:10880:5: note: in expansion of macro ‘__Pyx_GetModuleGlobalName’
10880 | __Pyx_GetModuleGlobalName(__pyx_t_5, __pyx_n_s_pyx_unpickle_Enum); if (unlikely(!__pyx_t_5)) __PYX_ERR(1, 15, __pyx_L1_error)
| ^~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:934:43: note: in definition of macro ‘likely’
934 | #define likely(x) __builtin_expect(!!(x), 1)
| ^
simdjson/csimdjson.cpp:1675:43: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
1675 | (var) = (likely(__pyx_dict_version == __PYX_GET_DICT_VERSION(__pyx_d))) ?\
| ^~~~~~~~~~~~~~~~~~~~~~
simdjson/csimdjson.cpp:10880:5: note: in expansion of macro ‘__Pyx_GetModuleGlobalName’
10880 | __Pyx_GetModuleGlobalName(__pyx_t_5, __pyx_n_s_pyx_unpickle_Enum); if (unlikely(!__pyx_t_5)) __PYX_ERR(1, 15, __pyx_L1_error)
| ^~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp: In function ‘__pyx_memoryview_obj* __pyx_memview_slice(__pyx_memoryview_obj*, PyObject*)’:
simdjson/csimdjson.cpp:15998:17: warning: ‘Py_OptimizeFlag’ is deprecated [-Wdeprecated-declarations]
15998 | if (unlikely(!Py_OptimizeFlag)) {
| ^~~~~~~~~~~~~~~
simdjson/csimdjson.cpp:935:43: note: in definition of macro ‘unlikely’
935 | #define unlikely(x) __builtin_expect(!!(x), 0)
| ^
In file included from /usr/local/include/python3.12/Python.h:48,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/pydebug.h:13:37: note: declared here
13 | Py_DEPRECATED(3.12) PyAPI_DATA(int) Py_OptimizeFlag;
| ^~~~~~~~~~~~~~~
simdjson/csimdjson.cpp: In function ‘void __Pyx_Raise(PyObject*, PyObject*, PyObject*, PyObject*)’:
simdjson/csimdjson.cpp:25228:36: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_traceback’
25228 | PyObject* tmp_tb = tstate->curexc_traceback;
| ^~~~~~~~~~~~~~~~
simdjson/csimdjson.cpp:25231:21: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_traceback’
25231 | tstate->curexc_traceback = tb;
| ^~~~~~~~~~~~~~~~
simdjson/csimdjson.cpp: In function ‘int __Pyx_PyUnicode_Equals(PyObject*, PyObject*, int)’:
10/10/2023 13:11:09 simdjson/csimdjson.cpp:546:51: error: ‘_PyUnicode_Ready’ was not declared in this scope; did you mean ‘_PyUnicode_Copy’?
546 | 0 : _PyUnicode_Ready((PyObject *)(op)))
| ^~~~~~~~~~~~~~~~
simdjson/csimdjson.cpp:935:43: note: in definition of macro ‘unlikely’
935 | #define unlikely(x) __builtin_expect(!!(x), 0)
| ^
simdjson/csimdjson.cpp:25390:22: note: in expansion of macro ‘__Pyx_PyUnicode_READY’
25390 | if (unlikely(__Pyx_PyUnicode_READY(s1) < 0) || unlikely(__Pyx_PyUnicode_READY(s2) < 0))
| ^~~~~~~~~~~~~~~~~~~~~
simdjson/csimdjson.cpp: In function ‘PyObject* __Pyx_PyInt_EqObjC(PyObject*, PyObject*, long int, long int)’:
simdjson/csimdjson.cpp:25872:53: error: ‘PyLongObject’ {aka ‘struct _longobject’} has no member named ‘ob_digit’
25872 | const digit* digits = ((PyLongObject*)op1)->ob_digit;
| ^~~~~~~~
simdjson/csimdjson.cpp: In function ‘void __pyx_fatalerror(const char*, ...)’:
simdjson/csimdjson.cpp:25987:5: error: ‘va_start’ was not declared in this scope
25987 | va_start(vargs);
| ^~~~~~~~
simdjson/csimdjson.cpp: In function ‘uint64_t __Pyx_get_tp_dict_version(PyObject*)’:
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:26064:27: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
26064 | return likely(dict) ? __PYX_GET_DICT_VERSION(dict) : 0;
| ^~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:26064:27: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
26064 | return likely(dict) ? __PYX_GET_DICT_VERSION(dict) : 0;
| ^~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:26064:27: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
26064 | return likely(dict) ? __PYX_GET_DICT_VERSION(dict) : 0;
| ^~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
10/10/2023 13:11:09 22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp: In function ‘uint64_t __Pyx_get_object_dict_version(PyObject*)’:
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:26076:36: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
26076 | return (dictptr && *dictptr) ? __PYX_GET_DICT_VERSION(*dictptr) : 0;
| ^~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:26076:36: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
26076 | return (dictptr && *dictptr) ? __PYX_GET_DICT_VERSION(*dictptr) : 0;
| ^~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:26076:36: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
26076 | return (dictptr && *dictptr) ? __PYX_GET_DICT_VERSION(*dictptr) : 0;
| ^~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp: In function ‘int __Pyx_object_dict_version_matches(PyObject*, uint64_t, uint64_t)’:
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:935:43: note: in definition of macro ‘unlikely’
935 | #define unlikely(x) __builtin_expect(!!(x), 0)
| ^
simdjson/csimdjson.cpp:26080:56: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
26080 | if (unlikely(!dict) || unlikely(tp_dict_version != __PYX_GET_DICT_VERSION(dict)))
| ^~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
10/10/2023 13:11:09 22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:935:43: note: in definition of macro ‘unlikely’
935 | #define unlikely(x) __builtin_expect(!!(x), 0)
| ^
simdjson/csimdjson.cpp:26080:56: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
26080 | if (unlikely(!dict) || unlikely(tp_dict_version != __PYX_GET_DICT_VERSION(dict)))
| ^~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:935:43: note: in definition of macro ‘unlikely’
935 | #define unlikely(x) __builtin_expect(!!(x), 0)
| ^
simdjson/csimdjson.cpp:26080:56: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
26080 | if (unlikely(!dict) || unlikely(tp_dict_version != __PYX_GET_DICT_VERSION(dict)))
| ^~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp: In function ‘PyObject* __Pyx__GetModuleGlobalName(PyObject*, uint64_t*, PyObject**)’:
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:1649:21: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
1649 | (version_var) = __PYX_GET_DICT_VERSION(dict);\
| ^~~~~~~~~~~~~~~~~~~~~~
simdjson/csimdjson.cpp:26097:5: note: in expansion of macro ‘__PYX_UPDATE_DICT_CACHE’
26097 | __PYX_UPDATE_DICT_CACHE(__pyx_d, result, *dict_cached_value, *dict_version)
| ^~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:1649:21: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
10/10/2023 13:11:09 1649 | (version_var) = __PYX_GET_DICT_VERSION(dict);\
| ^~~~~~~~~~~~~~~~~~~~~~
simdjson/csimdjson.cpp:26097:5: note: in expansion of macro ‘__PYX_UPDATE_DICT_CACHE’
26097 | __PYX_UPDATE_DICT_CACHE(__pyx_d, result, *dict_cached_value, *dict_version)
| ^~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:1649:21: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
1649 | (version_var) = __PYX_GET_DICT_VERSION(dict);\
| ^~~~~~~~~~~~~~~~~~~~~~
simdjson/csimdjson.cpp:26097:5: note: in expansion of macro ‘__PYX_UPDATE_DICT_CACHE’
26097 | __PYX_UPDATE_DICT_CACHE(__pyx_d, result, *dict_cached_value, *dict_version)
| ^~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp: In function ‘PyObject* __Pyx_PyInt_AddObjC(PyObject*, PyObject*, long int, int, int)’:
simdjson/csimdjson.cpp:26697:53: error: ‘PyLongObject’ {aka ‘struct _longobject’} has no member named ‘ob_digit’
26697 | const digit* digits = ((PyLongObject*)op1)->ob_digit;
| ^~~~~~~~
simdjson/csimdjson.cpp: In function ‘PyObject* __Pyx_PyUnicode_Join(PyObject*, Py_ssize_t, Py_ssize_t, Py_UCS4)’:
simdjson/csimdjson.cpp:546:51: error: ‘_PyUnicode_Ready’ was not declared in this scope; did you mean ‘_PyUnicode_Copy’?
546 | 0 : _PyUnicode_Ready((PyObject *)(op)))
| ^~~~~~~~~~~~~~~~
simdjson/csimdjson.cpp:935:43: note: in definition of macro ‘unlikely’
935 | #define unlikely(x) __builtin_expect(!!(x), 0)
| ^
simdjson/csimdjson.cpp:27299:22: note: in expansion of macro ‘__Pyx_PyUnicode_READY’
27299 | if (unlikely(__Pyx_PyUnicode_READY(uval)))
| ^~~~~~~~~~~~~~~~~~~~~
simdjson/csimdjson.cpp: In function ‘int __Pyx_CLineForTraceback(PyThreadState*, int)’:
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:934:43: note: in definition of macro ‘likely’
934 | #define likely(x) __builtin_expect(!!(x), 1)
| ^
simdjson/csimdjson.cpp:1654:16: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
1654 | if (likely(__PYX_GET_DICT_VERSION(DICT) == __pyx_dict_version)) {\
| ^~~~~~~~~~~~~~~~~~~~~~
simdjson/csimdjson.cpp:27371:9: note: in expansion of macro ‘__PYX_PY_DICT_LOOKUP_IF_MODIFIED’
27371 | __PYX_PY_DICT_LOOKUP_IF_MODIFIED(
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
10/10/2023 13:11:09 from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:934:43: note: in definition of macro ‘likely’
934 | #define likely(x) __builtin_expect(!!(x), 1)
| ^
simdjson/csimdjson.cpp:1654:16: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
1654 | if (likely(__PYX_GET_DICT_VERSION(DICT) == __pyx_dict_version)) {\
| ^~~~~~~~~~~~~~~~~~~~~~
simdjson/csimdjson.cpp:27371:9: note: in expansion of macro ‘__PYX_PY_DICT_LOOKUP_IF_MODIFIED’
27371 | __PYX_PY_DICT_LOOKUP_IF_MODIFIED(
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:934:43: note: in definition of macro ‘likely’
934 | #define likely(x) __builtin_expect(!!(x), 1)
| ^
simdjson/csimdjson.cpp:1654:16: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
1654 | if (likely(__PYX_GET_DICT_VERSION(DICT) == __pyx_dict_version)) {\
| ^~~~~~~~~~~~~~~~~~~~~~
simdjson/csimdjson.cpp:27371:9: note: in expansion of macro ‘__PYX_PY_DICT_LOOKUP_IF_MODIFIED’
27371 | __PYX_PY_DICT_LOOKUP_IF_MODIFIED(
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:1658:30: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
1658 | __pyx_dict_version = __PYX_GET_DICT_VERSION(DICT);\
| ^~~~~~~~~~~~~~~~~~~~~~
simdjson/csimdjson.cpp:27371:9: note: in expansion of macro ‘__PYX_PY_DICT_LOOKUP_IF_MODIFIED’
27371 | __PYX_PY_DICT_LOOKUP_IF_MODIFIED(
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
10/10/2023 13:11:09 1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:1658:30: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
1658 | __pyx_dict_version = __PYX_GET_DICT_VERSION(DICT);\
| ^~~~~~~~~~~~~~~~~~~~~~
simdjson/csimdjson.cpp:27371:9: note: in expansion of macro ‘__PYX_PY_DICT_LOOKUP_IF_MODIFIED’
27371 | __PYX_PY_DICT_LOOKUP_IF_MODIFIED(
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:1647:65: warning: ‘PyDictObject::ma_version_tag’ is deprecated [-Wdeprecated-declarations]
1647 | #define __PYX_GET_DICT_VERSION(dict) (((PyDictObject*)(dict))->ma_version_tag)
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp:1658:30: note: in expansion of macro ‘__PYX_GET_DICT_VERSION’
1658 | __pyx_dict_version = __PYX_GET_DICT_VERSION(DICT);\
| ^~~~~~~~~~~~~~~~~~~~~~
simdjson/csimdjson.cpp:27371:9: note: in expansion of macro ‘__PYX_PY_DICT_LOOKUP_IF_MODIFIED’
27371 | __PYX_PY_DICT_LOOKUP_IF_MODIFIED(
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.12/dictobject.h:90,
from /usr/local/include/python3.12/Python.h:61,
from simdjson/csimdjson.cpp:29:
/usr/local/include/python3.12/cpython/dictobject.h:22:34: note: declared here
22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
| ^~~~~~~~~~~~~~
simdjson/csimdjson.cpp: In function ‘int __Pyx_PyInt_As_int(PyObject*)’:
simdjson/csimdjson.cpp:28559:55: error: ‘PyLongObject’ {aka ‘struct _longobject’} has no member named ‘ob_digit’
28559 | const digit* digits = ((PyLongObject*)x)->ob_digit;
| ^~~~~~~~
simdjson/csimdjson.cpp:28614:55: error: ‘PyLongObject’ {aka ‘struct _longobject’} has no member named ‘ob_digit’
28614 | const digit* digits = ((PyLongObject*)x)->ob_digit;
| ^~~~~~~~
simdjson/csimdjson.cpp: In function ‘size_t __Pyx_PyInt_As_size_t(PyObject*)’:
simdjson/csimdjson.cpp:28755:55: error: ‘PyLongObject’ {aka ‘struct _longobject’} has no member named ‘ob_digit’
28755 | const digit* digits = ((PyLongObject*)x)->ob_digit;
| ^~~~~~~~
simdjson/csimdjson.cpp:28810:55: error: ‘PyLongObject’ {aka ‘struct _longobject’} has no member named ‘ob_digit’
28810 | const digit* digits = ((PyLongObject*)x)->ob_digit;
| ^~~~~~~~
simdjson/csimdjson.cpp: In function ‘long int __Pyx_PyInt_As_long(PyObject*)’:
simdjson/csimdjson.cpp:29065:55: error: ‘PyLongObject’ {aka ‘struct _longobject’} has no member named ‘ob_digit’
29065 | const digit* digits = ((PyLongObject*)x)->ob_digit;
| ^~~~~~~~
simdjson/csimdjson.cpp:29120:55: error: ‘PyLongObject’ {aka ‘struct _longobject’} has no member named ‘ob_digit’
29120 | const digit* digits = ((PyLongObject*)x)->ob_digit;
| ^~~~~~~~
simdjson/csimdjson.cpp: In function ‘char __Pyx_PyInt_As_char(PyObject*)’:
10/10/2023 13:11:30 simdjson/csimdjson.cpp:29337:55: error: ‘PyLongObject’ {aka ‘struct _longobject’} has no member named ‘ob_digit’
29337 | const digit* digits = ((PyLongObject*)x)->ob_digit;
| ^~~~~~~~
simdjson/csimdjson.cpp:29392:55: error: ‘PyLongObject’ {aka ‘struct _longobject’} has no member named ‘ob_digit’
29392 | const digit* digits = ((PyLongObject*)x)->ob_digit;
| ^~~~~~~~
simdjson/csimdjson.cpp: In function ‘const char* __Pyx_PyUnicode_AsStringAndSize(PyObject*, Py_ssize_t*)’:
simdjson/csimdjson.cpp:546:51: error: ‘_PyUnicode_Ready’ was not declared in this scope; did you mean ‘_PyUnicode_Copy’?
546 | 0 : _PyUnicode_Ready((PyObject *)(op)))
| ^~~~~~~~~~~~~~~~
simdjson/csimdjson.cpp:935:43: note: in definition of macro ‘unlikely’
935 | #define unlikely(x) __builtin_expect(!!(x), 0)
| ^
simdjson/csimdjson.cpp:30755:18: note: in expansion of macro ‘__Pyx_PyUnicode_READY’
30755 | if (unlikely(__Pyx_PyUnicode_READY(o) == -1)) return NULL;
| ^~~~~~~~~~~~~~~~~~~~~
simdjson/csimdjson.cpp: In function ‘Py_ssize_t __Pyx_PyIndex_AsSsize_t(PyObject*)’:
simdjson/csimdjson.cpp:30890:47: error: ‘PyLongObject’ {aka ‘struct _longobject’} has no member named ‘ob_digit’
30890 | const digit* digits = ((PyLongObject*)b)->ob_digit;
| ^~~~~~~~
error: command '/usr/bin/gcc' failed with exit code 1
at ~/.local/pipx/venvs/pipx/lib/python3.12/site-packages/poetry/installation/chef.py:147 in _prepare
143│
144│ error = ChefBuildError("\n\n".join(message_parts))
145│
146│ if error is not None:
→ 147│ raise error from None
148│
149│ return path
150│
151│ def _prepare_sdist(self, archive: Path, destination: Path | None = None) -> Path:
Note: This error originates from the build backend, and is likely not a problem with poetry but with pysimdjson (5.0.2) not supporting PEP 517 builds. You can verify this by running 'pip wheel --use-pep517 "pysimdjson (==5.0.2)"'.
ERROR: InvocationError for command /root/.local/bin/poetry install (exited with code 1)
```
I understand it's not documented to be supported either but that's also true for 3.11 but it does work with 3.11. It would be great to have support for 3.12 as well. | closed | 2023-10-11T21:14:39Z | 2024-02-06T16:19:34Z | https://github.com/TkTech/pysimdjson/issues/112 | [] | dneuhaeuser-zalando | 1 |
TkTech/pysimdjson | python-bindings | 111 | Printing JSON structure | Hey,
I am using `pysimdjson` very often to work with JSON and I appreciate the speed and the intuitiveness of the package. Generally, I use it when I need to look directly into specific JSON for information (debug mode).
However, when I start exploring a JSON it would be useful to have a function to print the structure (or the schema of the JSON) so that we can move faster.
i will give you an example.
Suppose we have the JSON `example`:
```json
{
"owner": {
"name": "Mike",
"age": "24",
"sex": "M"
},
"dogs": [
{
"name": "Charly",
"age": 1,
"sex": "M"
},
{
"name": "Vanessa",
"age": 2,
"sex": "S"
}
]
}
```
then i can write `example.schema()` (or `example.structure()` ) and the output will be:
```bash
root
|- owner
| |- name
| |- age
| |- sex
|- dogs
| |- array type
| |- name
| |- age
| |- sex
```
Is there already something in like that in the package? | open | 2023-09-28T06:16:19Z | 2023-10-20T08:12:19Z | https://github.com/TkTech/pysimdjson/issues/111 | [] | VascoSch92 | 3 |
TkTech/pysimdjson | python-bindings | 108 | No [benchmark] extra | The documentation mentions a [benchmark] install option:
https://pysimdjson.tkte.ch/contrib/index.html#development
```
To also install 3rd party JSON libraries used for running benchmarks, use:
pip install -e ".[benchmark]"
```
The extra isn't available, as shown in the log.
```$ pip install -e ".[benchmark]"
Obtaining file:///home/roland/kiesopmaat/pyjj/pysimdjson
Preparing metadata (setup.py) ... done
WARNING: pysimdjson 5.0.2 does not provide the extra 'benchmark'
Installing collected packages: pysimdjson
Attempting uninstall: pysimdjson
Found existing installation: pysimdjson 5.0.2
Uninstalling pysimdjson-5.0.2:
Successfully uninstalled pysimdjson-5.0.2
Running setup.py develop for pysimdjson
Successfully installed pysimdjson-5.0.2
[notice] A new release of pip available: 22.3.1 -> 23.1.2
[notice] To update, run: pip install --upgrade pip
```
This is on latest master, currently: 6b3e58dca8f2c5505e4e90d5083e05c356809022 | closed | 2023-06-13T14:53:46Z | 2023-09-03T01:02:28Z | https://github.com/TkTech/pysimdjson/issues/108 | [
"needs documentation"
] | rvanlaar | 1 |
TkTech/pysimdjson | python-bindings | 106 | Tag the source | It would be very helpful if you could tag releases as well. This would enable distributions who want to run your tests to fetch the package from GitHub instead of PyPI.
Thanks | closed | 2023-03-13T10:01:10Z | 2023-03-13T22:04:38Z | https://github.com/TkTech/pysimdjson/issues/106 | [] | fabaff | 2 |
TkTech/pysimdjson | python-bindings | 105 | Return a default value from at_pointer when the key doesn't exist | I'd like to request a feature to return a default value from `at_pointer` when the path doesn't exist rather than throwing a key error. This is especially important when parsing data with a mixed schema--e.g. application log/data that have changed schema over time.
Not throwing and catching the error could save significant time as Python error handling isn't especially performant and it would give users more flexibility to decide how to handle missing keys/values. | closed | 2023-02-03T18:44:00Z | 2023-09-04T06:20:45Z | https://github.com/TkTech/pysimdjson/issues/105 | [] | ELind77 | 1 |
TkTech/pysimdjson | python-bindings | 103 | Missing `loads` and `load` definitions in `__init__.pyi` | I know it is defined in `__init__.py`, but it seems that PyCharm only analyzes `__init__.pyi`, where `loads` is not defined.
Maybe I could create a PR to fix this tiny problem if you appreciate it.
 | closed | 2023-01-07T03:23:21Z | 2023-09-04T06:28:16Z | https://github.com/TkTech/pysimdjson/issues/103 | [] | hikariyo | 8 |
TkTech/pysimdjson | python-bindings | 100 | Is the Global Interpreter Lock (GIL) held while parsing JSON? | I would like to know if JSON parsing with `pysimdjson` can be speedup by using multithreading, for that the Python GIL can't be held while parsing. | closed | 2022-10-15T21:46:50Z | 2022-11-23T08:48:44Z | https://github.com/TkTech/pysimdjson/issues/100 | [] | HMaker | 1 |
TkTech/pysimdjson | python-bindings | 99 | Unable to serialize simdjson Objects into Pickle | Hello all!
When I try to serialize `simdjson` Object into Pickle, I get the following error:
`TypeError: self.c_element,self.c_parser cannot be converted to a Python object for pickling`
Would it be possible to add support for serializing/pickling simdjson instances directly, without converting them to `dict`? If not pickling, then at least an ability to serialize into `.json` would be lovely as well. | closed | 2022-10-05T12:46:33Z | 2022-10-06T18:34:52Z | https://github.com/TkTech/pysimdjson/issues/99 | [] | vovavili | 9 |
TkTech/pysimdjson | python-bindings | 97 | simdjson 2.0.1 does not compile with GCC 8 | simdjson 2.0.1 does not compile with GCC 8. The issue was[ fixed in 2.0.3](https://github.com/simdjson/simdjson/pull/1832)and pysimdjson need to update at least to that version. | closed | 2022-09-02T03:35:50Z | 2022-09-12T19:50:10Z | https://github.com/TkTech/pysimdjson/issues/97 | [] | watersaber | 2 |
TkTech/pysimdjson | python-bindings | 96 | Performance penalty when reading items | I'm getting increased latency in my application from simdjson but I can't figure out why.
This is a snippet from profiling the function that gets items from the simdjson object. The time is in seconds.
```
Ordered by: internal time
ncalls tottime percall cumtime percall filename:lineno(function)
26 0.017 0.001 0.017 0.001 {method 'get' of 'csimdjson.Object' objects}
```
When I time getting individual items from the same object I get timings of about 15 microseconds which seems comparable with getting items from a normal python dictionary. However when I test the whole function the performance is much worse. | closed | 2022-08-14T21:06:26Z | 2023-09-03T02:48:34Z | https://github.com/TkTech/pysimdjson/issues/96 | [] | jonathan-kosgei | 2 |
TkTech/pysimdjson | python-bindings | 95 | Missing changelog for last 2 5.x releases | The last 2 releases are missing changelog entries and GitHub releases:
* 5.0.0
* 5.0.1 | closed | 2022-06-01T11:33:27Z | 2022-06-06T13:31:32Z | https://github.com/TkTech/pysimdjson/issues/95 | [] | alanhamlett | 2 |
TkTech/pysimdjson | python-bindings | 93 | Explode/Flatten to CSV example? | Do you have an example of this?
https://stackoverflow.com/questions/54210389/is-there-a-generic-way-to-read-the-multiline-json-in-spark-more-specifically-sp | closed | 2022-04-07T01:20:13Z | 2022-06-01T13:37:23Z | https://github.com/TkTech/pysimdjson/issues/93 | [] | tooptoop4 | 0 |
TkTech/pysimdjson | python-bindings | 92 | Support ndjson format | Add parse_many function to parser for newline-delimeted json logs. | closed | 2022-03-13T03:01:20Z | 2022-06-01T14:19:16Z | https://github.com/TkTech/pysimdjson/issues/92 | [] | lepipasd | 1 |
TkTech/pysimdjson | python-bindings | 91 | Thread safe Parser? | Can we assume the parser is thread safe and can be used by multiple threads concurrently for `parse`? | closed | 2022-03-03T08:44:26Z | 2023-09-04T06:20:59Z | https://github.com/TkTech/pysimdjson/issues/91 | [] | gingerwizard | 2 |
TkTech/pysimdjson | python-bindings | 90 | Example from Documentation doesn't work | When installing pysimdjson 4.0.2 and running the example from the documentation:
```python
import simdjson
parser = simdjson.Parser()
for i in range(0, 100):
doc = parser.parse(b'{"a": "b"}')
```
I get the following error:
```
RuntimeError: Tried to re-use a parser while simdjson.Object and/or simdjson.Array objects still exist referencing the old parser.
```
This seems to be related to this:
https://github.com/TkTech/pysimdjson/issues/82
Is the most performant way to solve this to `del doc` at each stage in the loop? If so I can add that to the docs. | closed | 2021-11-25T21:36:55Z | 2021-12-06T03:43:41Z | https://github.com/TkTech/pysimdjson/issues/90 | [] | Will-So | 2 |
TkTech/pysimdjson | python-bindings | 88 | Add support to release Linux aarch64 wheels | Problem
---------
On aarch64, ‘pip install pysimdjson’ builds the wheels from source code and then installs it. It requires the user to have a development environment installed on his system. Also, it takes some time to build the wheels than downloading and extracting the wheels from pypi.
Resolution
-----------
On aarch64, ‘pip install pysimdjson’ should download the wheels from pypi
@TkTech and Team Please let me know your interest in releasing aarch64 wheels. I can help in this. | closed | 2021-11-09T06:47:24Z | 2021-12-06T03:43:17Z | https://github.com/TkTech/pysimdjson/issues/88 | [] | odidev | 3 |
TkTech/pysimdjson | python-bindings | 87 | Update to upstream simdjson 1.0.0 | << Work In Progress >> | closed | 2021-09-10T17:45:55Z | 2021-12-06T03:55:43Z | https://github.com/TkTech/pysimdjson/issues/87 | [] | TkTech | 1 |
TkTech/pysimdjson | python-bindings | 86 | This parser can't support a document that big | ubuntu@ip-172-31-16-166:~$ time python convert-to-pickle.py
Traceback (most recent call last):
File "convert-to-pickle.py", line 10, in <module>
data = simdjson.loads(ch.read())
File "/usr/local/lib/python3.8/dist-packages/simdjson/__init__.py", line 52, in loads
return parser.parse(s, True)
File "simdjson/csimdjson.pyx", line 468, in csimdjson.Parser.parse
ValueError: This parser can't support a document that big | closed | 2021-08-19T03:27:57Z | 2021-08-24T17:47:16Z | https://github.com/TkTech/pysimdjson/issues/86 | [
"invalid",
"zero-effort"
] | ghost | 17 |
TkTech/pysimdjson | python-bindings | 84 | ARM build failing and ARM python 3.9 missing wheels | The ARM build is failing due to an `error.h` error. The Python 3.9 wheels for ARM/aarch64 is missing as well. | closed | 2021-06-06T03:28:59Z | 2021-06-18T20:31:09Z | https://github.com/TkTech/pysimdjson/issues/84 | [] | ExecutionSpeed | 4 |
TkTech/pysimdjson | python-bindings | 82 | Improve user experience of memory safety. | We've added a check in v4 (https://github.com/TkTech/pysimdjson/blob/master/simdjson/csimdjson.pyx#L437) that prevents parsing new documents while references continue to exist to the old one. This is *correct*, in that it ensures no errors. I wasn't terribly happy with this, but it's better then segfaulting.
It has downsides:
- It sucks as a user (https://github.com/TkTech/pysimdjson/issues/53#issuecomment-850494991), where you might have to `del` the old objects, even if you didn't intend to use them again. Very un-pythonic.
- Doesn't work on PyPy, where `del` is unreliable. The objects may not be garbage collected until much later.
Brainstorming welcome. Alternatives:
- Probably the easiest approach would be for a Parser to keep a list of Object and Array proxies that hold a reference to it, and set a dirty bit on them when `parse()` is called with a different document. The performance of this would probably be unacceptable - I might be wrong.
- Use the new `parse_into_document()` and create a new document for every parse. This is potentially both slow and very wasteful with memory, but would let us keep a document around and valid for as long as Object or Array reference it. | closed | 2021-05-28T18:21:10Z | 2023-09-04T06:21:40Z | https://github.com/TkTech/pysimdjson/issues/82 | [
"enhancement",
"help wanted"
] | TkTech | 4 |
TkTech/pysimdjson | python-bindings | 81 | Out of bounds access when using parser.parse on 0-length memory view in 4.0.0 | This code will result in an out of bounds memory access exception:
```python
import simdjson
simdjson.Parser().parse(memoryview(b""))
```
The output is
```text
Traceback (most recent call last):
File "test.py", line 3, in <module>
simdjson.Parser().parse(memoryview(b""))
File "simdjson/csimdjson.pyx", line 484, in csimdjson.Parser.parse
IndexError: Out of bounds on buffer access (axis 0)
```
It should raise a ValueError complaining that no JSON was found rather than an index error, as an empty bytes does. | closed | 2021-05-23T19:14:53Z | 2021-05-23T19:57:15Z | https://github.com/TkTech/pysimdjson/issues/81 | [] | chutz | 1 |
TkTech/pysimdjson | python-bindings | 78 | Windows 3.6 Binary? | Hi! Thanks again for this fantastic project. ^_^
I ran into some CI errors where my Windows 64-bit builds were dying due to compile errors with CPython 3.6. I noticed there's no wheel on PyPI for it.
Would it be possible to fix?
Thanks! | closed | 2021-04-23T03:32:28Z | 2021-05-23T06:50:43Z | https://github.com/TkTech/pysimdjson/issues/78 | [
"enhancement",
"packaging"
] | william-silversmith | 6 |
TkTech/pysimdjson | python-bindings | 77 | collections.abc inheritance for simdjson.Object and simdjson.Array | It would frequently be useful if these objects inherited from the standard collections abstract classes, that way generic `isinstance` tests could work as expected.
My suggestions:
- `simdjson.Object`: `collections.abc.Mapping`
- `simdjson.Array`: `collections.abc.Sequence`, `collections.abc.Iterable`
I could probably take a stab at this if it's something that would be accepted. | closed | 2021-04-16T23:44:40Z | 2021-05-08T15:30:12Z | https://github.com/TkTech/pysimdjson/issues/77 | [] | chutz | 2 |
TkTech/pysimdjson | python-bindings | 75 | Adding typing support | Hey everyone,
it is just a simple question :).
Would like to know if you are interested in either of those:
- adding `py.typed` and `simdjson.pyi` to describe API for `mypy` or similar
- accepting PR with the same
- having a PR submitted to external [typeshed[(https://github.com/python/typeshed) | closed | 2021-03-26T07:12:49Z | 2021-05-23T05:11:22Z | https://github.com/TkTech/pysimdjson/issues/75 | [] | kornicameister | 2 |
TkTech/pysimdjson | python-bindings | 73 | Fairly high overhead on the boundary Python/C++ | We are parsing a very high number of ~2KB JSON files in our Python-based application.
- The native (C++) SIMDJSON library delivers ~700k parser cycles per second.
- The pysimdjson delivers ~350k parser cycles per second.
- The Cython-based PoC implementation (in-house, so far) delivers ~700k parser cycles per second (very close to C++ implementation).
I also conducted a rather artificial test of "how many parser cycles" can I get with basically empty JSON (`{}`). The issue here is quite visible, the overhead of the Python<->pysymdjson boundary crossing is high relatively to other possible implementations.
A "parser cycle" is defined as a one call to `parser.parse(json)` on the existing parser instance.
I'm not 100% sure if this is a priority of this library, so feel free to close this one as irrelevant. | closed | 2021-03-07T13:51:36Z | 2021-07-28T15:15:12Z | https://github.com/TkTech/pysimdjson/issues/73 | [] | ateska | 9 |
TkTech/pysimdjson | python-bindings | 72 | simdjson.Parser() gets slow when iterating via json object | First of all thank you for the great module. I'm new to json and am looking into fastest api due to high sizes of data to parse. I found out that simdjson.Parser() is super fast but when iterating over object, it gets pretty slow. Here is the example of my task with results:
```
import time
import orjson
import simdjson
parser = simdjson.Parser()
m = b'[{"evl":"Quest","DAY":"Monday","classes":[1,2,6,9],"sub1":10.23,"sub2":-13.123,"sub3":2.01,"hours1":200,"hours2":4000,"date":1607614205,"signature":1},{"evl":"Quest","DAY":"Monday","classes":[1,2,6,9],"sub1":10.23,"sub2":-13.123,"sub3":2.01,"hours1":200,"hours2":4000,"date":1607614205,"signature":1},{"evl":"Quest","DAY":"Monday","classes":[1,2,6,9],"sub1":10.23,"sub2":-13.123,"sub3":2.01,"hours1":200,"hours2":4000,"date":1607614205,"signature":1},{"evl":"Quest","DAY":"Monday","classes":[1,2,6,9],"sub1":10.23,"sub2":-13.123,"sub3":2.01,"hours1":200,"hours2":4000,"date":1607614205,"signature":1},{"evl":"Quest","DAY":"Monday","classes":[1,2,6,9],"sub1":10.23,"sub2":-13.123,"sub3":2.01,"hours1":200,"hours2":4000,"date":1607614205,"signature":1},{"evl":"Quest","DAY":"Monday","classes":[1,2,6,9],"sub1":10.23,"sub2":-13.123,"sub3":2.01,"hours1":200,"hours2":4000,"date":1607614205,"signature":1},{"evl":"Quest","DAY":"Monday","classes":[1,2,6,9],"sub1":10.23,"sub2":-13.123,"sub3":2.01,"hours1":200,"hours2":4000,"date":1607614205,"signature":1},{"evl":"Quest","DAY":"Monday","classes":[1,2,6,9],"sub1":10.23,"sub2":-13.123,"sub3":2.01,"hours1":200,"hours2":4000,"date":1607614205,"signature":1}]'
def benchmark0(name, loads):
start = time.time()
for _ in range(100_000):
jsn = loads(m)
print(name, F"{time.time() - start:2.3f}")
def benchmark1(name, loads):
start = time.time()
for _ in range(100_000):
jsn = loads(m)
for js in jsn:
a = js['evl']
# print(a)# do sth
print(name, F"{time.time() - start:2.3f}")
print('\n======== deserialization only ==================')
benchmark0(F"{'orjson':>15}", orjson.loads)
benchmark0(F"{'simdjson_loads':>15}", simdjson.loads)
benchmark0(F"{'simdjson_parser':>15}", parser.parse) # NOTE: I tested it also in trading: on_message() but simdjson is slower than orjson; especially at for js in jsn, where jsn is simdjson obj which is read super slowly
print('\n======== deserialization + iteration over json obj (my type of task) ==============')
benchmark1(F"{'orjson':>15}", orjson.loads)
benchmark1(F"{'simdjson_loads':>15}", simdjson.loads)
benchmark1(F"{'simdjson_parser':>15}", parser.parse) # NOTE: I tested it also in trading: on_message() but simdjson is slower than orjson; especially at for js in jsn, where jsn is simdjson obj which is read super slowly
```
and results:
```
======== deserialization only ==================
orjson 0.577
simdjson_loads 0.713
simdjson_parser 0.172
======== deserialization + iteration over json obj (my type of task) ==============
orjson 0.597
simdjson_loads 0.741
simdjson_parser 1.364
```
What we see is that in the first case the parser is super fast (0.172 vs 0.577), but when we need to iterate via json object, it gets very slow (1.364 vs 0.597). Is there any workaround to preserve the speed of the simdjson.Parser()? Thank you | closed | 2020-12-24T06:02:58Z | 2020-12-30T12:01:20Z | https://github.com/TkTech/pysimdjson/issues/72 | [] | smjure | 1 |
TkTech/pysimdjson | python-bindings | 71 | Expose document_stream interface |
The `pysimdjson` library could support our document_stream interface (`parse_many` function). It is well tested as of release 0.7 (with fuzz testing) and works well today. It supports streams of indefinite size.
See https://github.com/simdjson/simdjson/blob/master/doc/parse_many.md
Related to https://github.com/TkTech/pysimdjson/issues/70 | open | 2020-12-07T15:43:17Z | 2023-09-04T06:36:47Z | https://github.com/TkTech/pysimdjson/issues/71 | [
"enhancement"
] | lemire | 5 |
TkTech/pysimdjson | python-bindings | 70 | This parser can't support a document that big | I encounter the following issue when parsing a huge (>10G) JSON file.
| closed | 2020-12-04T19:45:27Z | 2020-12-07T15:23:59Z | https://github.com/TkTech/pysimdjson/issues/70 | [
"wontfix",
"upstream change required"
] | dclong | 4 |
TkTech/pysimdjson | python-bindings | 68 | Instead of returning a KeyError at_pointer returns the value of the valid root | Hello,
Step to reproduce:
```
>>> import simdjson
>>> parser = simdjson.Parser()
>>> t = '{"foo": "bar"}'
>>> d = parser.parse(t)
>>> d.at_pointer("/foo")
'bar'
>>> d.at_pointer("/bar")
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
KeyError: 'No such key'
>>> d.at_pointer("/foo/foo")
'bar'
```
I expect that `d.at_pointer("/foo/foo")` returns a `KeyError` to be consistent with `d.at_pointer("/bar")`.
This bug comes from simdjson version 5.0. On version 6.0, this bug has been fixed.
Best,
Hadrien | closed | 2020-12-03T15:42:26Z | 2020-12-03T15:47:48Z | https://github.com/TkTech/pysimdjson/issues/68 | [] | hglaude | 1 |
TkTech/pysimdjson | python-bindings | 66 | .at() in documentation should be .at_pointer() | `assert doc.at('res/1/name') == 'second'` from README gives error
`at_pointer` works as intended, it should be:
`assert doc.at_pointer('res/1/name') == 'second'`
Python 3.8.2
pysimdjson 3.1.1 | closed | 2020-11-30T17:58:51Z | 2020-12-01T10:23:54Z | https://github.com/TkTech/pysimdjson/issues/66 | [] | SergeyDidenko | 0 |
TkTech/pysimdjson | python-bindings | 65 | as_buffer() support for Object values. | We now support `as_buffer()` #59 which drastically improves performance when loading arrays from JSON into numpy.
We should also support `as_buffer()` for Objects, which would retrieve the values as an array. This is to support calling it like this:
https://github.com/riddell-stan/pystan-next/blob/1e027a8bded88d51c6b957a841b859938c0ac86d/stan/fit.py#L93
For @riddell-stan's use case, this should use less memory and be roughly 4x faster (since we also void the iterator creation for `values()`) | open | 2020-11-22T14:59:15Z | 2024-06-21T17:45:44Z | https://github.com/TkTech/pysimdjson/issues/65 | [
"enhancement"
] | TkTech | 3 |
TkTech/pysimdjson | python-bindings | 64 | Abandon Travis for ARM & PPC builds | Travis.ci (predictably, once they were bought by a fund) is starting to go down and is no longer a viable option for OSS that doesn't want the headache of constantly re-applying for minutes.
We have couple options:
1. We cross-compile on a native host with a pre-built docker image, then transfer as an artifact to run in Qemu for tests.
2. Find an alternative Ci with native platform support (Drone for ARM? I think @ddevault was working on ARM and PPC support for sh? Preferably, we find a one-shop-does-it-all)
3. We could host github runners ourselves (and we did for a short few minutes), except it turns out these are incredibly exploitable on public repos. No one wants to deal with a PR turning our box into a bitcoin miner.
@lemire | closed | 2020-11-13T03:01:43Z | 2021-12-06T03:56:03Z | https://github.com/TkTech/pysimdjson/issues/64 | [
"packaging"
] | TkTech | 3 |
TkTech/pysimdjson | python-bindings | 63 | Python 3.9 Binaries | Hi all,
I just wanted to check in to see when py39 binaries might be available. No rush, I'm just trying to make sure my libraries are ready for when usage picks up and pysimdjson is a dependency.
Thanks for all the help and a great library!
Thanks!
Will | closed | 2020-11-12T22:56:50Z | 2020-11-13T02:53:09Z | https://github.com/TkTech/pysimdjson/issues/63 | [
"packaging"
] | william-silversmith | 2 |
TkTech/pysimdjson | python-bindings | 62 | Bundle pybind11 | Even though pip's logs show that it is downloading the binary wheel, it's still occasionally requiring pybind11. Since this has happened a few times (for example most recently with https://github.com/alex/nyt-2020-election-scraper/issues/177#issuecomment-723253931), we either need to:
- figure out why this is happening
- bundle the pybind11 headers always, which are a couple of kb. | closed | 2020-11-06T22:41:20Z | 2021-02-03T19:42:32Z | https://github.com/TkTech/pysimdjson/issues/62 | [
"bug",
"packaging"
] | TkTech | 1 |
TkTech/pysimdjson | python-bindings | 61 | Access Dictionary Keys Fast | Hi! I have a JSON parsing problem where I am downloading 100k+ files and JSON parsing is taking about 74% of the time (in one sample) to process them excluding download time. I was looking at alternative SIMD JSON parsers to help reduce the burden of parsing as processing is taking somewhere between hours to tens of hours. The files look like:
```
{
'12291084214': [ 6x int ],
'19204192141': [ 6x int ],
...
}
```
The left hand side represents labels I need to accumulate and the right hand size represents a 3D bounding box. The right hand value side is not useful in the case where I consider the whole dataset and so can be ignored when working on the worst case of the problem. The left hand key side must be decoded and extracted in all cases. Is there a way to use something similar to the `at` method to rapidly extract only the keys?
As an alternative approach, I tried parsing all the files at once which reduces parsing time by about 30%, but results in huge memory usage. I figured there must be a useful middle ground where we can reduce the cost but retain online-processing. ^_^
This process is run infrequently and so it's not the end of the world if such a thing isn't possible, but jeez would it help:
<img width="895" alt="image" src="https://user-images.githubusercontent.com/2517065/97403730-55180f80-18cb-11eb-875a-a39428acecb7.png">
| closed | 2020-10-28T07:07:38Z | 2020-11-04T01:10:19Z | https://github.com/TkTech/pysimdjson/issues/61 | [
"needs documentation"
] | william-silversmith | 4 |
TkTech/pysimdjson | python-bindings | 60 | Support On-Demand API | Introduced in upstream version 0.6.0, improving performance for known structures. | closed | 2020-10-25T06:02:46Z | 2023-09-04T06:22:09Z | https://github.com/TkTech/pysimdjson/issues/60 | [
"enhancement"
] | TkTech | 1 |
TkTech/pysimdjson | python-bindings | 56 | Pysimdjson fails to install on python 3.6 | ```Collecting pysimdjson==2.5.0
Using cached https://files.pythonhosted.org/packages/9b/f6/c63260f8788574de8fdd0bbe70f803328cb058141c0903ba29637d89f863/pysimdjson-2.5.0.tar.gz
Installing collected packages: pysimdjson
Running setup.py install for pysimdjson ... error
Complete output from command /home/ubuntu/ctix-2/venv/bin/python3.6 -u -c "import setuptools, tokenize;__file__='/tmp/pip-install-wzmco2i3/pysimdjson/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-record-jelehspx/install-record.txt --single-version-externally-managed --compile --install-headers /home/ubuntu/ctix-2/venv/include/site/python3.6/pysimdjson:
running install
running build
running build_py
creating build
creating build/lib.linux-x86_64-3.6
creating build/lib.linux-x86_64-3.6/simdjson
copying simdjson/__init__.py -> build/lib.linux-x86_64-3.6/simdjson
running build_ext
building 'csimdjson' extension
creating build/temp.linux-x86_64-3.6
creating build/temp.linux-x86_64-3.6/simdjson
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/home/ubuntu/ctix-2/venv/lib/python3.6/site-packages/pybind11/include -I/home/ubuntu/ctix-2/venv/include -I/usr/include/python3.6m -c simdjson/binding.cpp -o build/temp.linux-x86_64-3.6/simdjson/binding.o -std=c++11
In file included from /home/ubuntu/ctix-2/venv/lib/python3.6/site-packages/pybind11/include/pybind11/pytypes.h:12:0,
from /home/ubuntu/ctix-2/venv/lib/python3.6/site-packages/pybind11/include/pybind11/cast.h:13,
from /home/ubuntu/ctix-2/venv/lib/python3.6/site-packages/pybind11/include/pybind11/attr.h:13,
from /home/ubuntu/ctix-2/venv/lib/python3.6/site-packages/pybind11/include/pybind11/pybind11.h:44,
from simdjson/binding.cpp:5:
/home/ubuntu/ctix-2/venv/lib/python3.6/site-packages/pybind11/include/pybind11/detail/common.h:112:20: fatal error: Python.h: No such file or directory
compilation terminated.
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
----------------------------------------
Command "/home/ubuntu/ctix-2/venv/bin/python3.6 -u -c "import setuptools, tokenize;__file__='/tmp/pip-install-wzmco2i3/pysimdjson/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-record-jelehspx/install-record.txt --single-version-externally-managed --compile --install-headers /home/ubuntu/ctix-2/venv/include/site/python3.6/pysimdjson" failed with error code 1 in /tmp/pip-install-wzmco2i3/pysimdjson/
You are using pip version 19.0, however version 20.2.4 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.``` | closed | 2020-10-20T11:47:48Z | 2020-10-20T19:07:43Z | https://github.com/TkTech/pysimdjson/issues/56 | [] | anudeepsamaiya | 6 |
TkTech/pysimdjson | python-bindings | 55 | Include License in release | Would it be possible to include the code's license in the pypi releases? That would help downstream packagers, like conda-forge. | closed | 2020-10-09T01:36:09Z | 2023-09-04T06:22:09Z | https://github.com/TkTech/pysimdjson/issues/55 | [
"enhancement",
"packaging"
] | CJ-Wright | 2 |
TkTech/pysimdjson | python-bindings | 54 | Question: Comparison with other Python-JSON packages | I'm currently comparing various Python packages for handling JSON ([link](https://github.com/MartinThoma/algorithms/tree/master/Python/json-benchmark): cpython 3.8.6 json, simplejson, ujson, simdjson, orjson, rapidjson). I'm trying to understand their differences. I would be super happy if you could help me with that by answering some questions:
1. Is there any difference in features between the JSON packages?
2. I compared reading/dumping a 2.3MB GeoJSON, a 631KB Twitter JSON, and a 2MB JSON full of floats. Is there any other thing you think I should compare for benchmarking? Do you have internal benchmarks?
3. Are you in contact with the other Python JSON package developers? Do you maybe share the way you benchmark or test cases?
4. Are you in contact with JSON package developers from other languages?
5. Are there other packages / articles for comparison I should have a look at?
6. My benchmarks show that pysimdjson is pretty fast for reading, but rather slow for writhing. Where does that come from?
7. What is the relationship to [libpy-simdjson](https://pypi.org/project/libpy-simdjson/)
8. Have you considered adding another maintainer or moving the git repository to an organization? This could build trust that the fate of the project does not stay/fall with a single developer.
9. According to the Trove-Classifiers, you consider this package to be in "alpha" state. Considering the fact that it is in version 3.x, over a year old, has multiple contributors and is used by other people... is that still current?
| closed | 2020-09-26T09:11:12Z | 2020-10-28T17:56:11Z | https://github.com/TkTech/pysimdjson/issues/54 | [] | MartinThoma | 1 |
TkTech/pysimdjson | python-bindings | 53 | Segfault when not assigning the parser to a variable | Here is a Python session that segfaults:
```
>>> import simdjson
>>> pa=simdjson.Parser().parse('{"a": 9999}')
>>> pa["a"]
zsh: segmentation fault (core dumped) python
```
And here is one that works:
```
>>> import simdjson
>>> p = simdjson.Parser()
>>> pa = p.parse('{"a": 9999}')
>>> pa["a"]
9999
```
It's unclear to me why the first one segfaults, and it looks like a bug?
I imagine the parser is garbage collected by Python in the first example, but it's still clearly in use by the "pa" variable? | closed | 2020-09-06T20:40:12Z | 2023-09-04T06:22:09Z | https://github.com/TkTech/pysimdjson/issues/53 | [
"bug"
] | palkeo | 9 |
TkTech/pysimdjson | python-bindings | 52 | Update to upstream 0.5.0. | closed | 2020-08-20T03:58:50Z | 2020-08-21T05:49:36Z | https://github.com/TkTech/pysimdjson/issues/52 | [] | TkTech | 1 |
|
TkTech/pysimdjson | python-bindings | 51 | Support for Decimal | I've read in the documentation there's plan to support this. What status are these plans in? Thanks. | open | 2020-08-19T13:16:57Z | 2020-10-28T17:48:40Z | https://github.com/TkTech/pysimdjson/issues/51 | [
"enhancement",
"upstream change required",
"blocked"
] | gaborbernat | 3 |
TkTech/pysimdjson | python-bindings | 50 | Transition to SAX-style interface in upstream simdjson | A SAX-style interface is coming in the upstream PR https://github.com/simdjson/simdjson/pull/1104. Once this is available in a release, it will be worth switching to just for reliable memory control on extremely large documents, let alone an apparent speed increase. | closed | 2020-08-10T18:01:23Z | 2020-10-28T17:45:32Z | https://github.com/TkTech/pysimdjson/issues/50 | [
"enhancement",
"upstream change required",
"blocked"
] | TkTech | 1 |
TkTech/pysimdjson | python-bindings | 47 | Prove we're worth using in real-world cases | We should experiment adding simdjson to some real-world projects where performance matters. This is both to prove we're worth using, and it ensure our API is extensive enough for real-world problems, extending it where needed. Basically "success stories". If you've used pysimdjson successfully, please feel free to contribute.
- @ericls's https://github.com/fellowinsights/prosemirror-py
- An ~8% gain on tiny documents (the document found in the project's example.py) from just switching `import json` to `import simdjson`.
before:
```
------------------------------------------------- benchmark: 1 tests -------------------------------------------------
Name (time in us) Min Max Mean StdDev Median IQR Outliers OPS (Kops/s) Rounds Iterations
----------------------------------------------------------------------------------------------------------------------
test_decoding_steps 26.0000 78.1000 28.3224 4.1256 27.3000 0.7000 559;930 35.3077 7571 1
----------------------------------------------------------------------------------------------------------------------
```
after:
```
------------------------------------------------- benchmark: 1 tests -------------------------------------------------
Name (time in us) Min Max Mean StdDev Median IQR Outliers OPS (Kops/s) Rounds Iterations
----------------------------------------------------------------------------------------------------------------------
test_decoding_steps 24.2000 74.5000 25.6597 2.8573 25.0000 0.5000 365;674 38.9716 5702 1
----------------------------------------------------------------------------------------------------------------------
```
Our high max time is the one-time overhead from selecting algorithm implementation, which can be avoided.
- On more realistic documents with many attributes that the server doesn't care about, and using the simdjson-specific API for lazy dicts, the speed gain was drastic, seeing a 4-8x increase on a synthetic test documents. However, minimal documents performed much worse, as every key was accessed anyways. Both are things that could be improved by rewriting parts of prosemirror-py to be simdjson-aware rather than patching it in. Additionally, there are a few checks for `isinstance(x, list)` that needed to be updated, as our Array type isn't a true list.
- [Kinto ](https://github.com/Kinto/kinto) is Mozilla's simple key-value database used for some production services like bookmark syncing. It's JSON performance is abysmal, and although it (sometime) uses ujson it does some odd bug workarounds. As an example using the memory backend will cause a `JSON decode (built-in) -> encode (built-in) -> decode (ujson) -> encode (built-in)` when creating (https://github.com/Kinto/kinto/blob/5f8ba312d0af8cac8d6f2ee5371bd26d5501be7e/kinto/core/storage/memory.py#L205) in an attempt to fix an issue where keys might be byte strings. Sure kinto isn't trying to be speedy, but this is silly and we can improve it. WIP. | closed | 2020-08-06T01:18:33Z | 2023-06-25T20:14:13Z | https://github.com/TkTech/pysimdjson/issues/47 | [
"enhancement",
"help wanted"
] | TkTech | 3 |
TkTech/pysimdjson | python-bindings | 46 | Properly populate JSONDecodeError & UnicodeDecodeError | We currently raise a ValueError instead of JSONDecodeError (which is a ValueError subclass) in some cases where JSONDecodeError would be more appropriate. This is because upstream simdjson does not report errors with enough granularity to populate `lineno` and `colno` (https://docs.python.org/3/library/json.html#json.JSONDecodeError)
Might be viable to return 0 and 0 for now? | open | 2020-07-20T16:54:37Z | 2020-08-10T18:05:50Z | https://github.com/TkTech/pysimdjson/issues/46 | [
"bug",
"upstream change required",
"blocked"
] | TkTech | 2 |
TkTech/pysimdjson | python-bindings | 45 | Filtering outside CPython | We used to have a little toy state machine that would let us do basic queries against documents before simdjson got JSONPointer support in 0.3.0. Anything we can do to reduce the number of objects crossing the C++ -> CPython barrier will greatly improve real-world performance, so it's time to bring this back.
This is a draft for experimentation and planning on syntax.
Selection:
- `.` -> Current element.
- `.[]` -> "For each item in an array". (returns array)
- `.[1]` -> For single item in array (returns scalar)
- `.[1:2]` -> For slice of array (returns array)
- `.<prop>` -> Property of current object. (returns scalar)
- `<string>` -> String literal, escapable with quotes and backslash.
Construction:
- `{name: .name, description: .description}` -> Construct an object from current object, ignoring unspecified fields.
- `[.name]` -> Construct an array from current object, ignoring unspecified fields.
- When an object key is not specified, the field it accesses is used. `{.price < 2}` is the same as `{price: .price < 2}`
Filtering:
- Given document `[0, 1, 2, 3, 4]`, query `.[] <= 2` returns `[0, 1, 2]`
- Given document `[{"price": 1.00}, {"price": 2.00}, {"price": 3.00}]`, query `.[].price < 2` returns `[{"price": 1.00}]`
- Given document `{"price": 1.00}`, query `.price` returns `1.00`
- When given multiple key filters, they're implicitly AND. Given document `[{"price": 1.00, "available": true, "unwantedfield": false}, {"price": 2.00, "available": false}, {"price": 3.00}]`, query `.[] | {.price < 2, .available == true}` returns `[{"price": 1.00, "available": true}]` | open | 2020-07-20T15:57:12Z | 2023-09-04T06:22:09Z | https://github.com/TkTech/pysimdjson/issues/45 | [
"enhancement"
] | TkTech | 0 |
TkTech/pysimdjson | python-bindings | 44 | FreeBSD & Windows ARM Binary Packages Tracking Issue | Time to start supporting ARM. Unfortunately we can't use self-hosted runners for ARM because we accept public PRs and I don't feel like having my AWS runner hijacked! We'll be using something other than GitHub actions for Ci on ARM platforms.
- [x] Linux
- [x] CPython
- [x] PyPy3 (currently not available on travis.ci for ARM)
- [ ] FreeBSD (no manylinux equivalent, can we even do this? #40)
- [ ] CPython
- [ ] Windows ARM
- [ ] CPython
- [x] OS X
- [x] CPython
Windows ARM support is a bit of an exotic stretch goal. The development ecosystem for Windows ARM is very, very new.
Likewise, OS X ARM support is likely to appear sometime late this year. It's likely Apple will release a new toolchain long before they start shipping hardware. | closed | 2020-07-20T13:58:00Z | 2023-06-25T20:17:02Z | https://github.com/TkTech/pysimdjson/issues/44 | [
"packaging"
] | TkTech | 6 |
TkTech/pysimdjson | python-bindings | 43 | manylinux2010 release silently failing to build Py3.8 wheels. | Build fails auditwheel, but does not fail the github action. | closed | 2020-07-18T18:05:36Z | 2020-07-19T13:51:12Z | https://github.com/TkTech/pysimdjson/issues/43 | [
"packaging"
] | TkTech | 2 |
TkTech/pysimdjson | python-bindings | 42 | Consider benchmarking against libpy_simdjson | It looks like libpy_simdjson does much better on some benchmarks...
```
-------------------------------------------------------- benchmark 'Load /home/runner/work/libpy_simdjson/libpy_simdjson/libpy_simdjson/tests/jsonexamples/twitter.json': 6 tests -------------------------------------------------------
Name (time in us) Min Max Mean StdDev Median IQR Outliers OPS Rounds Iterations
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
test_benchmark_load[path1-libpy_simdjson-loads] 374.2130 (1.0) 10,169.1400 (1.0) 445.6502 (1.0) 237.7491 (1.0) 443.3150 (1.0) 66.3020 (1.0) 19;29 2,243.9125 (1.0) 1790 1
test_benchmark_load[path1-orjson-loads] 2,788.1970 (7.45) 11,687.4110 (1.15) 3,351.3276 (7.52) 1,117.1151 (4.70) 3,198.9625 (7.22) 351.0120 (5.29) 10;12 298.3892 (0.13) 294 1
test_benchmark_load[path1-ujson-loads] 3,312.1150 (8.85) 12,571.4370 (1.24) 3,973.3347 (8.92) 1,221.4127 (5.14) 3,805.8815 (8.59) 447.3170 (6.75) 7;9 251.6778 (0.11) 258 1
test_benchmark_load[path1-pysimdjson-loads] 3,586.0280 (9.58) 18,704.8590 (1.84) 4,553.9661 (10.22) 1,772.5065 (7.46) 4,182.3480 (9.43) 331.1612 (4.99) 7;17 219.5888 (0.10) 169 1
test_benchmark_load[path1-python_json-loads] 4,573.6530 (12.22) 13,900.1650 (1.37) 5,396.5765 (12.11) 1,236.4753 (5.20) 5,222.7750 (11.78) 554.0430 (8.36) 6;7 185.3027 (0.08) 189 1
test_benchmark_load[path1-rapidjson-loads] 5,447.2870 (14.56) 16,226.5570 (1.60) 6,506.3766 (14.60) 1,495.7694 (6.29) 6,322.1140 (14.26) 544.9407 (8.22) 6;7 153.6954 (0.07) 165 1
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
``` | closed | 2020-07-16T16:42:26Z | 2020-10-28T17:48:03Z | https://github.com/TkTech/pysimdjson/issues/42 | [] | lemire | 5 |
TkTech/pysimdjson | python-bindings | 41 | Build binary packages using clang-cl on Windows | Support for clang-cl is coming. As part of the PR that allows CPython to build against clang-cl, distutils is updated to build *with* clang-cl (https://github.com/python/cpython/pull/18371). Once this PR is merged and a new CPython release includes it we can start using it for our binary releases.
Clang has reached a point where it's safe enough for us to use with CPython's built with MSVC2015 or newer. https://clang.llvm.org/docs/MSVCCompatibility.html
This would alleviate poor windows performance caused by MSVC issues (https://github.com/simdjson/simdjson/issues/847, but not entirely, https://github.com/simdjson/simdjson/issues/848).
We only need to do this if upstream simdjson doesn't figure out what's up with MSVC. @lemire | closed | 2020-07-08T02:51:07Z | 2020-08-10T18:03:13Z | https://github.com/TkTech/pysimdjson/issues/41 | [
"enhancement",
"packaging",
"blocked"
] | TkTech | 6 |
TkTech/pysimdjson | python-bindings | 40 | FreeBSD Packaging | Upstream simdjson has official FreeBSD support as of 0.4. There are some complications for our binary releases however.
- [ ] Our Ci, Github Actions, does not yet support FreeBSD as a hosted or self-hosted host. See https://github.com/actions/runner/issues/385. We'll need to run the builds elsewhere or cross-compile without running tests.
- [ ] There seems to be no equivalent to manylinux for FreeBSD. Hopefully I'm wrong. We'll need to distribute our binary packages through the native FreeBSD package manager. | closed | 2020-06-24T23:51:45Z | 2020-08-06T19:12:36Z | https://github.com/TkTech/pysimdjson/issues/40 | [
"enhancement",
"good first issue",
"packaging"
] | TkTech | 2 |
TkTech/pysimdjson | python-bindings | 39 | simdjson.h:129:23: error: ‘__m256i _mm256_loadu2_m128i(const __m128i*, const __m128i*)’ redeclared inline without ‘gnu_inline’ attribute | Self explanatory. The source seems to be defining some intrinsics which already exist in `/usr/lib/gcc/x86_64-redhat-linux/10/include/avxintrin.h`
```diff
diff --git a/simdjson/src/simdjson.h b/simdjson/src/simdjson.h
index 80c6b6d..3d6aea3 100644
--- a/simdjson/src/simdjson.h
+++ b/simdjson/src/simdjson.h
@@ -124,6 +124,7 @@ static inline void *aligned_malloc(size_t alignment, size_t size) {
}
+#if 0
#ifndef __clang__
#ifndef _MSC_VER
static __m256i inline _mm256_loadu2_m128i(__m128i const *__addr_hi,
@@ -143,6 +144,7 @@ static inline void _mm256_storeu2_m128i(__m128i *__addr_hi, __m128i *__addr_lo,
}
#endif
#endif
+#endif
static inline void aligned_free(void *memblock) {
``` | closed | 2020-06-10T07:03:51Z | 2020-07-17T18:38:06Z | https://github.com/TkTech/pysimdjson/issues/39 | [] | giannitedesco | 1 |
TkTech/pysimdjson | python-bindings | 38 | File causes a crash in pysimdjson (reliably) | I am copying over issue https://github.com/simdjson/simdjson/issues/921 from simdjson. We do not see a crash in simdjson itself, but there is a crash in pysimdjson:
```Python
import simdjson
a = open("test.txt").read()
b = simdjson.loads(a.encode())
```
Using the file https://github.com/simdjson/simdjson/files/4749603/test.txt
| closed | 2020-06-09T13:29:27Z | 2020-06-18T20:08:34Z | https://github.com/TkTech/pysimdjson/issues/38 | [] | lemire | 17 |
TkTech/pysimdjson | python-bindings | 37 | Warning! diff in json and simdjson with big number | First: sorry for my poor English, hope you can understand my code.
pysimdjson is an awesome project, but when I handle my dataset,I found it‘s different from python json.
```
import json
import simdjson
a = b'{"acase":10699247336865531002}\n'
print(a)
b = json.loads(a)
print(b)
c= simdjson.ParsedJson(a)
print(c)
```
```
---------------------------------------------------------------------------
JSONDecodeError Traceback (most recent call last)
<ipython-input-4-6ab3abe7b6ca> in <module>
5 b = json.loads(a)
6 print(b)
----> 7 c= simdjson.ParsedJson(a)
8 print(c)
simdjson/csimdjson.pyx in simdjson.csimdjson.ParsedJson.__init__()
JSONDecodeError: Error parsing document: line 1 column 1 (char 0)
``` | closed | 2020-05-19T06:57:51Z | 2020-05-22T06:41:19Z | https://github.com/TkTech/pysimdjson/issues/37 | [] | lishoujun | 5 |
TkTech/pysimdjson | python-bindings | 36 | my local compile was different from repo,could anyone help me,thanks! | my cmd:
`python3 setup.py clean && rm build -rf && python3 setup.py build_ext --inplace && python3 setup.py install`
then
`git diff
`
> -/* Generated by Cython 0.29.6 */
> +/* Generated by Cython 0.29.17 */
>some other diff
>
> @@ -824,7 +853,7 @@ static const char *__pyx_filename;
>
> static const char *__pyx_f[] = {
> "stringsource",
> - "csimdjson.pyx",
> + "simdjson/csimdjson.pyx",
> };
why the path is different, how can I compile the pyx to cpp just as code in repo.
> - "csimdjson.pyx",
> + "simdjson/csimdjson.pyx", | closed | 2020-05-19T03:50:03Z | 2020-07-17T18:38:17Z | https://github.com/TkTech/pysimdjson/issues/36 | [] | lishoujun | 0 |
TkTech/pysimdjson | python-bindings | 34 | Python 3.8 support | Hi,
First of all, thank you for the bindings!
Would it be feasible to add support for Python 3.8?
Thanks,
Eli | closed | 2020-04-20T07:00:16Z | 2020-07-17T20:42:27Z | https://github.com/TkTech/pysimdjson/issues/34 | [
"packaging"
] | h5rdly | 1 |
TkTech/pysimdjson | python-bindings | 32 | Add orjson comparison | https://pypi.org/project/orjson/ | closed | 2020-03-31T23:01:23Z | 2020-07-17T18:39:23Z | https://github.com/TkTech/pysimdjson/issues/32 | [
"good first issue"
] | mathbunnyru | 1 |
TkTech/pysimdjson | python-bindings | 31 | Consider upgrading to simdjson 0.4 | # Version 0.4 of simdjson is now available
Highlights
- Test coverage has been greatly improved and we have resolved many static-analysis warnings on different systems.
New features:
- We added a fast (8GB/s) minifier that works directly on JSON strings.
- We added fast (10GB/s) UTF-8 validator that works directly on strings (any strings, including non-JSON).
- The array and object elements have a constant-time size() method.
Performance:
- Performance improvements to the API (type(), get<>()).
- The parse_many function (ndjson) has been entirely reworked. It now uses a single secondary thread instead of several new threads.
- We have introduced a faster UTF-8 validation algorithm (lookup3) for all kernels (ARM, x64 SSE, x64 AVX).
System support:
- C++11 support for older compilers and systems.
- FreeBSD support (and tests).
- We support the clang front-end compiler (clangcl) under Visual Studio.
- It is now possible to target ARM platforms under Visual Studio.
- The simdjson library will never abort or print to standard output/error.
# Version 0.3 of simdjson is now available
## Highlights
- **Multi-Document Parsing:** Read a bundle of JSON documents (ndjson) 2-4x faster than doing it individually. [API docs](https://github.com/simdjson/simdjson/blob/master/doc/basics.md#newline-delimited-json-ndjson-and-json-lines) / [Design Details](https://github.com/simdjson/simdjson/blob/master/doc/parse_many.md)
- **Simplified API:** The API has been completely revamped for ease of use, including a new JSON navigation API and fluent support for error code *and* exception styles of error handling with a single API. [Docs](https://github.com/simdjson/simdjson/blob/master/doc/basics.md#the-basics-loading-and-parsing-json-documents)
- **Exact Float Parsing:** Now simdjson parses floats flawlessly *without* any performance loss (https://github.com/simdjson/simdjson/pull/558).
[Blog Post](https://lemire.me/blog/2020/03/10/fast-float-parsing-in-practice/)
- **Even Faster:** The fastest parser got faster! With a [shiny new UTF-8 validator](https://github.com/simdjson/simdjson/pull/387)
and meticulously refactored SIMD core, simdjson 0.3 is 15% faster than before, running at 2.5 GB/s (where 0.2 ran at 2.2 GB/s).
## Minor Highlights
- Fallback implementation: simdjson now has a non-SIMD fallback implementation, and can run even on very old 64-bit machines.
- Automatic allocation: as part of API simplification, the parser no longer has to be preallocated-it will adjust automatically when it encounters larger files.
- Runtime selection API: We've exposed simdjson's runtime CPU detection and implementation selection as an API, so you can tell what implementation we detected and test with other implementations.
- Error handling your way: Whether you use exceptions or check error codes, simdjson lets you handle errors in your style. APIs that can fail return simdjson_result<T>, letting you check the error code before using the result. But if you are more comfortable with exceptions, skip the error code and cast straight to T, and exceptions will be thrown automatically if an error happens. Use the same API either way!
- Error chaining: We also worked to keep non-exception error-handling short and sweet. Instead of having to check the error code after every single operation, now you can *chain* JSON navigation calls like looking up an object field or array element, or casting to a string, so that you only have to check the error code once at the very end. | closed | 2020-03-31T22:49:38Z | 2020-09-10T13:03:28Z | https://github.com/TkTech/pysimdjson/issues/31 | [] | lemire | 8 |
TkTech/pysimdjson | python-bindings | 29 | Fix simple typo: signficantly -> significantly | There is a small typo in tests/test_speed.py.
Should read `significantly` rather than `signficantly`.
| closed | 2020-02-18T10:30:45Z | 2020-04-02T00:50:55Z | https://github.com/TkTech/pysimdjson/issues/29 | [] | timgates42 | 0 |
TkTech/pysimdjson | python-bindings | 27 | Consider a similar function to ParsedJson.items which uses an already parsed query | I think, a good addition to the ParsedJson.items function would be either a new function which directly uses a already parsed query, or to extend the ParsedJson.items function to accept already parsed queries. In cases where you need to extract data from a lot of jsons with the same queries you might save a bit time. | closed | 2019-12-22T17:53:54Z | 2020-07-17T18:38:53Z | https://github.com/TkTech/pysimdjson/issues/27 | [] | tkilias | 0 |
TkTech/pysimdjson | python-bindings | 26 | Consider updating to simdjson 0.2.1 | The library simdjson has a new major release (0.2.0). Major changes:
* Support for 64-bit ARM processors, can run under iOS (iPhone).
* Runtime dispatching on x64 processors (switches to SSE on older x64 processors, uses AVX2 when available). Supports processors as far back as the Intel Westmere.
* More accurate number parsing.
* Fixes most warnings under Visual Studio.
* Several small bugs have been fixed.
* Better performance in some cases.
* Introduces a JSON Pointer interface https://tools.ietf.org/html/rfc6901
* Better and more specific error messages (with optional textual descriptions).
* valgrind clean.
* Unified code style (LLVM).
| closed | 2019-08-01T20:37:02Z | 2020-03-31T22:50:16Z | https://github.com/TkTech/pysimdjson/issues/26 | [] | lemire | 6 |
TkTech/pysimdjson | python-bindings | 25 | Consider updating to latest release (0.1.2) | It fixes a few potential buffer overruns for adversarial inputs. It should be safer. | closed | 2019-05-10T13:49:16Z | 2019-08-01T20:25:47Z | https://github.com/TkTech/pysimdjson/issues/25 | [] | lemire | 3 |
TkTech/pysimdjson | python-bindings | 24 | Consider updating to simdjson 0.1.1 | We have a new version which has precomputed string lengths, and supporting strings with null characters in them. | closed | 2019-03-14T00:12:12Z | 2019-03-14T16:47:26Z | https://github.com/TkTech/pysimdjson/issues/24 | [] | lemire | 0 |
TkTech/pysimdjson | python-bindings | 22 | The Python overhead is about 95% of the processing time | From `simdjson/scripts/javascript`, I generated a file called `large.json`. In C++, parsing this file takes about 0.25 s.
```
$parse large.json
Min: 0.252188 bytes read: 203130424 Gigabytes/second: 0.805471
```
I wrote the following Python script...
```
from timeit import default_timer as timer
with open('large.json', 'rb') as fin:
x = fin.read()
for i in range(10):
start = timer()
doc = simdjson.loads(x)
end = timer()
print(end - start)
```
I get...
```
$ time python3 test.py
3.471898762974888
3.9210079659242183
3.3614078611135483
3.72252986789681
3.7506914171390235
3.756883286871016
3.752689895918593
3.751842977013439
3.7484844669234008
(...)
```
If my analysis is correct (and it could be wrong), pysimdjson takes 3.7 s to parse the file, and of that, 0.25 s are due to simdjson, leaving about 95% of the processing time to overhead.
I know that this is known, but I wanted to provide a data point.
| closed | 2019-03-03T22:14:57Z | 2020-07-17T21:13:18Z | https://github.com/TkTech/pysimdjson/issues/22 | [] | lemire | 24 |
TkTech/pysimdjson | python-bindings | 20 | API compatibility with python's json module | Hi, I just tested this library and I was very impressed with the way it quickly loaded my JSON lines into dicts. however, I found some incompatibilities with the default `json` module and `pysimdjson`. For example, `json` module accepts strings to load as opposed to `pysimdjson` which only accepts `bytes`. Also, there's no dumps function.
Is it advisable to make a fully compatible library as a drop-in replacement for `json`? for example, writing a module so adding this at the top of the script would work:
```
try:
import pysimdjson as json
except:
import json
```
We can also fall back to the built-in json module to handle unimplemented sections for the time being.
Thanks for the good project :+1: | closed | 2019-03-01T08:31:09Z | 2019-03-06T23:15:48Z | https://github.com/TkTech/pysimdjson/issues/20 | [] | mosajjal | 1 |
TkTech/pysimdjson | python-bindings | 19 | OSX Failure with gcc-8 | ```
Running setup.py install for pysimdjson ... error
Complete output from command /Users/dnb/miniconda3/bin/python -u -c "import setuptools, tokenize;__file__='/private/var/folders/2j/_qcjjf4d24n5fswlhqk5zq6c0000gn/T/pip-install-fysr9lw_/pysimdjson/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /private/var/folders/2j/_qcjjf4d24n5fswlhqk5zq6c0000gn/T/pip-record-rpb664eh/install-record.txt --single-version-externally-managed --compile:
running install
running build
running build_py
creating build
creating build/lib.macosx-10.7-x86_64-3.6
creating build/lib.macosx-10.7-x86_64-3.6/simdjson
copying simdjson/__init__.py -> build/lib.macosx-10.7-x86_64-3.6/simdjson
running build_ext
[build_assist] LDFLAGS/LINK is set in environment, so default linker arguments of ['-lc++', '-nodefaultlibs'] will not be used.
building 'simdjson.csimdjson' extension
creating build/temp.macosx-10.7-x86_64-3.6
creating build/temp.macosx-10.7-x86_64-3.6/simdjson
gcc-8 -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/Users/dnb/miniconda3/include -arch x86_64 -I/Users/dnb/miniconda3/include -arch x86_64 -I/usr/local/opt/llvm/include -I/usr/local/opt/readline/include -I/usr/local/opt/openssl/include -Isimdjson -I./simdjson -I/Users/dnb/miniconda3/include/python3.6m -c simdjson/csimdjson.cpp -o build/temp.macosx-10.7-x86_64-3.6/simdjson/csimdjson.o -march=native -stdlib=libc++
gcc-8: error: unrecognized command line option '-stdlib=libc++'
error: command 'gcc-8' failed with exit status 1
----------------------------------------
Command "/Users/dnb/miniconda3/bin/python -u -c "import setuptools, tokenize;__file__='/private/var/folders/2j/_qcjjf4d24n5fswlhqk5zq6c0000gn/T/pip-install-fysr9lw_/pysimdjson/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /private/var/folders/2j/_qcjjf4d24n5fswlhqk5zq6c0000gn/T/pip-record-rpb664eh/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /private/var/folders/2j/_qcjjf4d24n5fswlhqk5zq6c0000gn/T/pip-install-fysr9lw_/pysimdjson/
```
setup.py should check whether clang or gcc is being used. | closed | 2019-02-28T12:37:30Z | 2020-06-25T04:43:30Z | https://github.com/TkTech/pysimdjson/issues/19 | [
"enhancement",
"packaging"
] | dnbaker | 6 |
TkTech/pysimdjson | python-bindings | 18 | ImportError: No module named csimdjson | I use command `sudo CFLAGS="-march=native -std=c++17" python setup.py install` to install。After it success, I use `import simdjson` in my python2.7 interpreter, then I got this error:
```
Python 2.7.12 (default, Nov 12 2018, 14:36:49)
[GCC 5.4.0 20160609] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import simdjson
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "simdjson/__init__.py", line 1, in <module>
from simdjson.csimdjson import (
ImportError: No module named csimdjson
``` | closed | 2019-02-28T02:55:54Z | 2019-02-28T10:09:51Z | https://github.com/TkTech/pysimdjson/issues/18 | [] | VoidBird | 1 |
TkTech/pysimdjson | python-bindings | 17 | pip install fails on macOS Mohave with fatal error: 'ios' file not found | The problem is as follows... (using Python 3.7)
```
$ pip install pysimdjson
Collecting pysimdjson
Using cached https://files.pythonhosted.org/packages/89/f2/dc4dd7687b4d3a3f5bdfd2839c3789a5eefdb20b7ed9da0bf5c294988dfd/pysimdjson-1.3.0.tar.gz
Building wheels for collected packages: pysimdjson
Building wheel for pysimdjson (setup.py) ... error
Complete output from command /anaconda3/bin/python -u -c "import setuptools, tokenize;__file__='/private/var/folders/y8/nl_pprtd12x78vqkv3px0bp40000gn/T/pip-install-6oo7crzn/pysimdjson/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" bdist_wheel -d /private/var/folders/y8/nl_pprtd12x78vqkv3px0bp40000gn/T/pip-wheel-8d_dfkkx --python-tag cp36:
running bdist_wheel
running build
running build_ext
building 'simdjson' extension
creating build
creating build/temp.macosx-10.7-x86_64-3.6
gcc -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/anaconda3/include -arch x86_64 -I/anaconda3/include -arch x86_64 -I. -I/anaconda3/include/python3.6m -c simdjson.cpp -o build/temp.macosx-10.7-x86_64-3.6/simdjson.o
warning: include path for stdlibc++ headers not found; pass '-std=libc++' on the command line to use the libc++ standard library instead [-Wstdlibcxx-not-found]
simdjson.cpp:626:10: fatal error: 'ios' file not found
#include "ios"
^~~~~
1 warning and 1 error generated.
error: command 'gcc' failed with exit status 1
----------------------------------------
Failed building wheel for pysimdjson
Running setup.py clean for pysimdjson
Failed to build pysimdjson
Installing collected packages: pysimdjson
Running setup.py install for pysimdjson ... error
Complete output from command /anaconda3/bin/python -u -c "import setuptools, tokenize;__file__='/private/var/folders/y8/nl_pprtd12x78vqkv3px0bp40000gn/T/pip-install-6oo7crzn/pysimdjson/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /private/var/folders/y8/nl_pprtd12x78vqkv3px0bp40000gn/T/pip-record-pk52ri4p/install-record.txt --single-version-externally-managed --compile:
running install
running build
running build_ext
building 'simdjson' extension
creating build
creating build/temp.macosx-10.7-x86_64-3.6
gcc -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/anaconda3/include -arch x86_64 -I/anaconda3/include -arch x86_64 -I. -I/anaconda3/include/python3.6m -c simdjson.cpp -o build/temp.macosx-10.7-x86_64-3.6/simdjson.o
warning: include path for stdlibc++ headers not found; pass '-std=libc++' on the command line to use the libc++ standard library instead [-Wstdlibcxx-not-found]
simdjson.cpp:626:10: fatal error: 'ios' file not found
#include "ios"
^~~~~
1 warning and 1 error generated.
error: command 'gcc' failed with exit status 1
----------------------------------------
Command "/anaconda3/bin/python -u -c "import setuptools, tokenize;__file__='/private/var/folders/y8/nl_pprtd12x78vqkv3px0bp40000gn/T/pip-install-6oo7crzn/pysimdjson/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /private/var/folders/y8/nl_pprtd12x78vqkv3px0bp40000gn/T/pip-record-pk52ri4p/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /private/var/folders/y8/nl_pprtd12x78vqkv3px0bp40000gn/T/pip-install-6oo7crzn/pysimdjson/
```
The trouble remains even if we use the recommended flags...
```
$ CFLAGS="-march=native -std=c++17" pip install pysimdjson
Collecting pysimdjson
Using cached https://files.pythonhosted.org/packages/89/f2/dc4dd7687b4d3a3f5bdfd2839c3789a5eefdb20b7ed9da0bf5c294988dfd/pysimdjson-1.3.0.tar.gz
Building wheels for collected packages: pysimdjson
Building wheel for pysimdjson (setup.py) ... error
Complete output from command /anaconda3/bin/python -u -c "import setuptools, tokenize;__file__='/private/var/folders/y8/nl_pprtd12x78vqkv3px0bp40000gn/T/pip-install-c47y1lww/pysimdjson/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" bdist_wheel -d /private/var/folders/y8/nl_pprtd12x78vqkv3px0bp40000gn/T/pip-wheel-y35qun9z --python-tag cp36:
running bdist_wheel
running build
running build_ext
building 'simdjson' extension
creating build
creating build/temp.macosx-10.7-x86_64-3.6
gcc -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -march=native -std=c++17 -I. -I/anaconda3/include/python3.6m -c simdjson.cpp -o build/temp.macosx-10.7-x86_64-3.6/simdjson.o
warning: include path for stdlibc++ headers not found; pass '-std=libc++' on the command line to use the libc++ standard library instead [-Wstdlibcxx-not-found]
simdjson.cpp:626:10: fatal error: 'ios' file not found
#include "ios"
^~~~~
1 warning and 1 error generated.
error: command 'gcc' failed with exit status 1
----------------------------------------
Failed building wheel for pysimdjson
Running setup.py clean for pysimdjson
Failed to build pysimdjson
Installing collected packages: pysimdjson
Running setup.py install for pysimdjson ... error
Complete output from command /anaconda3/bin/python -u -c "import setuptools, tokenize;__file__='/private/var/folders/y8/nl_pprtd12x78vqkv3px0bp40000gn/T/pip-install-c47y1lww/pysimdjson/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /private/var/folders/y8/nl_pprtd12x78vqkv3px0bp40000gn/T/pip-record-8bjwe4j2/install-record.txt --single-version-externally-managed --compile:
running install
running build
running build_ext
building 'simdjson' extension
creating build
creating build/temp.macosx-10.7-x86_64-3.6
gcc -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -march=native -std=c++17 -I. -I/anaconda3/include/python3.6m -c simdjson.cpp -o build/temp.macosx-10.7-x86_64-3.6/simdjson.o
warning: include path for stdlibc++ headers not found; pass '-std=libc++' on the command line to use the libc++ standard library instead [-Wstdlibcxx-not-found]
simdjson.cpp:626:10: fatal error: 'ios' file not found
#include "ios"
^~~~~
1 warning and 1 error generated.
error: command 'gcc' failed with exit status 1
----------------------------------------
Command "/anaconda3/bin/python -u -c "import setuptools, tokenize;__file__='/private/var/folders/y8/nl_pprtd12x78vqkv3px0bp40000gn/T/pip-install-c47y1lww/pysimdjson/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /private/var/folders/y8/nl_pprtd12x78vqkv3px0bp40000gn/T/pip-record-8bjwe4j2/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /private/var/folders/y8/nl_pprtd12x78vqkv3px0bp40000gn/T/pip-install-c47y1lww/pysimdjson/
```
The fix is to set `MACOSX_DEPLOYMENT_TARGET` like so:
```
$ MACOSX_DEPLOYMENT_TARGET=10.14 CFLAGS="-march=native -std=c++17" pip install pysimdjson
Collecting pysimdjson
Using cached https://files.pythonhosted.org/packages/89/f2/dc4dd7687b4d3a3f5bdfd2839c3789a5eefdb20b7ed9da0bf5c294988dfd/pysimdjson-1.3.0.tar.gz
Building wheels for collected packages: pysimdjson
Building wheel for pysimdjson (setup.py) ... done
Stored in directory: /Users/lemire/Library/Caches/pip/wheels/64/52/4b/4c2feec7ea7e50f875ee0c2ad68290b5015fb93a60c16db5b4
Successfully built pysimdjson
Installing collected packages: pysimdjson
Successfully installed pysimdjson-1.3.0
```
Maybe this ought to appear in the README? Instructions for macOS Mohave? | closed | 2019-02-27T14:49:03Z | 2019-03-02T20:36:37Z | https://github.com/TkTech/pysimdjson/issues/17 | [
"enhancement",
"packaging"
] | lemire | 4 |
TkTech/pysimdjson | python-bindings | 16 | default on the right flags by including the logic in setup.py | It seems that it should not be necessary for the user to provide the flags in this manner:
```
CFLAGS="-march=native -std=c++17" pip install pysimdjson
```
Violating the standard (which is just pip install pysimdjson) is not great from a usability point of view (for obvious reasons).
One can detect the platform with `platform.system()` (Windows, Darwin, and so forth), and then do compile_args.append('-std=c++17') or the like.
| closed | 2019-02-27T13:10:15Z | 2019-03-02T19:53:35Z | https://github.com/TkTech/pysimdjson/issues/16 | [
"enhancement",
"packaging"
] | lemire | 6 |
TkTech/pysimdjson | python-bindings | 15 | Installation report exception | My local environment：
python3.6
macos mojave 10.14.3
When I use this installation method `pip install pysimdjson`
Error exception：
When I use this installation method
`git clone https://github.com/TkTech/pysimdjson.git
cd pysimdjson
python setup.py install`
Error exception：
Please help me to see this installation problem, thank you | closed | 2019-02-27T09:39:18Z | 2019-02-27T22:54:16Z | https://github.com/TkTech/pysimdjson/issues/15 | [] | lvorcool | 2 |
TkTech/pysimdjson | python-bindings | 14 | Provide a simple cli | With the merging of `restructured` in 53ca4a60 the project is now structured as a proper python module, making it cleaner to add pure-python additions to the package. We should include a cli as part of the package, based on click.
- [ ] `simdjson <source> <query>` should filter `source` by `query` and return the results as JSON with no further output. (the poor-man's jq)
- [ ] `simdjson shell [source]` should load a Python shell with `ParsedJson`, `Iterator`, `pj` (`= ParsedJson(source)`), and `iterator` (`= Iterator(pj)`) already imported.
- [ ] `simdjson debug [source] tape` should provide a syntax-highlighted debugging view of the state of the tape for `source`. | closed | 2019-02-27T06:20:06Z | 2020-06-24T23:37:21Z | https://github.com/TkTech/pysimdjson/issues/14 | [
"enhancement"
] | TkTech | 0 |
TkTech/pysimdjson | python-bindings | 13 | Expand simdjson.pxd to have 1:1 coverage of simdjson's API | Currently we only expose the minimum of simdjson's API to support `loads()` and `items()`' query "language". We should aim for 1:1 so that this library can be used to:
- explore simdjson features outside of our limited functionality
- quickly expand the test coverage of simdjson itself by writing high-level tests in Python
- 3rd party projects that want to use simdjson and not pysimdjson should be able to just import our .pxd to get "free" bindings
- ideally @lemire and @geofflangdale themselves should find it more enjoyable and efficient to test new features and changes for simdjson using pysimdjson. `pysimdjson shell canada.json` should give you a Python shell with the `ParsedJson` and a `Iterator` object already setup. | closed | 2019-02-27T04:21:14Z | 2019-03-02T19:54:07Z | https://github.com/TkTech/pysimdjson/issues/13 | [
"enhancement"
] | TkTech | 4 |
TkTech/pysimdjson | python-bindings | 12 | Provide manylinux binary wheels for linux | Trivial, but time consuming. simdjson uses c++17 features in a few places that make it depend on recent versions of gcc and libstdc++. Normally for 99% of C/C++ bindings we can get away with just using the manylinux docker images, but only when we can use gcc5. We need to build gcc7 on centos5 and static link libstc++ (which will add a couple MB to the binary 😢).
Building gcc is not what I'd call "fast", so we definitely need to create our own docker image with it ready to go. I imagine this would definitely be useful to other projects, so worth the effort.
@lemire tweet in https://twitter.com/lemire/status/1100566630994792448 makes it pretty clear interested parties aren't always going to know how to deal with a C compiler. Actually pretty happy about that, since it means Linux is becoming more accessible. Tilts the scale from "eh, linux users know the routine" to "we should probably do this."
Refs:
- https://github.com/pypa/manylinux/issues/118
- https://www.python.org/dev/peps/pep-0571/
- https://github.com/pypa/manylinux/issues/179
- https://www.python.org/dev/peps/pep-0491/ | closed | 2019-02-27T04:02:51Z | 2019-03-01T18:35:06Z | https://github.com/TkTech/pysimdjson/issues/12 | [
"enhancement",
"packaging"
] | TkTech | 2 |
TkTech/pysimdjson | python-bindings | 11 | Support for Python 2? | For Python 2, it might be useful to ignore the register keyword:
```
CFLAGS="-march=native -std=gnu++17 -Wno-register" pip install pysimdjson
```
Notice the `-Wno-register` part, it seems important.
Otherwise you may get this...
```
$ CFLAGS="-march=native -std=gnu++17" pip install pysimdjson
Collecting pysimdjson
Using cached https://files.pythonhosted.org/packages/89/f2/dc4dd7687b4d3a3f5bdfd2839c3789a5eefdb20b7ed9da0bf5c294988dfd/pysimdjson-1.3.0.tar.gz
Building wheels for collected packages: pysimdjson
Running setup.py bdist_wheel for pysimdjson ... error
Complete output from command /usr/bin/python -u -c "import setuptools, tokenize;__file__='/tmp/pip-install-py_i2_/pysimdjson/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" bdist_wheel -d /tmp/pip-wheel-NuS0q1 --python-tag cp27:
/usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution option: 'long_description_content_type'
warnings.warn(msg)
running bdist_wheel
running build
running build_ext
building 'simdjson' extension
creating build
creating build/temp.linux-x86_64-2.7
clang-6.0 -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -march=native -std=gnu++17 -fPIC -I. -I/usr/include/python2.7 -c simdjson.cpp -o build/temp.linux-x86_64-2.7/simdjson.o
In file included from simdjson.cpp:24:
In file included from /usr/include/python2.7/Python.h:85:
/usr/include/python2.7/unicodeobject.h:534:5: error: ISO C++17 does not allow 'register' storage class specifier [-Wregister]
register PyObject *obj, /* Object */
^~~~~~~~~
/usr/include/python2.7/unicodeobject.h:553:5: error: ISO C++17 does not allow 'register' storage class specifier [-Wregister]
register PyObject *obj /* Object */
^~~~~~~~~
/usr/include/python2.7/unicodeobject.h:575:5: error: ISO C++17 does not allow 'register' storage class specifier [-Wregister]
register const wchar_t *w, /* wchar_t buffer */
^~~~~~~~~
/usr/include/python2.7/unicodeobject.h:593:5: error: ISO C++17 does not allow 'register' storage class specifier [-Wregister]
register wchar_t *w, /* wchar_t buffer */
^~~~~~~~~
In file included from simdjson.cpp:24:
In file included from /usr/include/python2.7/Python.h:94:
/usr/include/python2.7/stringobject.h:173:5: error: ISO C++17 does not allow 'register' storage class specifier [-Wregister]
register PyObject *obj, /* string or Unicode object */
^~~~~~~~~
/usr/include/python2.7/stringobject.h:174:5: error: ISO C++17 does not allow 'register' storage class specifier [-Wregister]
register char **s, /* pointer to buffer variable */
^~~~~~~~~
/usr/include/python2.7/stringobject.h:175:5: error: ISO C++17 does not allow 'register' storage class specifier [-Wregister]
register Py_ssize_t *len /* pointer to length variable or NULL
^~~~~~~~~
7 errors generated.
error: command 'clang-6.0' failed with exit status 1
``` | closed | 2019-02-26T21:08:00Z | 2019-02-28T08:48:15Z | https://github.com/TkTech/pysimdjson/issues/11 | [
"enhancement",
"needs documentation"
] | lemire | 5 |
TkTech/pysimdjson | python-bindings | 10 | Ambiguous License | @TkTech What license is this project under?
The badge shows `mit license` but the license file is the Apache License.
Also would be great if you can link the badge to the license file. :) | closed | 2019-02-26T16:31:04Z | 2019-02-26T16:39:30Z | https://github.com/TkTech/pysimdjson/issues/10 | [] | feluelle | 1 |
TkTech/pysimdjson | python-bindings | 9 | Installation failed on ppc64le architecture | Hello!
I'm trying to install the package on a Power PC 9 machine architecture and am having trouble specifying the correct C flags. Here is the machine information:
```
(kmer-hashing)
✘ Mon 25 Feb - 07:17 ~/code/pysimdjson origin ☊ master ✔ ☗v1.3.0 1☀
uname -a
Linux euler.czbiohub.org 4.14.0-49.13.1.el7a.ppc64le #1 SMP Mon Aug 27 07:37:11 EDT 2018 ppc64le ppc64le ppc64le GNU/Linux
(kmer-hashing)
✘ Mon 25 Feb - 07:23 ~/code/pysimdjson origin ☊ master ✔ ☗v1.3.0 1☀
lscpu
Architecture: ppc64le
Byte Order: Little Endian
CPU(s): 128
On-line CPU(s) list: 0-127
Thread(s) per core: 4
Core(s) per socket: 16
Socket(s): 2
NUMA node(s): 6
Model: 2.2 (pvr 004e 1202)
Model name: POWER9, altivec supported
CPU max MHz: 3800.0000
CPU min MHz: 2300.0000
L1d cache: 32K
L1i cache: 32K
L2 cache: 512K
L3 cache: 10240K
NUMA node0 CPU(s): 0-63
NUMA node8 CPU(s): 64-127
NUMA node252 CPU(s):
NUMA node253 CPU(s):
NUMA node254 CPU(s):
NUMA node255 CPU(s):
```
And here is the installation commands
### With `pysimdjson`-recommended flags
```
((kmer-hashing)
Mon 25 Feb - 07:22 ~/code/pysimdjson origin ☊ master ✔ ☗v1.3.0 1☀
CFLAGS="-march=native -std=c++17" python setup.py install
running install
running bdist_egg
running egg_info
writing pysimdjson.egg-info/PKG-INFO
writing dependency_links to pysimdjson.egg-info/dependency_links.txt
writing top-level names to pysimdjson.egg-info/top_level.txt
reading manifest file 'pysimdjson.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'pysimdjson.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-ppc64le/egg
running install_lib
running build_ext
building 'simdjson' extension
gcc -pthread -B /home/olga/.conda/envs/kmer-hashing/compiler_compat -Wl,--sysroot=/ -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -march=native -std=c++17 -fPIC -I. -I/home/olga/.conda/envs/kmer-hashing/include/python3.6m -c simdjson.cpp -o build/temp.linux-ppc64le-3.6/simdjson.o
gcc: error: unrecognized command line option ‘-march=native’
gcc: error: unrecognized command line option ‘-std=c++17’
error: command 'gcc' failed with exit status 1
(kmer-hashing)
```
### With `CFLAGS` from [gentoo](https://wiki.gentoo.org/wiki/Safe_CFLAGS#POWER8)
Cannot import `x86intrin.h`
```
(kmer-hashing)
Mon 25 Feb - 07:25 ~/code/pysimdjson origin ☊ master ✔ ☗v1.3.0 1☀
env|grep -E '^C.*FLAGS'
CXXFLAGS=-mcpu=power8 -O2 -pipe -mabi=altivec -maltivec
CFLAGS=-mcpu=power8 -O2 -pipe -mabi=altivec -maltivec
Mon 25 Feb - 07:23 ~/code/pysimdjson origin ☊ master ✔ ☗v1.3.0 1☀
python setup.py install
running install
running bdist_egg
running egg_info
writing pysimdjson.egg-info/PKG-INFO
writing dependency_links to pysimdjson.egg-info/dependency_links.txt
writing top-level names to pysimdjson.egg-info/top_level.txt
reading manifest file 'pysimdjson.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'pysimdjson.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-ppc64le/egg
running install_lib
running build_ext
building 'simdjson' extension
gcc -pthread -B /home/olga/.conda/envs/kmer-hashing/compiler_compat -Wl,--sysroot=/ -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -mcpu=power8 -O2 -pipe -mabi=altivec -maltivec -fPIC -I. -I/home/olga/.conda/envs/kmer-hashing/include/python3.6m -c simdjson.cpp -o build/temp.linux-ppc64le-3.6/simdjson.o
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++ [enabled by default]
In file included from simdjson.cpp:630:0:
src/simdjson.h:9:23: fatal error: x86intrin.h: No such file or directory
#include <x86intrin.h>
^
compilation terminated.
error: command 'gcc' failed with exit status 1
```
Suggestions welcome! Thank you.
Warmest,
Olga | closed | 2019-02-25T15:27:53Z | 2021-02-04T13:07:48Z | https://github.com/TkTech/pysimdjson/issues/9 | [
"enhancement",
"packaging"
] | olgabot | 4 |
TkTech/pysimdjson | python-bindings | 8 | Cannot build from source on linux | ```
(feb2018) pascal@archbook:/home/.../gits/pysimdjson$ python setup.py install
running install
running bdist_egg
running egg_info
creating pysimdjson.egg-info
writing pysimdjson.egg-info/PKG-INFO
writing dependency_links to pysimdjson.egg-info/dependency_links.txt
writing top-level names to pysimdjson.egg-info/top_level.txt
writing manifest file 'pysimdjson.egg-info/SOURCES.txt'
reading manifest file 'pysimdjson.egg-info/SOURCES.txt'
writing manifest file 'pysimdjson.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_ext
building 'simdjson' extension
creating build
creating build/temp.linux-x86_64-3.7
gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -I/home/pascal/.pyenv/versions/3.7.2/envs/feb2018/include -I/home/pascal/.pyenv/versions/3.7.2/include/python3.7m -c simdjson.cpp -o build/temp.linux-x86_64-3.7/simdjson.o
In file included from simdjson.cpp:634:
src/simdjson.h:35727:2: warning: #warning "We require AVX2 support!" [-Wcpp]
#warning "We require AVX2 support!"
^~~~~~~
In file included from simdjson.cpp:634:
src/simdjson.h: In function ‘__m256i _mm256_loadu2_m128i(const __m128i*, const __m128i*)’:
src/simdjson.h:95:67: warning: AVX vector return without AVX enabled changes the ABI [-Wpsabi]
__m128i const *__addr_lo) {
^
In file included from simdjson.cpp:634:
src/simdjson.h: At global scope:
src/simdjson.h:450:6: error: ‘string_view’ in namespace ‘std’ does not name a type
std::string_view get_corpus(std::string filename);
^~~~~~~~~~~
src/simdjson.h:450:1: note: ‘std::string_view’ is only available from C++17 onwards
std::string_view get_corpus(std::string filename);
^~~
In file included from simdjson.cpp:634:
src/simdjson.h:35749:44: error: ‘string_view’ in namespace ‘std’ does not name a type
static inline size_t jsonminify(const std::string_view & p, char *out) {
^~~~~~~~~~~
src/simdjson.h:35749:39: note: ‘std::string_view’ is only available from C++17 onwards
static inline size_t jsonminify(const std::string_view & p, char *out) {
^~~
src/simdjson.h: In function ‘size_t jsonminify(const int&, char*)’:
src/simdjson.h:35750:25: error: request for member ‘data’ in ‘p’, which is of non-class type ‘const int’
return jsonminify(p.data(), p.size(), out);
^~~~
src/simdjson.h:35750:35: error: request for member ‘size’ in ‘p’, which is of non-class type ‘const int’
return jsonminify(p.data(), p.size(), out);
^~~~
In file included from simdjson.cpp:634:
src/simdjson.h: At global scope:
src/simdjson.h:37274:35: error: ‘string_view’ in namespace ‘std’ does not name a type
inline bool json_parse(const std::string_view &s, ParsedJson &pj, bool reallocifneeded = true) {
^~~~~~~~~~~
src/simdjson.h:37274:30: note: ‘std::string_view’ is only available from C++17 onwards
inline bool json_parse(const std::string_view &s, ParsedJson &pj, bool reallocifneeded = true) {
^~~
src/simdjson.h: In function ‘bool json_parse(const int&, ParsedJson&, bool)’:
src/simdjson.h:37275:23: error: request for member ‘data’ in ‘s’, which is of non-class type ‘const int’
return json_parse(s.data(), s.size(), pj, reallocifneeded);
^~~~
src/simdjson.h:37275:33: error: request for member ‘size’ in ‘s’, which is of non-class type ‘const int’
return json_parse(s.data(), s.size(), pj, reallocifneeded);
^~~~
src/simdjson.h: At global scope:
src/simdjson.h:37308:48: error: ‘string_view’ in namespace ‘std’ does not name a type
inline ParsedJson build_parsed_json(const std::string_view &s, bool reallocifneeded = true) {
^~~~~~~~~~~
src/simdjson.h:37308:43: note: ‘std::string_view’ is only available from C++17 onwards
inline ParsedJson build_parsed_json(const std::string_view &s, bool reallocifneeded = true) {
^~~
src/simdjson.h: In function ‘ParsedJson build_parsed_json(const int&, bool)’:
src/simdjson.h:37309:30: error: request for member ‘data’ in ‘s’, which is of non-class type ‘const int’
return build_parsed_json(s.data(), s.size(), reallocifneeded);
^~~~
src/simdjson.h:37309:40: error: request for member ‘size’ in ‘s’, which is of non-class type ‘const int’
return build_parsed_json(s.data(), s.size(), reallocifneeded);
^~~~
In file included from simdjson.cpp:635:
src/simdjson.cpp: At global scope:
src/simdjson.cpp:29:6: error: ‘string_view’ in namespace ‘std’ does not name a type
std::string_view get_corpus(std::string filename) {
^~~~~~~~~~~
src/simdjson.cpp:29:1: note: ‘std::string_view’ is only available from C++17 onwards
std::string_view get_corpus(std::string filename) {
^~~
In file included from simdjson.cpp:635:
src/simdjson.cpp:312:35: error: ‘string_view’ in namespace ‘std’ does not name a type
extern bool json_parse(const std::string_view &s, ParsedJson &pj, bool reallocifneeded);
^~~~~~~~~~~
src/simdjson.cpp:312:30: note: ‘std::string_view’ is only available from C++17 onwards
extern bool json_parse(const std::string_view &s, ParsedJson &pj, bool reallocifneeded);
^~~
src/simdjson.cpp:314:48: error: ‘string_view’ in namespace ‘std’ does not name a type
extern ParsedJson build_parsed_json(const std::string_view &s, bool reallocifneeded);
^~~~~~~~~~~
src/simdjson.cpp:314:43: note: ‘std::string_view’ is only available from C++17 onwards
extern ParsedJson build_parsed_json(const std::string_view &s, bool reallocifneeded);
^~~
In file included from simdjson.cpp:635:
src/simdjson.cpp: In function ‘bool find_structural_bits(const uint8_t*, size_t, ParsedJson&)’:
src/simdjson.cpp:438:34: error: aggregate ‘find_structural_bits(const uint8_t*, size_t, ParsedJson&)::avx_processed_utf_bytes previous’ has incomplete type and cannot be defined
struct avx_processed_utf_bytes previous;
^~~~~~~~
src/simdjson.cpp:480:20: error: ‘avxcheckUTF8Bytes’ was not declared in this scope
previous = avxcheckUTF8Bytes(input_lo, &previous, &has_error);
^~~~~~~~~~~~~~~~~
src/simdjson.cpp:647:20: error: ‘avxcheckUTF8Bytes’ was not declared in this scope
previous = avxcheckUTF8Bytes(input_lo, &previous, &has_error);
^~~~~~~~~~~~~~~~~
In file included from simdjson.cpp:635:
src/simdjson.cpp: In function ‘uint64_t cmp_mask_against_input(__m256i, __m256i, __m256i ’:
src/simdjson.cpp:418:24: note: The ABI for passing parameters with 32-byte alignment has changed in GCC 4.6
really_inline uint64_t cmp_mask_against_input(__m256i input_lo, __m256i input_hi,
^~~~~~~~~~~~~~~~~~~~~~
error: command 'gcc' failed with exit status 1
```
*Versions*
Python 3.7.1
gcc (GCC) 8.2.1 20181127 | closed | 2019-02-24T13:32:30Z | 2019-02-25T01:24:29Z | https://github.com/TkTech/pysimdjson/issues/8 | [
"wontfix"
] | kootenpv | 5 |
TkTech/pysimdjson | python-bindings | 7 | Cannot install from pip on linux: src/simdjson.h: No such file or directory | closed | 2019-02-24T13:30:33Z | 2019-02-24T19:53:06Z | https://github.com/TkTech/pysimdjson/issues/7 | [
"bug"
] | kootenpv | 2 |
|
TkTech/pysimdjson | python-bindings | 6 | Support negative array subscripts in query syntax. | Currently when using a query path you can only retrieve an entire list (ex: `.results[].id`), which is sub-optimal. We should support the typical python slice syntax:
- [x] `.results[0].id` (single) - first element (added in 43e2f2d)
- [x] `.results[:2].id` (array) - first 2 elements (added in 43e2f2d)
- [ ] `.results[-2:].id` (array) - last 2 elements. | closed | 2019-02-23T21:13:03Z | 2020-06-24T23:37:09Z | https://github.com/TkTech/pysimdjson/issues/6 | [
"enhancement"
] | TkTech | 4 |
TkTech/pysimdjson | python-bindings | 5 | Flesh out documentation. | Documentation is now auto-generated and hosted using http://pysimdjson.tkte.ch/.
However, the documentation is very sparse, and needs to have 100% coverage.
- [x] All methods in Iterator
- [x] All methods in ParsedJson
- [ ] All syntax for `.items()` should be covered, with examples.
- [x] `Iterator` should include an example for traversing the tape.
- [ ] The non-primitive movement methods on `Iterator` like `move_forward` and `move_to_key` should include examples of usage in their docstring. | closed | 2019-02-23T21:09:12Z | 2020-07-19T01:33:24Z | https://github.com/TkTech/pysimdjson/issues/5 | [
"needs documentation"
] | TkTech | 0 |
TkTech/pysimdjson | python-bindings | 4 | Elevate CParsedJson::iterator to a first-class citizen with direct python access. | Directly accessing the iterator and its interfaces will be essential for top performance when required, however it's currently unavailable outside of the Cython interface. We should map it to `citerator` as we do with `ParsedJson` and provide a first-class interface for it.
The wrapper will also simplify lifecycle management since we don't need to shove new/try/finally/del everywhere. | closed | 2019-02-22T21:53:33Z | 2019-02-23T18:39:52Z | https://github.com/TkTech/pysimdjson/issues/4 | [] | TkTech | 0 |
TkTech/pysimdjson | python-bindings | 3 | Provide an efficient interface for getting only sections of a document. | `simdjson` is orders of magnitude faster than existing Python JSON parsers when just parsing a document. However, most of the time when using `loads()` is spent just converting primitives to Python objects, especially strings. On the `jsonexample/*` files, `ujson.loads` performs nearly as well as `pysimdjson.loads`.
We should look at implementing something akin to [jq](https://stedolan.github.io/jq/)'s filtering language, so that the filtering of the document can be done entirely in Cython and convert the minimum of results back to Python objects. | closed | 2019-02-22T16:48:07Z | 2019-02-23T18:41:24Z | https://github.com/TkTech/pysimdjson/issues/3 | [
"enhancement"
] | TkTech | 2 |
TkTech/pysimdjson | python-bindings | 2 | Cost of creating dict objects is immense and can likely be improved. | 70% of the time on random.json is spent just assigning to the dict rather than spent on parsing the JSON itself or decoding the strings. This seems unnecessarily high and can likely be improved. https://github.com/TkTech/pysimdjson/blob/master/pysimdjson.pyx#L65
(Should we drop down a level and use `PyDict_SetItem` directly?) | closed | 2019-02-22T03:48:53Z | 2019-02-22T16:48:31Z | https://github.com/TkTech/pysimdjson/issues/2 | [
"enhancement"
] | TkTech | 1 |
TkTech/pysimdjson | python-bindings | 1 | Our error messages are placeholders, improve them. | Exceptions are raised without further clarification, making them fairly useless. We should be able to provide more detail. | closed | 2019-02-22T03:45:45Z | 2019-03-06T23:16:09Z | https://github.com/TkTech/pysimdjson/issues/1 | [
"enhancement",
"upstream change required"
] | TkTech | 2 |
corpetty/py-etherscan-api | python-bindings | 131 | Error! Unable to locate ContractCode at Is this a valid Contract Address? | closed | 2024-03-20T17:06:51Z | 2024-03-20T19:00:53Z | https://github.com/corpetty/py-etherscan-api/issues/131 | [] | Oba9526 | 0 |
|
corpetty/py-etherscan-api | python-bindings | 122 | Corpetty | open | 2022-04-02T10:40:17Z | 2022-04-02T10:40:17Z | https://github.com/corpetty/py-etherscan-api/issues/122 | [] | arslan-raza-143 | 0 |
|
corpetty/py-etherscan-api | python-bindings | 119 | Python 3.9+ compatability | API does not work on newer version of python and there is a computability issue with newer versions. | open | 2022-02-16T00:12:07Z | 2022-02-16T00:12:07Z | https://github.com/corpetty/py-etherscan-api/issues/119 | [] | kubesqrt | 0 |
corpetty/py-etherscan-api | python-bindings | 110 | Ropsten API seems to produce 403 Bad Response? | Hello!
I would like to use your library to access the Ropsten network. I saw that the main change to switch networks was the base URL. I cloned your repo, and added a flag to the Account and Client __init__ functions for use_ropsten=False. Then added an if in the init to change the URL if that is true. Testing this produced a 403 error.
I then put the Account class back to its original state, and replaced client.py with client.ropsten.py and tried again. Again, this produced a 403 bad response.
Have you encountered this issue before, and do you know the root cause of it? If I can get this working, I will submit the code.
Thank you! | open | 2021-08-23T13:21:33Z | 2021-12-05T17:13:12Z | https://github.com/corpetty/py-etherscan-api/issues/110 | [] | walesdata | 4 |
corpetty/py-etherscan-api | python-bindings | 100 | how to figure out the number of decimals? | Using the method get_token_balance(address=my_address) to get the token balance for an address, the output does not take into account the number of decimals. For example:
fetching USDC (contract address 0xdac17f958d2ee523a2206206994597c13d831ec7) token balance returns a number that needs to be divided by 1e+6 (i.e. 6 decimal places):
Result: {"status":"1","message":"OK","result":"87000000000"} --> actual value = 87,000
But for many other tokens, it needs to be divided by 1e+18:
For example, for aWETH (contract address 0x030ba81f1c18d280636f32af80b9aad02cf0854e):
Result: {"status":"1","message":"OK","result":"200004568518412516545"} --> actual value = 200.004568518412516545
Question is how can we know the divisor / i.e. how many decimals is in the result? | closed | 2021-05-08T02:46:12Z | 2021-05-15T01:38:05Z | https://github.com/corpetty/py-etherscan-api/issues/100 | [] | chiwalfrm | 1 |
corpetty/py-etherscan-api | python-bindings | 97 | Jobs | open | 2021-02-08T10:24:27Z | 2021-02-08T10:24:27Z | https://github.com/corpetty/py-etherscan-api/issues/97 | [] | abbaskiko | 0 |
|
corpetty/py-etherscan-api | python-bindings | 91 | etherscan.client.EmptyResponse | hello when execute api.get_balance_multiple() it raises this error
when i call
api = Account(address=[list of adress], api_key=one_key_in_string)
balances = api.get_balance_multiple()
this works about one year ago now i dont know why it fail
```
balances = api.get_balance_multiple()
File "/usr/local/lib/python3.6/dist-packages/etherscan/accounts.py", line 24, in get_balance_multiple
req = self.connect()
File "/usr/local/lib/python3.6/dist-packages/etherscan/client.py", line 123, i n connect
raise EmptyResponse(data.get('message', 'no message'))
etherscan.client.EmptyResponse: <Err: NOTOK>
```
| open | 2020-12-11T02:42:43Z | 2021-11-04T09:53:03Z | https://github.com/corpetty/py-etherscan-api/issues/91 | [] | EnriqueGautoSand | 1 |
corpetty/py-etherscan-api | python-bindings | 90 | are there any equivalent methods in this tools for these two methods ? api.get_ext_transactions(), api.get_int_transactions() | are there any equivalent methods in this tools for these two methods ? api.get_ext_transactions(), api.get_int_transactions() | open | 2020-12-10T20:22:03Z | 2021-11-04T09:53:53Z | https://github.com/corpetty/py-etherscan-api/issues/90 | [] | kalkite | 1 |
corpetty/py-etherscan-api | python-bindings | 89 | blocks = api.get_all_blocks_mined(offset=10000, blocktype='uncles') tried this | OK
page 1 added
OK
page 2 added
OK
page 3 added
OK
page 4 added
OK
page 5 added
OK
page 6 added
OK
page 7 added
OK
page 8 added
---------------------------------------------------------------------------
EmptyResponse Traceback (most recent call last)
<ipython-input-142-2b8eabc7d0bb> in <module>()
----> 1 blocks = api.get_all_blocks_mined(offset=10000, blocktype='uncles')
/export/home/rkalak/.local/lib/python3.6/site-packages/etherscan/accounts.py in get_all_blocks_mined(self, blocktype, offset)
133 while True:
134 self.build_url()
--> 135 req = self.connect()
136 print(req['message'])
137 if "No transactions found" in req['message']:
/export/home/rkalak/.local/lib/python3.6/site-packages/etherscan/client.py in connect(self)
121 return data
122 else:
--> 123 raise EmptyResponse(data.get('message', 'no message'))
124 raise BadRequest(
125 "Problem with connection, status code: %s" % req.status_code)
EmptyResponse: <Err: No transactions found>
| open | 2020-12-10T19:27:14Z | 2022-11-05T06:04:24Z | https://github.com/corpetty/py-etherscan-api/issues/89 | [] | kalkite | 1 |
corpetty/py-etherscan-api | python-bindings | 88 | i tried to get the all the transactions api.get_all_transactions() by using this. it gives error like this. | EmptyResponse Traceback (most recent call last)
<ipython-input-113-51999cdf1b82> in <module>()
----> 1 trans = api.get_all_transactions()
/export/home/rkalak/.local/lib/python3.6/site-packages/etherscan/accounts.py in get_all_transactions(self, offset, sort, internal)
90 while True:
91 self.build_url()
---> 92 req = self.connect()
93 if "No transactions found" in req['message']:
94 print(
/export/home/rkalak/.local/lib/python3.6/site-packages/etherscan/client.py in connect(self)
121 return data
122 else:
--> 123 raise EmptyResponse(data.get('message', 'no message'))
124 raise BadRequest(
125 "Problem with connection, status code: %s" % req.status_code)
EmptyResponse: <Err: Result window is too large, PageNo x Offset size must be less than or equal to 10000> | open | 2020-12-10T19:01:50Z | 2022-02-23T23:19:51Z | https://github.com/corpetty/py-etherscan-api/issues/88 | [] | kalkite | 0 |
corpetty/py-etherscan-api | python-bindings | 86 | pip install has different version than repo | after installing via pip, I run into the problem:
```
from etherscan.transactions import Transactions
```
**ModuleNotFoundError: No module named 'etherscan.transactions'**
I do not encounter this issue when I simply clone and install manually. | open | 2020-09-21T14:25:33Z | 2020-09-21T14:25:33Z | https://github.com/corpetty/py-etherscan-api/issues/86 | [] | pcko1 | 0 |
End of preview. Expand
in Data Studio
README.md exists but content is empty.
- Downloads last month
- 10