Creating standalone (exe) viewer from code run on Ipython - qt

I have this very basic piece of Python which I use to visualize some data and perform a few interactions with. I launch it from Spyder and it is basically just a function.
In broad terms:
open a file and create a DataFrame from it
plot some data and add a few sliders to interact with the data
I was wondering whether I could make this small code available to other people who do not have Python installed and probably not even the latest Qt5 libs I am using.
Os would be Linux but could also be Windows if it came easier.
Can you tell me how time consuming would it be to create a standalone file which could be double clicked and just show the plot with the interactive bits?

Just followed the (2 line!) instructions on PyInstaller:
$ echo "print 'hello world...'" > helloworld.py
$ pip install pyinstaller
$ pyinstaller helloworld.py
$ dist/helloworld/helloworld
hello world...
Looks pretty automated. It analyses your dependencies as far I can tell and brings everything you need together and then makes a launch script. It works on loads of platforms and even mentions Qt on the front page. I reckon its worth a go!

Related

Differences between various consoles in Python

I am trying to make run a script for webscraping. However, I feel the problem could be that I keep running the written script in the wrong console.
So far I could not really understand the differences between the consoles cmd and Anaconda Prompt. Anaconda Navigator looks rather like an administrative tool, but it seems still to make a difference for my code whether I use a terminal from there or not. Could anyone elaborate on that?
Much appreciated
cmd: command-prompt, that used to run our python script, especially for scripts with .py extension. Besides that, we can used to install python library
Anaconda Prompt: almost similar to cmd. But usually we used to open jupyter notebook or other console on Anaconda Navigator.
Anaconda Navigator: a GUI desktop application that is included in the Anaconda installation package. Through Anaconda Navigator, programmers can easily run and manage Conda packages, environments and channels without the need to use command prompt commands. Anaconda Navigator can search for packages in the anaconda cloud repository.
So, the difference depends on what we want to do. You can't judge the problem arises because of the wrong console. It depends on the error message that appears.
Suggestion: read the error message, and analyze or find a way to solve the problem

How to make R executable file

Is it possible to create an executable file where I can just upload the excels and an output is generated based on the coding and without sharing it as well.
On Linux or OSX you can make an R script double clickable with the shebang trick:
Add #!/usr/bin/Rscript as the first line
Make the script executable with chmod +x
On OSX, there is also the option to convert an R script into an application bundle with Platypus. On Windows, I do not know whether this is easily achievable at all, especially as executables usually are not placed in the search path on Windows.
is using R-Shiny apps can cover that? Its an R based program and you can customize the output / logic there.

Run R command without entering R and without a script

I want to run an R command from command line (actually, from within a Makefile). The command is roxygen2::roxygenise(), if it is relevant. I don't want to create a new file and run that as a script - that will just clutter my directory.
In python, this is simple - you write python -c "import antigravity".
I use the Makefile to build, install and test a (Rcpp) package I'm working on.
This is generally done with so 'shebang scripts'.
Historically, littler was there first, about a decade or so ago. It is still widely used, and contains a number of helper scripts as for example roxy.r which does just what you desire: run roxygen2::roxygenize(). I use this all the time.
Next, Rscript started to ship with R. It is similar to littler but automatically available whereever R is which is a plus. On the minus side, it starts slower, and fails to load the methods package which is a source of a number of bug reports and SO questions.
Much more recently, R itself added the ability to run expressions following the -e ... switch.
So you have plenty of choices. You can also study plenty of src/Makevars files many of which use Rscript.

Unix command to print directory structure in the form of a tree?

I am a newbie to UNIX, i want to print tree structure of files in a directory. below image is example in DOS, what will be the command of Unix to achieve same objective
I think you are looking for the "tree" command. If you are having issues running it you might have to find out how to install it on your specific distribution. For ubuntu installs you can find instructions here:
https://askubuntu.com/questions/507588/not-able-to-install-tree-comand-in-ubuntu
Not sure what you mean by "on Unix". What OS are you running, specifically? Tree should be compatible on Unix systems. You may just have to compile it for your particular OS.
This command prints output like the following (on cygwin):

Advice on upgrading Emacs (22 -> 24), and also about GUI vs console/terminal

I'm using a Macbook Pro (Snow Leopard, 10.6.8) and have been a regular emacs user for the past few months. I'm trying to install a modified version of Emacs 24.2 provided here to utilize Emacs Speaks Statistics (ESS) from the downloads page. I currently have 22.1.1:
M-x emacs-version
GNU Emacs 22.1.1 (mac-apple-darwin) of 2011-06-07 on b1030.apple.com
I installed the emacs linked earlier, put it in Applications, and set this in .bashrc:
alias emacs="/Applications/Emacs.app/Contents/MacOS/Emacs -nw"
So it seems like it's working correctly as I wrote and successfully ran a short R program.
M-x emacs-version
GNU Emacs 24.2.1 (x86_64-apple-darwin, NS apple-appkit-1038.36) of 2012-08-27 on bob.porkrind.org
Is this the usual way to upgrade to a "newer version" of Emacs? Sorry if this question seems trivial, but I've never done this before (I typically used emacs on a different computer) and the Installation step on the previous website consists of just one sentence. The all-in-one installation method also isn't explained in the official documentation.
A brief side note while I was searching on the web: I believe calling 'emacs file_name' should open a GUI version, while 'emacs -nw file_name' is the console, so I remain using the terminal. But on my Mac, using emacs has the same effect as using emacs -nw. In other words, I can't get a GUI or separate window to show up. Can anyone confirm that this Super User question has the 'correct' answer? (I don't really have a problem with this, as I hate having another pop-up window, but it would be nice to know for completeness.)
The Emacs that comes with Mac OS X /usr/bin/emacs does not have a graphical interface, just the terminal one, so calling emacs is the same as emacs -nw.
Your upgraded Emacs by default starts with the graphical interface, so you need to specify -nw to force it to use the terminal.
There is no "usual" way to upgrade OS X's default Emacs (i.e. Apple does not provide an upgraded Emacs); what you've done is fine. Or you could install a binary from http://emacsformacosx.com/ or use a package manager like homebrew.

Resources