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

Not Python 2.6 compatible #36

Closed
kynan opened this issue Oct 15, 2013 · 7 comments
Closed

Not Python 2.6 compatible #36

kynan opened this issue Oct 15, 2013 · 7 comments
Labels

Comments

@kynan
Copy link
Member

kynan commented Oct 15, 2013

The core_types extension module is not compatible with Python 2.6 due to the use of capsules, which were introduced in 2.7.

A possible workaround would be introducing a compatibility header that redefines PyCapsule C API calls in terms of PyCObject.

@kynan
Copy link
Member Author

kynan commented Oct 15, 2013

Fixed in c2415d3

@kynan kynan closed this as completed Oct 15, 2013
@kynan kynan reopened this Oct 17, 2013
@kynan
Copy link
Member Author

kynan commented Oct 17, 2013

Turns out this isn't quite fixed yet. For reasons I can't quite tell the build on 2.6 still fails.

@wence-
Copy link
Contributor

wence- commented Feb 23, 2014

I sort of don't care about this. 2.7 is not /that/ new. Is there a compelling reason to tie ourselves in knots to support 2.6? I'd be more worried about forward compatibility to 3.4.

@kynan
Copy link
Member Author

kynan commented Feb 23, 2014

There's certainly no reason to care about 2.6 other than deploying to clusters. I agree that we should rather start worrying about forward compatibility.

@ggorman
Copy link

ggorman commented Feb 23, 2014

I believe the future for deployment on clusters and supercomputers is via python platforms such as Anaconda. This is resolving many ongoing python/numpy/scipy issues for us on HECToR/ARCHER. In addition, Andy Terrel and Continuum are working with Cray to sort out scalability etc. so this approach is gaining momentum.

ie - we really don’t care about 2.6 etc.

@kynan
Copy link
Member Author

kynan commented Feb 23, 2014

Yes, if we could have a recent Anaconda distribution on HPC clusters that would be fantastic. With that 2.6 would not be a concern, but we should keep forward compatibility in mind.

@wence-
Copy link
Contributor

wence- commented Mar 31, 2014

Closing this, since we've decided we don't care enough about 2.6

@wence- wence- closed this as completed Mar 31, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants