|
I echo John's sentiments on QSH. QSH is just hard. Jessie Gorzinski
published a good article on getting started with SSH.
http://ibmsystemsmag.com/blogs/open-your-i/august-2017/
eight-reasons-to-embrace-ssh/
The one prior to that talks about setting up your default shell. I use
Cygwin as my terminal and bash as my shell. Add pudb to that and you get a
pretty good terminal debug environment for Python.
-----Original Message-----
From: OpenSource <opensource-bounces@xxxxxxxxxxxx> On Behalf Of John Yeung
Sent: Friday, August 24, 2018 8:33 AM
To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxx>
Subject: Re: [IBMiOSS] Python, adding modules to RPM installs
The e-mail below is from an external source. Please do not open
attachments or click links from an unknown or suspicious origin.
On Fri, Aug 24, 2018 at 5:18 AM Craig Richards <craig@xxxxxxxxxxxxxxxx>
wrote:
What I'd like to do now is install xlsxwriter into the RPM python3
installation.
I'm not really sure how to do that - do I need to use yum manually to
do that?
No, once Python is installed, the idea is to use pip for everything
related to that installation of Python.
I don't have any of the PASE Pythons to test for myself, but there should
be a pip that is specific to your Python 3.6.6. If you can't find that,
then you can invoke pip not as a standalone command but as a Python script
that is run by the desired Python interpreter. For example, assuming your
path and/or current directory is such that `python` refers to the Python
you want, do
python -m pip install xlsxwriter
Also, on a slightly different note, although the RPM version of python
3.6.6 works fine for my json pretty print requirement, I notice that
if I run QSH interactively and then /QOpenSys/pkgs/bin/python3 to go
into python it behaves differently to the other installs of python2
and python3 -if I type something and press enter, it takes just the
first letter of what I have typed, if I press enter a second time, the
rest of what I typed appears on the next line down and then runs?
As I said, I can't test this myself, but the preferred way to work with
any of the PASE Pythons is to set up your i to accept SSH sessions, and
then log in that way. You'll then have a much more Unix-like environment.
The 5250 is just not a TTY-style terminal interface, and you really need
that to use PASE effectively (and sanely!).
Sadly, I don't have any tips on how to tell if you are set up for SSH
(other than just trying to connect using PuTTY or similar software), and
more importantly how to set it up if it's not already. But plenty of others
here can chime in because they all use SSH for their PASE work.
John Y.
--
This is the IBMi Open Source Roundtable (OpenSource) mailing list To post
a message email: OpenSource@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: https://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at https://archive.midrange.com/opensource.
NOTICE: This electronic mail message and any files transmitted with it are
intended
exclusively for the individual or entity to which it is addressed. The
message,
together with any attachment, may contain confidential and/or privileged
information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.
--
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/opensource.
As an Amazon Associate we earn from qualifying purchases.
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.