I have just sent you the invitation to the PyTables mintainers team on
Il 29/12/20 20:29, Miroslav Šedivý ha scritto:
> Hi PyTables developers,
> happy to be here again and looking forward to contributing more to
> PyTables! While I have touched some non-destructive topics until now,
> there are some upcoming issues that I'd like to understand before I can
> contribute any further:
> 1. What are the supported Python versions? The current living Python
> versions are 3.6–3.9 and they are configured in the CI. In #838 I tried
> to drop the Python 3.5 (after EOL) support and Antonio correctly asked
> to deprecate it properly first. That means, that right now we're at
> Python 3.5–3.9 and the code snippet  with 3.4 in mind is just
> outdated and can be fixed?
>  https://github.com/PyTables/PyTables/blob/master/setup.py#L99-L102
In my opinion PyTables shall support only Python versions (and the same
holds for numpy, hdf5, etc) that have not reached the "end-of-life".
Some specific exception can be eventually considered if we intend to
support some specific linux distribution (Debian stable, Ubuntu x.y LTS
Also I don't think we need a deprecation period, just we shell ensure
that the PyTables code and documentation in the master branch is updated
* checks in the code
* PyPI classifiers
* README.rst, installation.rst and release notes
* python_requires in the setup.py
> Can we plan for dropping 3.5 support in the near future with proper
> announcement of the last PyTables version supporting it?
To me we can drop it immediately, in principle, as soon as we do it
properly (see above).
A question: which are features of Python 3.6 and above that you think
could be interesting to use in PyTables?
> 2. In the same PR I touched files in the `c-blosc` directory and the
> `cpuinfo.py` file, but Antonio told me they were imported (and probably
> `hdf-blosc` as well). While Francesc imports the `c-blosc` version
> frequently, the `cpuinfo.py` file get sporadic updates. What is exactly
> the reason that these two projects are not imported the same way
> `numpy` or `numexpr` are? With proper version pinning, etc. Wouldn't it
> be easier to maintain if the repository contained only its own files
> and depended on the rest?
Regarding c-blosc and hdf-blosc they contain libraries that supposedly
cannot be installed via pip.
If I understand correctly this is no longer true for c-blosc.
They are bundled with PyTable to try to make it easier for the final
user to build and install PyTables for sources.
I think this has always been a very critical point and the complexity of
the setup script is indicative in this sense.
For c-blosc we have a subtree-merge-blosc.sh script.
For hdf-blosc and cpuinfo we could also consider to use git submodule.
In any case I agree with you that we have care of updating al external
code regularly and that new PyTables releases should bundle the latest
available version of th external code.