[Satosa-dev] Microservices installation

Ioannis Kakavas ikakavas at protonmail.com
Wed Nov 8 14:42:39 CET 2017

> -------- Original Message --------
> Subject: Re: [Satosa-dev] Microservices installation
> Local Time: November 8, 2017 3:38 PM
> UTC Time: November 8, 2017 1:38 PM
> From: skoranda at gmail.com
> To: Rainer Hoerbe <rainer at hoerbe.at>
> Ioannis Kakavas <ikakavas at protonmail.com>, satosa-dev at lists.sunet.se <satosa-dev at lists.sunet.se>
>> I would prefer not to have dependencies hard coded (like pysaml1==4.x.x). That
>> requires forking the main project because of a changed dependency.
> I agree. The dependency on a particular version of pysaml2 has been
> bothersome since there has been so much (quite helpful) evolution of
> pysaml2 lately and production deployments need the latest release. All
> of my production deployments have extra
> pip --upgrade pysaml2
> instructions.
> I would like to use minimum version dependencies as much as possible and
> let pip grab the latest version when available.


> Scott K
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sunet.se/pipermail/satosa-dev/attachments/20171108/60a57791/attachment.html>

More information about the Satosa-dev mailing list