On Mon, Aug 19, 2019 at 8:55 AM Antoine Pitrou wrote:
>
> On Mon, 19 Aug 2019 08:44:26 -0500
> Wes McKinney wrote:
> > Will publishing only manylinux2010 wheels have any consequences (for
> > example, a relatively new version of setuptools may be required)?
>
> A relatively new version of pip is
On Mon, 19 Aug 2019 08:44:26 -0500
Wes McKinney wrote:
> Will publishing only manylinux2010 wheels have any consequences (for
> example, a relatively new version of setuptools may be required)?
A relatively new version of pip is required. But upgrading pip is
straightforward, at least in a virtu
Will publishing only manylinux2010 wheels have any consequences (for
example, a relatively new version of setuptools may be required)?
On Fri, Aug 16, 2019 at 11:58 AM Neal Richardson
wrote:
>
> For R's official support for various C++ versions, see
> https://cran.r-project.org/doc/manuals/r-rele
For R's official support for various C++ versions, see
https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Using-C_002b_002b11-code
and below. Empirically, C++ > 11 is not really used: there are only 6
packages on CRAN that declare it as a requirement, and none of those
are widely used.
$
Le 16/08/2019 à 17:11, Hatem Helal a écrit :
> Hi all,
>
> I ran into a surprising (to me) limitation when working on an issue [1]. To
> summarize, supporting the manylinux1 standard ties Arrow development to gcc
> 4.8.x which is technically not C++11 complete. This brought on few questions
Hi all,
I ran into a surprising (to me) limitation when working on an issue [1]. To
summarize, supporting the manylinux1 standard ties Arrow development to gcc
4.8.x which is technically not C++11 complete. This brought on few questions
for me:
* What are the pre-conditions for dropping many
