8000 Accept constant memoryviews in HashTable.lookup by xhochy · Pull Request #21688 · pandas-dev/pandas · GitHub
[go: up one dir, main page]

Skip to content

Accept constant memoryviews in HashTable.lookup #21688

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 13 commits into from
Jul 7, 2018
Prev Previous commit
Next Next commit
Start new section 'Build Changes' in whatsnew
  • Loading branch information
xhochy committed Jul 7, 2018
commit 9deaf07112f3951be41d167af14ee5d4543ca2b1
5 changes: 4 additions & 1 deletion doc/source/whatsnew/v0.24.0.txt
Original file line number Diff line number Diff line change
Expand Up @@ -410,13 +410,16 @@ Reshaping
-
-

Build Changes
^^^^^^^^^^^^^

- Building pandas for development now requires ``cython >= 0.28`` (:issue:`21688`)
-

Other
^^^^^

- :meth: `~pandas.io.formats.style.Styler.background_gradient` now takes a ``text_color_threshold`` parameter to automatically lighten the text color based on the luminance of the background color. This improves readability with dark background colors without the need to limit the background colormap range. (:issue:`21258`)
- Building pandas for development now requires ``cython >= 0.28``
- Require at least 0.28 version of cython to support read-only memoryviews (:issue:`21688`)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Referenced the PR as issue here. Is that sufficient or would you like to have separate issues for each line for documentation purposes?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so we really need to bump cython here?

Copy link
Member
@jschendel jschendel Jul 1, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assuming we need to bump Cython, it looks like there are a few things missing in order to fully bump it: pin some CI builds to the minimum Cython version, update version number in install.rst.

See the changes in #18623 for where I bumped to 0.24; should show all the places that need updating.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reading through the changelog of Cython, we need to bump to 0.28 to support the const specifier for memoryviews. Looking a bit through the Travis setup, we only pin Cython for the 2.7 builds and these are the ones that failed. (sadly with a weird error message).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we need to bump to 0.28 to support the const specifier for memoryviews

is this an actual change in cython?

I agree its nice to change this, but cython 0.28 is pretty new.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you move the building pandas to a new sub-section (like we did previously when we bumped deps, as going to do this for more deps this cycle).

also is 0.28 min, or 0.28.2?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

0.28.0 works but we should build with 0.28.2 due to the mentioned problems in sklearn. I would at least bump the Cython version on Travis & CricleCI.

Should we then allow 0.28.0 or require 0.28.2 so that we don't get the bug reports w.r.t. problems that are fixes in .2?

-
-
Expand Down
0