[
https://issues.apache.org/jira/browse/ARROW-5756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17258274#comment-17258274
]
Joris Van den Bossche commented on ARROW-5756:
----------------------------------------------
Some other links:
- Matti Picus wrote a blogpost about that it is time to drop manylinux1:
https://labs.quansight.org/blog/2020/11/manylinux1-is-obsolete-manylinux2010-is-almost-eol-what-is-next/
- He raised the issue on the numpy mailing list
(https://mail.python.org/pipermail/numpy-discussion/2020-November/081196.html)
and python discussion site
(https://discuss.python.org/t/blog-post-about-manylinux-and-the-future-of-manylinux1/5734)
Now, to what extent should we tie this to our support for Python 3.6?
Because Python 3.6 ships with an older pip version (18) that does not yet
support manylinux2010 (users can of course always (and probably _should_)
upgrade the pip version, but if you don't do this, you can get quite cryptic
error messages as it will try to install from source with older pip and if no
manylinux1 wheel is available)
> [Python] Remove manylinux1 support
> ----------------------------------
>
> Key: ARROW-5756
> URL: https://issues.apache.org/jira/browse/ARROW-5756
> Project: Apache Arrow
> Issue Type: Task
> Components: Packaging, Python
> Reporter: Antoine Pitrou
> Priority: Major
>
> We should decide when we want to stop producing manylinux1 packages.
> Installing manylinux2010 packages requires a recent pip (and, obviously, a
> not-too-antiquated system, but I think that's less of a problem for us).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
