Please look at the proposed naming scheme and the changes for consumers of aperturedb-python.
The major external impact of the change is the refactor of execute_batch out form ParallelQuery.
A Backward compatibility method is provided, but it'll log depreciation warnings.
The tests still work through that compatibility mechanism.
We would need to update demos and docs following this, though nothing should break, but deprecation warning .
This is an effort to generate leaner but clearer docs, and a more readable code in public repo
Addresses https://github.com/aperture-data/aperturedb-python/issues/475
Naming alert.
Please look at the proposed naming scheme and the changes for consumers of aperturedb-python. The major external impact of the change is the refactor of execute_batch out form ParallelQuery.
A Backward compatibility method is provided, but it'll log depreciation warnings. The tests still work through that compatibility mechanism.
We would need to update demos and docs following this, though nothing should break, but deprecation warning . This is an effort to generate leaner but clearer docs, and a more readable code in public repo