Personally, I simply don't really understand the aversion for merge
commits. The need to recreate the "master" branch locally after a
release has bitten me several times (git lets you screw that up very
easily...), and it has always been a bit frustrating.
Regards
Antoine.
Le 26/11/2020 à 02
Also note that drone.io supports linux-arm64 which we use in conda-forge for
this architecture and is already setup in crossbow (although we had issues with
branches not being seen).
On Thu, Nov 26, 2020, at 1:31 AM, Jeroen Ooms wrote:
> On Wed, Nov 25, 2020 at 10:54 PM Sutou Kouhei wrote:
> >
Arrow Build Report for Job nightly-2020-11-26-0
All tasks:
https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-11-26-0
Failed Tasks:
- conda-win-vs2017-py38:
URL:
https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-11-26-0-azure-conda-win-vs2017-py38
- te
I have also used the pattern of releasing from a release branch and
cherry-picking (as opposed to merge) fixes from main to the release branch
as needed for the release (on commercial software products), and it worked
well.
As long as you have a regular and frequent release schedule (as Arrow does
Hello,
Python 3.5 is not supported upstream, neither by the CPython development
team nor by third-party projects such as NumPy.
Our CI for Python 3.5 has just started failing because a dependency of
pytest doesn't support it anymore:
https://github.com/apache/arrow/runs/1458449054?check_suite_f
+1 on dropping Python 3.5
On Thu, 26 Nov 2020 at 12:26, Antoine Pitrou wrote:
>
> Hello,
>
> Python 3.5 is not supported upstream, neither by the CPython development
> team nor by third-party projects such as NumPy.
>
> Our CI for Python 3.5 has just started failing because a dependency of
> pyt
Note that we already released from a branch in the past, for the 1.0.1
release, if I am not mistaken. In this case we cherry-picked the
patches for the bugfix release on that release branch
(https://github.com/apache/arrow/pull/7933).
+1 to do that also for the main releases to avoid any need of fo
+1 from my side too
On Thu, Nov 26, 2020, at 1:04 PM, Joris Van den Bossche wrote:
> +1 on dropping Python 3.5
>
> On Thu, 26 Nov 2020 at 12:26, Antoine Pitrou wrote:
>
> >
> > Hello,
> >
> > Python 3.5 is not supported upstream, neither by the CPython development
> > team nor by third-party pr
Hi,
I've build arrow and python integration.
There is file `pyarrow/_compute.cpython-38-darwin.so`.
But when I try import pyarrow.compute I get error that the module is not
found.
Do I miss some flags in the building procedure? It looks like it is built
by default from setup.py
--
Best regards,
Hi Kirill,
Can you post the full traceback?
Le 26/11/2020 à 17:21, Kirill Lykov a écrit :
> Hi,
>
> I've build arrow and python integration.
> There is file `pyarrow/_compute.cpython-38-darwin.so`.
> But when I try import pyarrow.compute I get error that the module is not
> found.
> Do I miss
I followed, as usual, the build procedure described there --
https://arrow.apache.org/docs/developers/python.html
With `ARROW_PARQUET=OFF, ARROW_GANDIVA=ON` and `--inplace` option
Traceback as the following:
Python 3.8.5 (default, Jul 21 2020, 10:42:08)
[Clang 11.0.0 (clang-1100.0.33.17)] on darw
Did you enable ARROW_COMPUTE=ON when building Arrow C++?
Le 26/11/2020 à 18:07, Kirill Lykov a écrit :
> I followed, as usual, the build procedure described there --
> https://arrow.apache.org/docs/developers/python.html
> With `ARROW_PARQUET=OFF, ARROW_GANDIVA=ON` and `--inplace` option
>
> T
Sanity check, you aren’t standing in a folder which has a folder named
“pyarrow” in it from the build?
Do you get the same error if you move to your home folder and install the
wheel?
On Thu, 26 Nov 2020 at 18:18, Antoine Pitrou wrote:
>
> Did you enable ARROW_COMPUTE=ON when building Arrow C++
Could we hold off for at least a few days, I'd like to run this by some
colleagues. Are there any options for maintaining a functioning CI for
Python 3.5?
Thanks,
Micah
On Thu, Nov 26, 2020 at 4:23 AM Uwe L. Korn wrote:
> +1 from my side too
>
> On Thu, Nov 26, 2020, at 1:04 PM, Joris Van den
14 matches
Mail list logo