Skip to content
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

PERF: follow up to ASV #10849

Closed
4 of 8 tasks
jreback opened this issue Aug 19, 2015 · 12 comments
Closed
4 of 8 tasks

PERF: follow up to ASV #10849

jreback opened this issue Aug 19, 2015 · 12 comments
Labels
good first issue Performance Memory or execution speed performance

Comments

@jreback
Copy link
Contributor

jreback commented Aug 19, 2015

xref #9715

  • add docs on how to use / add tests (in contributing.md / contributing.rst)
  • add/update vbenches to current
  • whatsnew note (put in highlites that this is added)
  • test on Windows (basicly works, but had to do some small adjustments)
  • get it working with python 3
  • clean up autogenerated tests
    • fix failing tests
    • remove redundancy (by putting things in classes and reusing setup, .

cc @qwhelan

@jreback jreback added the Performance Memory or execution speed performance label Aug 19, 2015
@jreback jreback added this to the 0.17.0 milestone Aug 19, 2015
@jorisvandenbossche
Copy link
Member

Added:

  • test on Windows (basicly works, but had to do some small adjustments):
    • eg needs libpython to build -> I don't know how it is possible to specify something windows only in the yaml file
  • clean up autogenerated tests:
    • fix failing tests
    • remove redundancy (by putting things in classes and reusing setup, ..)

Maybe I can find some people for this on the EuroScipy sprint if it is not yet done before that.

@jreback
Copy link
Contributor Author

jreback commented Aug 19, 2015

@jorisvandenbossche awesome!

@jreback
Copy link
Contributor Author

jreback commented Aug 19, 2015

note that I disabled the 3.4 support (was failing anyhow) for now.

@jreback jreback modified the milestones: 0.17.0, Next Major Release Aug 19, 2015
@qwhelan
Copy link
Contributor

qwhelan commented Aug 21, 2015

I've fixed the translation script a bit to move functions from inside setup() to the class-level, so the majority of failures outside eval.py should be fixed.

I also have the suite running under Python 3 - I'll have to look into the current results in the morning but it looks promising.

@TomAugspurger
Copy link
Contributor

Great. @qwhelan I'm curious what cause the py3 failures? Was it a change in how imports are handled?

@qwhelan
Copy link
Contributor

qwhelan commented Aug 21, 2015

@TomAugspurger Partially, the changes were:

  • from pandas_vb_common import * -> from .pandas_vb_common import *
  • Replace xrange with range and add from pandas.compat import range in pandas_vb_common
  • Replace string.uppercase with string.ascii_uppercase

There are probably a few others, but the vast majority seem to be working with the above changes.

@jorisvandenbossche
Copy link
Member

@qwhelan could you push what you already did on this? Possibly there could be some people to sprint on this on Sunday, so then for that case best to start with your latest version!

@qwhelan
Copy link
Contributor

qwhelan commented Aug 29, 2015

@jorisvandenbossche Definitely, I'll squash down the commits tonight. There's a bit of updating of docs still needed and I don't want to waste any of the EuroScipy's folks' time reverse engineering my failure to document something, so I'll take care of that as well.

Sorry about being spotty on this - job interviews have been sucking me dry lately.

@max-sixty
Copy link
Contributor

Is this closed? Some of the things like python3 work

@jorisvandenbossche
Copy link
Member

The "clean up autogenerated tests" is not yet fully finished. I am not fully sure about windows.

@jbrockmendel
Copy link
Member

the py3 checkbox must be fixed right? auto-generated probably too

@mroeschke
Copy link
Member

Yeah, I think we could close this issue and open up a separate issue about Windows if that's still an issue...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Performance Memory or execution speed performance
Projects
None yet
Development

No branches or pull requests

7 participants