× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi John,

Thanks for your reply.
I had a quick google but it wasn't completely clear how that option works -
whether it is a place to look where packages cannot be found locally (in
the venv) or whether it is designed to completely replace the packages in
the venv.

If the latter, then doesn't that completely negate the point of virtual
environments which is all about having packages with different dependancies?
In my case I'd mainly be using the venv to make sure that any package
changes didn't break anything before I pushed to the main install directory.

thanks and regards,
Craig

On Mon, 1 Apr 2019 at 16:48, John Yeung <gallium.arsenide@xxxxxxxxx> wrote:

I installed 3.6.6 via the Open Souce Package Management option from IBMi
ACS.
Forgive my ignorance but I don't know if this uses yum under the covers
or
if there is another way to use yum to do the install directly.

Ah, right, ACS. I don't use that. Yes, that ultimately uses yum.

But I assume this will just update the version in /QOpenSys/pkgs/bin

I could then re-create my venv and it would be at the 3.6.8-1 version of
python but the venv wouldn't not contain ibm-db and itoolkit.

Correct.

To install packages into my venv I'd normally activate the venv then pip
install the required packages.

By default, venv creates a new minimal install, but if you are OK with
the new environment having access to all the packages in
/QOpenSys/pkgs/lib/python3.6/site-packages, you could use the
'--system-site-packages' option on the venv call.

John Y.
--
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/opensource.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.