mirror of
https://github.com/apache/impala.git
synced 2025-12-22 19:35:22 -05:00
9e76a8f7c3
We are going to publish impala-shell release 4.1.0a1 on PyPi. This patch upgrades following three python libraries which are used for generating egg files when building impala-shell tarball. upgrade bitarray from 1.2.1 to 2.3.0 upgrade prettytable from 0.7.1 to 0.7.2 upgrade thrift_sasl from 0.4.2 to 0.4.3 Updates shell/packaging/requirements.txt for the versions of dependent Python libraries. Testing: - Ran core tests. - Built impala-shell package impala_shell-4.1.0a1.tar.gz, installed impala-shell package from local impala_shell-4.1.0a1.tar.gz, verified impala-shell was installed in ~/.local/lib/python2.7/site-packages. Verified the version of installed impala-shell and dependent Python libraries as expected. - Set IMPALA_SHELL_HOME as ~/.local/lib/python2.7/site-packages/ impala_shell, copied over egg files under installed impala-shell python package so we can run the end-to-end unit tests against the impala-shell installed with the package downloaded from PyPi. Passed end-to-end impala-shell unit tests. - Verified the impala-shell tarball generated by shell/make_shell_tarball.sh. Change-Id: I378404e2407396d4de3bb0eea4d49a9c5bb4e46a Reviewed-on: http://gerrit.cloudera.org:8080/17826 Reviewed-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com> Tested-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>
32 lines
1.4 KiB
Markdown
32 lines
1.4 KiB
Markdown
Contributing to bitarray
|
|
========================
|
|
|
|
The bitarray type is very stable and feature complete at this point,
|
|
which means that pull requests to `bitarray/_bitarray.c` will most likely
|
|
be rejected, unless they improve readability and performance.
|
|
|
|
There may be room for improvements/additions in the `bitarray.util` module,
|
|
added in the 1.2.0 release. However, due to the slow release cycle of this
|
|
package, it may be more practical to create your own library which depends
|
|
on bitarray. This is completely possible, even on the C-level. Please
|
|
study the implementation of `bitarray/_util.c` for details. In particular for
|
|
C extensions to work with the bitarray type, it is important that
|
|
the `bitarrayobject` struct is defined in the same way:
|
|
|
|
typedef struct {
|
|
PyObject_VAR_HEAD
|
|
char *ob_item; /* buffer */
|
|
Py_ssize_t allocated; /* allocated buffer size (in bytes) */
|
|
Py_ssize_t nbits; /* length of bitarray, i.e. elements */
|
|
int endian; /* bit endianness of bitarray */
|
|
int ob_exports; /* how many buffer exports */
|
|
PyObject *weakreflist; /* list of weak references */
|
|
} bitarrayobject;
|
|
|
|
/* member endian may have these values */
|
|
#define ENDIAN_LITTLE 0
|
|
#define ENDIAN_BIG 1
|
|
|
|
These essential (as well as other useful) declarations can be found
|
|
in `bitarray/bitarray.h`.
|