hi Pycket, what version of Python should I use?

pypy says it wants 2.7.13 or 3.5.3 (https://pypy.org/), but the Pycket readme doesn’t specify

also, fyi, this repo was very helpful the last time I tried to use Pycket https://github.com/btlachance/pycket-docker

@ben I use 2.7.15 which is what I get as python

also I hope things have gotten easier

last time I think my problem was with pypy

anyway, the docker was a quick, zero-effort solution that I was happy to find

wow pypy takes a long time to build

@ben Yeah pypy takes around ~2 hours to build, though you should be able to use a prebuilt binary with the 2.7.13/15 checkout (which I’m pretty sure is what our test setup does)

how do I get a prebuilt binary?

I tried following the Pycket instructions (https://github.com/pycket/pycket)

and couldn’t do the 3rd step

because #/usr/bin/env pypy led to “pypy not found” or something

I didn’t see a pypy executable in my pypy repo, so I started building

Yeah you can either build the binary which should be around /pypy/goal/pypy-c, or you can download a prebuild binary and use it alongside the 2.7.13 checkout

Here’s the link that our test setup uses to get the binary https://bitbucket.org/pypy/pypy/downloads/pypy2-v6.0.0-linux64.tar.bz2

should that link be in the pycket readme? or, is it in the pypy readme somehwere

Well, you can use any pypy you want to translate, either you can get the latest pypy checkout and build it yourself, or use a prebuilt binary like in the link above, you can even use the CPython to do the translation (it’ll take very long though)

I agree that we should probably make the README a little clearer on how to get the PYPY running, we seem to be assuming that

do you actually need pypy to translate? I think you can do it with python

@samth sure, in fact if you don’t have PYPY binary in the environment, then make pycket-c is automatically going to use cpython

@ben I think you should just use the various make targets

@cadr I think we should stop putting the manual instructions first

ok

hmm, I’ve set PLTEXECFILE, but when I try to run pycket-c I get “sh: racket: command not found”

this is because I don’t have a racket executable in my path — but I’d rather tell Pycket exactly what racket to use instead of it looking in my path

I think you should just arrange for racket to be in your path

does the pycket package depend on Racket 7? I tried make setup with a Racket based on 6.12 and got: pycket/pycket-lang/zo-expand.rkt:5:18: only-in: identifier `compiled-position->primitive'