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

creates a virtual environment for encorec #107

Merged
merged 3 commits into from
Apr 18, 2015

Conversation

kikofernandez
Copy link
Contributor

This was merged in new-ponyrt but not in master. master does not have this change and therefore, diverges from new-ponyrt. As soon as this pull request is merged, we can conclude that new-ponyrt has been merged with master.

I do not want to be the first one that breaks the pull request policy and need someone to merge this pull request :)

Kiko Fernandez Reyes added 3 commits February 27, 2015 16:25
the idea is to create a virtual environment similar to what you
can expect in virtualenv (python) and/or rbenv (ruby). At the moment
it just sets the encore compiler to the right path. Therefore, forking
and having multiple copies of the repo with multiple compilers is
easy to handle. Steps involved:

  1. go to the encore compiler fork you would like to activate
  2. source activate
  3. from this terminal, you can compile any encore program and
     it will safely use the encore compiler that you jut activated.

missing features:

  - no real dependency management yet, so no need to create new folder
creates a virtual environment for encore
@supercooldave
Copy link

You are safely not the first to break the pull request policy.
Remember the cake on Thursday!

supercooldave pushed a commit that referenced this pull request Apr 18, 2015
creates a virtual environment for encorec
@supercooldave supercooldave merged commit aa5929d into parapluu:master Apr 18, 2015
@kikofernandez
Copy link
Contributor Author

No merge => no crime!

@kaeluka
Copy link
Contributor

kaeluka commented Apr 18, 2015

Question: this branch was merged but not deleted. IMO there's no reason to leave the branch lying around, am I right? Can we delete the branch?

@kikofernandez kikofernandez deleted the feature/virtualenv branch April 18, 2015 16:50
@kikofernandez
Copy link
Contributor Author

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