7:42 a.m.
Hi,
I was discussing development of InAcademia with Niels and again had to mention
that the debug cycle of SATOSA involves: pip installing, editing the virtual-
env code, restarting satosa, check behaviour, port changes to the git tree,
commit and push, pip install --upgrade, check.
Especially the manual port of the virtualenv changes/hacks back into the git
tree are error prone.
Am I doing it wrong, or is this really the only way?
Best regards,
Martin
9:35 a.m.
On Wed, 29 Aug 2018 at 10:42, Martin van Es <martin at surfnet.nl> wrote:
Hi,
I was discussing development of InAcademia with Niels and again had to mention
that the debug cycle of SATOSA involves: pip installing, editing the virtual-
env code, restarting satosa, check behaviour, port changes to the git tree,
commit and push, pip install --upgrade, check.
Especially the manual port of the virtualenv changes/hacks back into the git
tree are error prone.
Am I doing it wrong, or is this really the only way?
While on the project repository in a clean environment, do
pip install -e .
or
python ./setup.py develop
This will install the package in virtualenv by keeping a symlink to
the repository source.
Any change you make to the repository will be reflected to the
installed package.
You can verify this by running:
pip list -v
[...]
SATOSA 3.4.8 /projects/SATOSA/src
[...]
while other pacakges will be installed inside the virtualenv directory, ie
PyYAML 3.13
/projects/SATOSA/venv/lib/python3.7/site-packages pip
Hope this helps ;)
Cheers,
--
Ivan c00kiemon5ter Kanakarakis >:3
10:23 a.m.
Hi Ivan,
On Wednesday, August 29, 2018 11:35:12 AM CEST Ivan Kanakarakis wrote:
This will install the package in virtualenv by keeping
a symlink to
the repository source.
Thanks, that sure helps a lot!
That would require git cloning the repository local and preclude the use of
pip instal(ling) git+git://... construct I guess?
Grtz
Martin
11:03 a.m.
Hi,
On Wednesday, August 29, 2018 11:35:12 AM CEST Ivan Kanakarakis wrote:
While on the project repository in a clean
environment, do
pip install -e .
or
python ./setup.py develop
This will install the package in virtualenv by keeping a symlink to
the repository source.
I discoverd something extra (which may be common knowledge but was surprised
to see it working):
If you do a pip install -e (which means editable I found out by now) on a git+
url, pip will first clone the repo in ./src/<repo> and install it editable from
there. So, two steps in one!
Cheers!
Martin
2152
days inactive
2159
days old
3 comments
2 participants
participants (2)
-
ivan.kanak＠gmail.com -
martin＠surfnet.nl