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 #98

Merged

Conversation

kikofernandez
Copy link
Contributor

the idea is to create a virtual environment similar to what you
can expect in virtualenv (python), rbenv (ruby), cabal (haskell). 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

credits: virtualenv

@kikofernandez
Copy link
Contributor Author

I have assigned this pull request to @TobiasWrigstad since you are the one that have many copies of the encore compiler. @kaeluka you can test as well but I cannot assign this issue to more than one person

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
kikofernandez pushed a commit that referenced this pull request Feb 27, 2015
creates a virtual environment for encore
@kikofernandez kikofernandez merged commit 1a2bd25 into parapluu:new-ponyrt Feb 27, 2015
@kikofernandez kikofernandez deleted the features/virtualenv branch February 27, 2015 15:27
@supercooldave
Copy link

Could this help later when we have a standard package library located somewhere that is imported by default (or in the import path by default)?

@kikofernandez
Copy link
Contributor Author

Definitely!

@TobiasWrigstad
Copy link
Contributor

I love this idea. Thank's kiko. I have been suffering accumulated illness following Brussels, but I hope to be back tomorrow to look at this.

@kikofernandez
Copy link
Contributor Author

right now there's not much apart from some aliases (using virtualenv as inspiration). As @supercooldave mentions, in the future I can extend this to include some external libraries.

@supercooldave
Copy link

Not external libraries -- the encore standard library.

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