On Sun, Oct 2, 2016 at 1:51 PM, Steve D'Aprano <steve+pyt...@pearwood.info> wrote: > On Sun, 2 Oct 2016 09:31 am, Paul Rubin wrote: > >> Steve D'Aprano <steve+pyt...@pearwood.info> writes: >>> However I do have access to another machine (actually a VM) which can >>> compile Python 3.6. It's not practical for me to use it as a my main >>> development machine, but as a temporary measure, I thought I could >>> compile 3.6 on this VM, then copy the python binary to my usual >>> desktop machine. >> >> How about installing the same OS on the VM that you're running on the >> development machine? > > Because then I won't be able to build Python on the VM either, which > completely misses the point. I already have three machines that cannot > build Python. I don't need a fourth. I need one which *can* build Python.
Hmm, I've possibly missed something here, which may indicate a problem. Why can't your existing machines build? Is it because they have too-old versions of tools, and if so, which? ChrisA -- https://mail.python.org/mailman/listinfo/python-list