×
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.
On our 7.3 box we had python 2.7.13 and 3.4.6 installed.
I added the xlsxwriter module to them using pip2 and pip3 commands.
I later installed python 3.6.6 via RPM which has installed into
/QOpenSys/pkgs/bin/phthon3, which allowed me to use a version of the json
module to pretty print json without forcing an alphabetic key resequence of
the document...
That all works swimmingly.
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?
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?
e.g I type:
help<enter>
and what appears is
h
I press enter again and then I get:
elp
Type help() for interactive help, or help(object) for help about object.
So the first enter seems to just load in the first letter of what I have
typed and the second enter pulls in the rest and processes the command.
Is this a known bug or is this just me being ignorant?
Sorry I a bit new to python and opensource.
Thanks kindly,
Craig
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.