Re: pyarrow versioning

2017-08-07 Thread Colin Nichols
Ah ok, makes sense -- thanks Wes! - Colin *Colin Nichols | Senior Software Engineer335 Madison Avenue, 16F | New York, NY, 10017+1 (646) 912 2018 | BAM.ai* On Mon, Aug 7, 2017 at 3:55 PM, Wes McKinney wrote: > hi Colin, > > Sorry about that. Yes, I pulled the 0.5.0 packages from PyPI (which i

Re: pyarrow versioning

2017-08-07 Thread Wes McKinney
hi Colin, Sorry about that. Yes, I pulled the 0.5.0 packages from PyPI (which is an unofficial package, because the Arrow PMC has not voted on it) because of the problems with jemalloc in ARROW-1282 -- it is not possible to replace a broken package without also changing the version number. This is

pyarrow versioning

2017-08-07 Thread Colin Nichols
Hi all, I noticed today that pyarrow==0.5.0 has disappeared from Pypi, replaced by 0.5.0.post2. Just wanted to make sure that was intended. If so, is the expectation that users put e.g., pyarrow~=0.5.0 in their requirements file as opposed to pyarrow==0.5.0? Thank you, Colin *Colin Nichols |