Replace virtualenv by python3 -m venv, fix #48

README.md

@@ -90,6 +90,14 @@ PenguinDome also uses a bunch of Python packages, all of which are
 deployed into a private virtualenv on the clients and server using
 `pip` at install time.
 
+`virtualenv` are created with native `python3 -m venv` tool now.
+Existing `virtualenv` created previously with `virtualenv` continue
+to work as-is.
+
+The use of `netifaces` package in client plugins requires `pip` 
+to compile it, hence the requirement of ubuntu `python-dev` or 
+equivalent on *the client* side.
+
 There's a nascent attempt in the `arch` subdirectory to build Pacman
 client packages for Arch Linux, but these don't entirely work right
 now, so for the time being, Arch clients use the same deployment

client/arch-packages.txt

@@ -22,7 +22,7 @@ git
 lvm2
 psmisc
 python
-python-virtualenv
+python
 systemd
 tar
 util-linux

client/client-setup.sh

@@ -36,7 +36,7 @@ elif [ "$ID_LIKE" = "archlinux" -o "$ID" = "arch" ]; then
 fi
 
 if [ ! -d $venv ]; then
-    virtualenv -p python3 $venv
+    python3 -m venv $venv
 fi
 
 for dir in $(find $venv -name site-packages); do

client/ubuntu-packages.txt

@@ -26,5 +26,6 @@ systemd
 tar
 ubuntu-release-upgrader-core
 update-notifier-common
-virtualenv
+python3-venv
+python3-dev
 wireless-tools

server/arch-packages.txt

@@ -17,6 +17,6 @@ gnupg
 https://aur.archlinux.org/libgfshare.git
 openssl
 python
-python-virtualenv
+python
 systemd
 tar

server/server-setup.sh

@@ -75,7 +75,7 @@ elif [ "$ID_LIKE" = "archlinux" ]; then
 fi
 
 if [ ! -d $venv ]; then
-    virtualenv -p python3 $venv
+    python3 -m venv $venv
 fi
 
 for dir in $(find $venv -name site-packages); do

server/ubuntu-packages.txt

@@ -18,4 +18,5 @@ openssl
 python3
 systemd
 tar
-virtualenv
+python3-venv
+python3-dev