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

{vis}[foss/2016a] PyBERT 1.7.9 w/Python-3.5.1 (WIP) #3446

Closed
wants to merge 2 commits into from

Conversation

hajgato
Copy link
Collaborator

@hajgato hajgato commented Aug 22, 2016

No description provided.

@hajgato hajgato changed the title {vis}[foss/2016a] PyBERT 1.7.9 w/Python-3.5.1 (WIP) {vis}[foss/2016a] PyBERT 1.7.9 w/Python-3.5.1 (REVIEW) Aug 25, 2016
@boegel boegel added this to the v2.9.0 milestone Aug 25, 2016
toolchain = {'name': 'foss', 'version': '2016a'}

source_urls = ['https://github.com/enthought/chaco/archive/']
sources = ['%s.tar.gz' % commit_id]
Copy link
Member

Choose a reason for hiding this comment

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

@hajgato 4.5.0 is the latest official release, why not use that?

Once we start diverging from official releases, we'll need to stick to it forever, since 20160817 will always be newer than 4.5.0 or any other newer version...

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@boegel I had two options. Try to do everything with Python3, as the user want to use PyBERT simultaneously with pyGIMLi. As far as I got from pyGIMLi homepage, its requires Python3. So I had to use Python3 here as well. and the latest official release is not yet Python3 compatible. I could use version4.6.0beta.20160817 (or whatever is the version claimed by the code).

Other possibility to make a Python2/2.7.11-Python-3.5.1, and use all the stuff here with that.
(chaco/4.5.0-foss-2016a-Python-2.7.11-Python-3.5.1 or so). The option to use system Python is not a good way, since PyBERT requires Python 2.7

Copy link
Member

Choose a reason for hiding this comment

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

according to http://www.pygimli.org/installation.html#optional-prerequisites, pyGIMLi is compatible with Python 2.7 as well?

Copy link
Member

@boegel boegel Aug 26, 2016

Choose a reason for hiding this comment

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

also, I'm not sure what Python2/2.7.11-Python-3.5.1 is? is that Python 2 and 3 combined? that's a nice recipe for disaster ;)

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Ok, for the future what is the recipe to use python2 and python3 together. Ok, in this project it is not needed, but if in the future this problem will pop up? If I have a linux distro, I can have both, and most of the cases its not a disaster.

Copy link
Member

Choose a reason for hiding this comment

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

I think the right approach would be to make a Python2/2.7.11-* module, and load Python (3) and Python2 together as deps

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

How do you prevent users to load python (2) and python2 module together? I think that's also a recipe for disaster (for example which order did they loaded it)

Copy link
Member

Choose a reason for hiding this comment

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

Nothing would break then, one module would just shadow the other?

@hajgato hajgato changed the title {vis}[foss/2016a] PyBERT 1.7.9 w/Python-3.5.1 (REVIEW) {vis}[foss/2016a] PyBERT 1.7.9 w/Python-3.5.1 (WIP) Aug 26, 2016
@hajgato
Copy link
Collaborator Author

hajgato commented Aug 26, 2016

@boegel I can confirm that PyBERT does not work (prblem with the matplotlib interface)

@hajgato
Copy link
Collaborator Author

hajgato commented Aug 26, 2016

@boegel: Ok, I found the error, it needs an old version of SWIG

@hajgato
Copy link
Collaborator Author

hajgato commented Aug 26, 2016

@boegel: I put this back as WIP, and I will make a bundle.

@hajgato
Copy link
Collaborator Author

hajgato commented Aug 26, 2016

Python2 version will be made.

@hajgato hajgato closed this Aug 26, 2016
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