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

3.5.3-1 include tk8.6 but tk8.5 is pinned #127

Closed
looooo opened this issue Mar 19, 2017 · 6 comments
Closed

3.5.3-1 include tk8.6 but tk8.5 is pinned #127

looooo opened this issue Mar 19, 2017 · 6 comments

Comments

@looooo
Copy link

looooo commented Mar 19, 2017

when trying to build a library with win I get errors because there are two versions of tk available. One is directly shiped with the python packacge and this is 8.6.

@looooo
Copy link
Author

looooo commented Mar 19, 2017

I don't know if my problem is really related to this, but this seems quite strange to me.

@jjhelmus
Copy link
Contributor

What platform (Windows, OS X, Linux) and version of Python are you seeing this issue with.

The Windows version of Python 3.5.3-1 includes a version of tk 8.6 which is build and packaged with Python. This is included in the official installer as well as the conda version. Installing a separate tk package into a conda environment is not recommended.

On OS X and Linux the tk package is separate from the Python package and is currently pinned at 8.5.x. This version mismatch is a bit odd but is in place to keep compatibility with the defaults channel.

@jakirkham
Copy link
Member

Is defaults still pinned to 8.5.x or have they gone to 8.6.x?

@looooo
Copy link
Author

looooo commented Mar 20, 2017

win = windows, sorry
@jjhelmus thanks for clarification.

@jjhelmus
Copy link
Contributor

defaults still seems to be pinned to 8.5.x.

Closing this issue, feel free to re-open if you feel this has not been resolved.

@looooo
Copy link
Author

looooo commented Mar 25, 2017

@jjhelmus : I can't use the tk version which is shipped with python because there are no headers available... So maybe we can reopen this issue.

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

No branches or pull requests

3 participants