Skip to content

MNT: future numpy only takes ints as index - #9142

Merged
efiring merged 3 commits into
matplotlib:masterfrom
tacaswell:mnt_memleak_future_numpy
Sep 1, 2017
Merged

efiring merged 3 commits into
matplotlib:masterfrom
tacaswell:mnt_memleak_future_numpy

Conversation

@tacaswell

Copy link
Copy Markdown
Member

Discovered this while testing for 2.1rc1

@tacaswell tacaswell added this to the 2.1 (next point release) milestone Sep 1, 2017
@tacaswell tacaswell mentioned this pull request Sep 1, 2017
Comment thread unit/memleak.py Outdated
tracemalloc.start()

starti = min(50, iterations / 2)
starti = int(min(50, iterations / 2))

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

min(50, iterations // 2) looks idiomatic.

@efiring
efiring merged commit d02024e into matplotlib:master Sep 1, 2017
@tacaswell
tacaswell deleted the mnt_memleak_future_numpy branch September 1, 2017 13:33
tacaswell pushed a commit that referenced this pull request Sep 1, 2017
MNT: future numpy only takes ints as index
@tacaswell

Copy link
Copy Markdown
Member Author

backported to v2.1.x as 67d1299

dstansby pushed a commit to dstansby/matplotlib that referenced this pull request Sep 8, 2017
…numpy

MNT: future numpy only takes ints as index

Deprecate logspace

Deprecate frange
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants