virthualenv alternatives and similar packages
Based on the "Development" category.
Alternatively, view virthualenv alternatives based on common mentions on social networks and blogs.
stack10.0 6.0 virthualenv VS stackThe Haskell Tool Stack
hadolint10.0 6.8 virthualenv VS hadolintDockerfile linter, validate inline bash, written in Haskell
ShellCheck10.0 8.2 virthualenv VS ShellCheckShellCheck, a static analysis tool for shell scripts
ihaskell10.0 5.7 virthualenv VS ihaskellA Haskell kernel for the Jupyter project.
haddock9.9 7.4 virthualenv VS haddockHaskell Documentation Tool
ghcide9.9 9.0 virthualenv VS ghcideA library for building Haskell IDE tooling
ghci-ng9.9 0.4 virthualenv VS ghci-ngNext generation GHCi
shake9.9 0.0 virthualenv VS shakeShake build system
intero9.9 0.4 virthualenv VS interoComplete interactive development program for Haskell
niv9.9 2.1 virthualenv VS nivEasy dependency management for Nix projects
hlint9.9 8.6 virthualenv VS hlintHaskell source code suggestions
ghcid9.9 0.0 virthualenv VS ghcidVery low feature GHCi based IDE
ormolu9.9 6.6 virthualenv VS ormoluA formatter for Haskell source code
ghc-mod9.9 0.0 virthualenv VS ghc-modHappy Haskell Programming
haddock-api9.9 7.4 virthualenv VS haddock-apiHaskell Documentation Tool
leksah9.9 2.5 virthualenv VS leksahHaskell IDE
hoogle9.9 4.0 virthualenv VS hoogleHaskell API search engine
hie-core9.9 9.9 virthualenv VS hie-coreThe Daml smart contract language
hpack9.8 5.0 virthualenv VS hpackhpack: A modern format for Haskell packages
stan9.8 4.0 virthualenv VS stan🕵️ Haskell STatic ANalyser
criterion9.8 5.0 virthualenv VS criterionA powerful but simple library for measuring the performance of Haskell code.
haskell-lsp9.8 5.9 virthualenv VS haskell-lspHaskell library for the Microsoft Language Server Protocol
hindent9.8 6.0 virthualenv VS hindentHaskell pretty printer
cabal-install-parsersScripts and instructions for using CI services (e.g. Travis CI or Appveyor) with multiple GHC configurations
stgi9.8 0.0 virthualenv VS stgiA user-centric visual STG implementation to help understand GHC/Haskell's execution model.
structured-haskell-modeStructured editing minor mode for Haskell in Emacs
retrie9.8 1.6 virthualenv VS retrieRetrie is a powerful, easy-to-use codemodding tool for Haskell.
H9.8 0.0 virthualenv VS HThe full power of R in Haskell.
shelly9.8 2.5 virthualenv VS shellyHaskell shell scripting
inline-c9.7 3.5 virthualenv VS inline-cWrite Haskell source files including C code inline. No FFI required.
inline-java9.7 0.0 virthualenv VS inline-javaHaskell/Java interop via inline Java code in Haskell modules.
alex9.7 2.8 virthualenv VS alexA lexical analyser generator for Haskell
happy9.7 1.0 virthualenv VS happyThe Happy parser generator for Haskell
elm-make9.7 0.0 virthualenv VS elm-makeA build tool for Elm projects
gi-atk9.7 0.0 virthualenv VS gi-atkGenerate Haskell bindings for GObject-Introspection capable libraries
nixfmt9.7 1.0 virthualenv VS nixfmtA formatter for Nix code
gtk2hs-buildtools9.7 0.0 virthualenv VS gtk2hs-buildtoolsGUI library for Haskell based on GTK+
curryrs9.7 0.0 virthualenv VS curryrsBridge the gap between Haskell and Rust
lambdabot-core9.6 0.0 virthualenv VS lambdabot-coreA friendly IRC bot and apprentice coder, written in Haskell.
fourmolu9.6 8.8 virthualenv VS fourmoluA fourk of ormolu that uses four space indentation and allows arbitrary configuration. Don't like it? PRs welcome!
c2hs9.6 1.6 virthualenv VS c2hsc2hs is a pre-processor for Haskell FFI bindings to C libraries
halive9.6 0.0 virthualenv VS haliveLive recompiler for Haskell
scion9.6 0.0 virthualenv VS scionOLD, DEPRECATED: Use this instead https://github.com/haskell/haskell-ide-engine
lit9.6 0.0 virthualenv VS litA modern tool for literate programming
hie-bios9.6 5.8 virthualenv VS hie-biosSet up a GHC API session for various Haskell Projects
lambdabot9.6 0.0 virthualenv VS lambdabotA friendly IRC bot and apprentice coder, written in Haskell.
git-gpush9.6 0.0 virthualenv VS git-gpushMore intelligent push-to-GitHub utility.
threadscope9.5 1.6 virthualenv VS threadscopeA graphical tool for profiling parallel Haskell programs
Access the most powerful time series database as a service
Do you think we are missing an alternative of virthualenv or a related project?
Virtual Haskell Environment
virthualenv is deprecated, please use the hsenv tool.
What is it?
virthualenv is a tool (inspired by Python's virtualenv) to create isolated Haskell environments.
What does it do?
It creates a sandboxed environment in a .virthualenv/ sub-directory of your project, which, when activated, allows you to use regular Haskell tools (ghc, ghci, ghc-pkg, cabal) to manage your Haskell code and environment. It's possible to create an environment, that uses different GHC version than your currently installed. Very simple emacs integration mode is included.
First, choose a directory where you want to keep your sandboxed Haskell environment, usually a good choice is a directory containing your cabalized project (if you want to work on a few projects (perhaps an app and its dependent library), just choose any of them, it doesn't really matter). Enter that directory:
Next, create your new isolated Haskell environment (this is a one time only (per environment) step):
Now, every time you want to use this environment, you have to activate it:
That's it! Now it's possible to use all regular Haskell tools like usual, but it won't affect your global/system's Haskell environment, and also your per-user environment (from ~/.cabal and ~/.ghc) will stay the same. All cabal-installed packages will be private to this environment, and also the external environments (global and user) will not affect it (this environment will only inherit very basic packages, mostly ghc and Cabal and their deps).
When you're done working with this environment, enter command 'deactivate', or just close the current shell (with exit).
Here's the most advanced usage of virthualenv. Let's say you want to:
- hack on json library
- do so comfortably
- use your own version of parsec library
- and do all this using nightly version of GHC
First, download binary distribution of GHC for your platform (e.g. ghc-7.3.20111105-i386-unknown-linux.tar.bz2).
Create a directory for you environment:
mkdir /tmp/test; cd /tmp/test
Then, create a new environment using that GHC:
Download a copy of json library and your private version of parsec:
darcs get http://patch-tag.com/r/Paczesiowa/parsec; cabal unpack json
cd parsec2; cabal install
Install the rest of json deps:
cd ../json-0.5; cabal install --only-dependencies
Now, let's say you want to hack on Parsec module of json library. Open it in emacs:
Activate the virtual environment (virthualenv must be required earlier):
M-x virthualenv-activate /tmp/test/
Edit some code and load it in ghci using 'C-c C-l'. If it type checks, you can play around with the code using nightly version of ghci running in your virtual environment. When you're happy with the code, exit emacs and install your edited json library:
And that's it.
virthualenv has been tested on i386 Linux and FreeBSD systems, but it should work on any Posix platform. External (from tarball) GHC feature requires binary GHC distribution compiled for your platform, that can be extracted with tar and installed with "./configure --prefix=PATH; make install".
Q: Can I use it together with tools like cabal-dev or capri?
A: No. All these tools work more or less the same (wrapping cabal command, setting GHC_PACKAGE_PATH env variable), so something will probably break.
Q: Using GHC from tarball fails, when using FreeBSD with a bunch of make tool
gibberish. What do I do?
A: Try '--make-cmd=gmake' switch.
Q: Can I use virthualenv inside virthualenv?
A: No. It may be supported in future versions.
Q: Does it work on x64 systems?
A: It hasn't been tested, but there's no reason why it shouldn't.
Q: Will it work on Mac?
A: I doubt it. It should be easy to make it work there with system's GHC, Using GHC from tarball will be probably harder. I don't have any mac machines, so you're on your own, but patches/ideas/questions are welcome.
Q: Will it work on Windows?
A: I really doubt it would even compile. I don't have access to any windows machines, so you're on your own, but patches/ideas/questions are welcome. Maybe it would work on cygwin.
Q: Does it require bash?
A: No, it should work with any POSIX-compliant shell. It's been tested with bash, bash --posix, dash, zsh and ksh.
Q: Can I use it with a different haskell package repository than hackage?
A: Yes, just adjust the url in .virthualenv/cabal/config file.
Q: How do I remove the whole virtual environment?
A: If it's activated - 'deactivate' it. Then, delete the .virthualenv/ directory.
Q: Is every environment completely separate from other environments and
the system environment?
A: Yes. The only (minor) exception is ghci history - there's only one per user history file. Also, if you alter your system's GHC, then virtual environments using system's GHC copy will probably break. Virtual environments using GHC from a tarball should continue to work.