(This message has been automatically imported from the retired mailing list)
Are there any best practices or recommended approaches for adding additiona=
l packages into the zato virtual environment? We rely on a handful of addi=
tional packages to help out with calling some third party webservices. My =
approach for handling these right now is to maintain a requirements.txt fil=
e and install into the zato venv with the -no-deps switch (as I’ve found th=
at omitting this pulls in “official” versions of some libraries, most notab=
ly requests, which seems to break zato quite badly). This is…a bit unwie=
ldly, and it’s quickly turning into an exercise in “hunt down the dependenc=
y”, plus there is the omnipresent risk of a developer basically wrecking ou=
r environment by forgetting the -no-deps switch.
Additionally, I’m noticing that django appears to be available in the zato =
environment now; this is triggering some odd behavior in a package we use. =
Specifically, if it is able to import django (which it now is), it checks =
a django setting to disable itself, then attempts to use django’s persisten=
ce framework to store some data. As this is unconfigured (rightly so, in f=
act) in the zato environment, this is basically causing every call through =
this library to fail. Is there any way of setting django settings via zato=
so we can force-disable this behavior from the package?
4901 Forbes Blvd. | Lanham, MD 20706
P. 240.487.2999 | F. 301.731.5199 | E. email@example.com
Click on http://www.ggoutfitters.com for all of your promotional needs!!!
Follow us on [https://secure.sureshiponline.com/catalogs/ggo/GGO-Facebook.p=
ng] https://www.facebook.com/pages/GG-Outfitters/100759079981924 [https:=
nsider the environment before printing this e-mail.
This message contains confidential information and is intended only for the=
individual(s) addressed in the message. If you are not the named addressee=
, you should not disseminate, distribute, or copy this e-mail. If you are n=
ot the intended recipient, you are notified that disclosing, distributing, =
or copying this e-mail is strictly prohibited.