HaPy alternatives and similar packages
Based on the "Foreign" category.
Alternatively, view HaPy alternatives based on common mentions on social networks and blogs.
-
tasty-lua
DISCONTINUED. Integrate Lua tests into tasty. This package is now part of the hslua monorepo. -
hslua-module-text
DISCONTINUED. Lua module providing a selected set of operations on Text. NOTE: moved into the hslua monorepo. -
hslua-module-system
DISCONTINUED. HsLua module for system and directory functions. This repository has been moved to the hslua monorepo. -
foreign-storable-asymmetric
DISCONTINUED. Types and instances for implementing a Storable with different peek and poke
SaaSHub - Software Alternatives and Reviews
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of HaPy or a related project?
README
HaPy
Call Haskell functions from Python! HaPy is set of Haskell bindings for Python. Initially written in 2011 as a final project for Stanford's CS240H Haskell class by Ashwin Siripurapu, William Rowan, and David Fisher. Now rewritten mostly from scratch by David Fisher with different tradeoffs (gaining far more stability at the expense of initial setup).
Table of Contents
- Ubuntu Installation and Usage
- OS X/General Installation and Usage
- Common Errors
- FAQ
- Caveats
- Future development
Ubuntu Installation and Usage:
- Install the dynamic base libraries with
sudo apt-get install ghc-dynamic
. - Follow the steps of the OS X/General Installation below.
OS X/General Installation and Usage:
- Pre-installation assumptions: (if you don't meet these, please consult the appropriate project's documentation for more information)
- In the directory of your Haskell project:
- Update your cabal file:
- Add HaPy to your build-depends. You should have a line that looks like this:
build-depends: [other haskell dependencies, if any], HaPy == 0.1.*
. - Add the GHC RTS library to your extra-libraries. The line should look like this:
extra-libraries: HSrts-ghc7.6.3
. IMPORTANT: You must update this line to refer to your current version of GHC. (This is slightly annoying, but I haven't been able to find a better way to do this.) - Make a FFI export Haskell module. Due to Template Haskell restrictions, this must be in a different module from any functions you are exporting. See:
example/haskell/Export.hs
.
- Add HaPy to your build-depends. You should have a line that looks like this:
- If you're not already using one, create a cabal sandbox with
cabal sandbox init
. - Build and install your Haskell module to your local sanbox with
cabal install --enable-shared
. - Copy the compiled .so (on Linux) or .dylib (on OS X) file from
dist/dist-sandbox-*/build/
to your Python project directory.
- Update your cabal file:
- In your Python project:
- Install the Python library with
sudo pip install hapy-ffi
. - Import your Haskell module with
from HaPy import HASKELL_MODULE_NAME
. - Call Haskell functions from Python, just like you would any other Python module.
- Install the Python library with
Common Errors:
- During cabal install:
- Error:
cabal: Could not resolve dependencies
--> HaPy might not be in your local package index; runcabal update
and try again. If this doesn't help, the problem probably isn't HaPy related. - Error:
Missing C library: HSrts-ghc7.8.2
(or similar) --> The version of the GHC RTS library that you specified in your cabal file doesn't match the version of GHC you're running.
- Error:
- When running your Python project:
Symbol not found: _stg_IND_STATIC_info
orundefined symbol: stg_forkOnzh
--> The GHC RTS library isn't specified as one of the extra-libraries in the cabal file of your Haskell project. See the General Installation and Usage section above.
- Anything else: please make an issue and I'll take a look!
FAQ:
None yet! Feel free to start an issue if there's something you don't understand.
Caveats:
- Only functions of certain types can be exported. Currently supported types:
- Bool
- Char
- Int
- Double
- String
- Lists (at any level of nesting) of all the above types (e.g. [Int], [[Int]], etc.)
- The FFI adds some overhead: all values are copied twice (e.g. from the Python representation to the C representation to the Haskell representation).
Future development:
- Near term:
- Allow the compiled Haskell binary to be in appropriate other directories
- Under consideration:
- Automatically compile Haskell library from Python
- Automatically generate Template Haskell export file in Python
- Add support for passing Python functions
- Add support for tuples