Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / ejgallego/pycoq issues and pull requests
#30 - Can't install this
Issue -
State: open - Opened by enjoysmath over 1 year ago
- 2 comments
#29 - pip install cam run arbitrary code -- including make install -- through the setup.py file
Issue -
State: open - Opened by brando90 over 1 year ago
#28 - Why does one need to run a test file to use pycoq?
Issue -
State: open - Opened by brando90 over 1 year ago
- 1 comment
#27 - Why do we need to do git submodules for installing a normal python package?
Issue -
State: open - Opened by brando90 almost 2 years ago
- 1 comment
#26 - How to remove make install and dune to run pycoq?
Issue -
State: open - Opened by brando90 almost 2 years ago
- 1 comment
#25 - ppx_base not found during installation
Issue -
State: open - Opened by brando90 almost 2 years ago
- 2 comments
#24 - installation
Issue -
State: open - Opened by ASamSam almost 2 years ago
- 16 comments
#23 - installation
Issue -
State: closed - Opened by ASamSam almost 2 years ago
- 3 comments
#22 - why do we need os.chdir('_build/default')?
Issue -
State: open - Opened by brando90 over 2 years ago
- 1 comment
#21 - Data set for machine learning compatible with PyCoq
Issue -
State: open - Opened by brando90 over 2 years ago
- 1 comment
#20 - Can CoqGym's data be used with PyCoq?
Issue -
State: open - Opened by brando90 almost 3 years ago
- 1 comment
#19 - Can't make
Issue -
State: closed - Opened by inpefess almost 3 years ago
#18 - Trouble installing
Issue -
State: closed - Opened by ju-sh almost 3 years ago
- 1 comment
#17 - nixify
Issue -
State: open - Opened by quinn-dougherty about 3 years ago
- 4 comments
#16 - Rename `test` to `examples`
Pull Request -
State: open - Opened by quinn-dougherty about 3 years ago
- 2 comments
#15 - return objects should probably be dicts instead of nested 2-tuples
Issue -
State: open - Opened by quinn-dougherty about 3 years ago
- 2 comments
#14 - let `pytest` and `pytype` know about `pycoq.so` somehow, probably by doing some kind of `dune exec -- pytest`
Issue -
State: open - Opened by quinn-dougherty about 3 years ago
- 1 comment
#13 - Give the caller `namedtuple`; factor out the need for dictionaries
Issue -
State: open - Opened by quinn-dougherty about 3 years ago
- 1 comment
#12 - goal: a jupyter build, probably docker image.
Issue -
State: open - Opened by quinn-dougherty about 3 years ago
- 1 comment
#11 - codesmell: breaks when `import pycoq` is omitted even tho `pycoq` is not invoked.
Issue -
State: open - Opened by quinn-dougherty about 3 years ago
- 1 comment
#10 - a `nix` build and testing infra
Pull Request -
State: open - Opened by quinn-dougherty about 3 years ago
- 12 comments
Labels: needs: rebase
#9 - [ci] Run CI with the constraints in the pycoq.opam file
Pull Request -
State: closed - Opened by ejgallego about 3 years ago
#8 - Documentation
Issue -
State: open - Opened by ejgallego about 3 years ago
#7 - Test suite
Issue -
State: open - Opened by ejgallego about 3 years ago
- 2 comments
#6 - Better development setup
Issue -
State: open - Opened by ejgallego about 3 years ago
- 6 comments
Labels: help wanted
#5 - Laziness and Sharing
Issue -
State: open - Opened by ejgallego about 3 years ago
#4 - Encoding of objects
Issue -
State: open - Opened by ejgallego about 3 years ago
#3 - Stop using the protocol interpreter interface
Issue -
State: open - Opened by ejgallego about 3 years ago
- 1 comment
#2 - Fix error handling
Issue -
State: closed - Opened by ejgallego about 3 years ago
- 1 comment
Labels: bug
#1 - Distribution / packaging
Issue -
State: open - Opened by ejgallego about 3 years ago
- 9 comments
Labels: help wanted