[openstack-dev] [hyper-v] oslo.privsep vs Windows
Angus Lees
gus at inodes.org
Thu Nov 26 05:13:46 UTC 2015
On Thu, 26 Nov 2015 at 14:19 Robert Collins <robertc at robertcollins.net>
wrote:
> On 26 November 2015 at 15:54, Alessandro Pilotti
> <apilotti at cloudbasesolutions.com> wrote:
> > When done, open a PowerShell or command prompt and set your PATH and
> > PYTHONPATH e.g.:
> >
> > $ENV:PATH += ";C:\Python27;C:\Python27\Scripts"
> > $ENV:PYTHONPATH = "."
>
Wow, this syntax is completely foreign to me. You have no idea how much of
a newbie I feel, thanks ;)
> > For running tests you can use for example nose since tox / testr don’t
> > really work:
> >
> > pip install mock
> > pip install nose
> > nosetests .
>
> i haven't seen any bug reports on testrepository vis-a-vis windows;
> please do file them, otherwise I'll presume it works.
>
>From my brief day or two of experience, I think the tox executable itself
works fine - it's more the typical tox.ini:
- "python3.5.exe" doesn't typically exist - the regular python 3.5 windows
install seems to just install an unversioned python.exe and breaks the
usual tox basepython values. Creating a "python3.5" symlink doesn't seem
to be a thing ;)
- Just about every tox.ini we have is full of unixisms - see for example
nova/tox.ini's liberal use of bash scripts and find commands.
- Virtualenv installs things differently on windows. In particular the
venv has all the executables in $venv\Scripts\ rather than $venv/bin/.
I quickly gave up on using tox, and was running the virtualenv and "pip
install -r requirements.txt" steps by hand. The wheels (pun unintended)
well and truly fell off once I hit my first C library dependencies (for me,
yaml and netifaces pulled in by oslo.utils), and I was looking at having to
set up a full C toolchain from scratch too.
I didn't get far enough to try testr.
Alessandro: I think the main blocker I've hit so far (other than "how do I
cut+paste" ;) is installing the non-python library dependencies. Is there
something I can do to steal your pre-built wheels (and dlls?), or use a
pre-built distro like cygwin/msys2[1], or perhaps we should build a conda
repository for openstack/windows like I did once for openstack/linux[2], or
...?
[1] I didn't get an answer to my earlier question, I presume installing
cygwin _is_ going to invalidate my hyper-v-suitability tests, right? I
presume other "unix-like distros" like msys2 (mingw-based afaict) are
similarly bad?
[2] https://conda.anaconda.org/gus - It was a (mostly positive) experiment
in trying something other than pip. I haven't maintained the repo, but it
didn't take that long to package the transitive dependencies of nova.
- Gus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151126/d33aee45/attachment.html>
More information about the OpenStack-dev
mailing list