Welcome!
This is the community forum for my apps Pythonista and Editorial.
For individual support questions, you can also send an email. If you have a very short question or just want to say hello — I'm @olemoritz on Twitter.
I tried to download setuptools and copy its pkg_resources sub-folder into site-packages. Then import pygal just worked. Maybe we can make this a standard process to install pkg_resources the first time stash pip is called.
By the way, these are the commands I used to install pkg_resources.
pip download setuptools
tar -zxvf setuptools-25.1.0.tar.gz
cp setuptools-25.1.0/pkg_resources site-packages/
If there are any import errors afterwards, try restart Pythonista.
@dgelessus Thanks I'll make sure the setup files are deleted at the end.
I have seen this type of error before. It is caused by the reload() statements in your main.py file.
Reload will define a new class object for the same class. To Python interpreter, this new class object is considered as a different class from the old class object. If you have a subclass instance of the old class object, it will not be compatible with the new class object. In your case, it is most likely that the PhysicsCamera is still a subclass of the old LookObject class object.
You could try replace LookObject.__init__(...) with super(PhysicsCamera, self).__init__(*args, **kwargs). The super() function should get the correct parent class. But it also means any changes to the parent class via reload are not honored.
This was caused by a bug in pip when it registers installed package, which is backed by RawConfigParser. The RawConfigParser has its own string interpolation rule which relies on the percentage sign.
The bug has now been fixed and you can get it by selfupdate -f.
It cannot be done. greenlet does not work in Pythonista.
greenlet is a pure C extension. It does not have any Python modules to be installed. That is what caused the error. C extension installation generally requires compiling C code which is impossible in Pythonista.
Thanks a lot @dgelessus ! One cannot ask for a better answer!
@korakot @plessner There was a bug in stash pip command that prevented it from parsing package names with uppercase letters. The bug is now fixed and you can get the updated version via selfupdate.
The install script works for both Python 2 and 3.
The program itself runs in Python 2. However **you can still use Python 3 **as the default interpreter thanks to the shebang line for cross-interpreter calls.
I did start porting the whole program to Python 3 a while back. However it is not completed due to some difficulties in porting some of the command scripts. Plus I am not not very happy of the overall porting. It was too aggressive and tried to use as much as Python 3 features as possible. I now think it is better to be more conservative. When omz adds the possibility to use both 2 and 3 in the same app. I basically discard the last porting. I'll probably try it again at some point. But for now, the program works fine in the new Pythonista.
[EDIT]: 2016-05-26
Inspired by shellista and its variants, StaSh is a serious attempt to implement a Bash-like shell for Pythonista.
Since its initial release, valuable contributions and advices have been received constantly from the Pythonista community. The two most popular utilities are pip (authored by @briarfox) and git (authored by @jsbain). Remarkable contributions are also made by
@dgelessus, @pudquick, @oefe, @cclauss, @georg.viehoever, @BBOOXX and @bennr01.
StaSh stands for Pythonista Shell. While Sta may not be the best abbreviation for Pythonista, it forms a concise and meaningful word with the following Sh part. So the name StaSh was chose to indicate it is a confined environment and great treasures may be found within.
StaSh can be easily installed via one line of python command (courtesy of @whitone).
import requests as r; exec(r.get('http://bit.ly/get-stash').text)
Simply copy the above line, paste into Pythonista interactive prompt and execute. It installs StaSh as a Python module under the site-packages folder (~/Documents/site-packages/stash) and copies a launching script, ~/Documents/launch_stash.py for easy access.
If you have previous versions of StaSh installed (e.g. v0.4.x), You may need to restart Pythonista BEFORE the installation.
If you have a GitHub tool available in Pythonista, such as gitview or gitrepo, you can choose to directly clone or download the repository.
StaSh requires Pythonista v2.0 as the new ObjC feature is heavily used. For older Pythonista 1.5 compatible version, please refer to the v0.4 branch.
Once StaSh is installed, it can be easily updated by running the selfupdate command from within the shell.
selfupdate defaults to the master branch. To update from a different branch, e.g. dev, use selfupdate dev.selfupdate compares local and remote versions and only performs update if newer version is found. You can however force the update without version checking via selfupdate -f.selfupdate -n.selfupdate manages StaSh installation folder and may delete files in the process. It is therefore recommended to not place your own scripts under $STASH_ROOT/bin. Instead, save your own scripts in~/Documents/bin or customise the locations with the BIN_PATH environment variable.selfupdate cannot be used for version 0.4.x and under. A fresh installation is needed.
StaSh has a pile of features that are expected from a real shell. These
features are what really set the difference from shellista.
Panel UI program that is completely event driven
Comprehensive command line parsing and handling using pyparsing
echo $HOME, NAME=valuealias l1='ls -1'"*" means literal *, "$HOME" expands while '$HOME' does not.ls My\ Script.pyls ~/*.pytouch `ls *.py` find . -name "*.txt" | grep interestingls *.py > py_files.txt. Input redirect can be achieved by using pipes.
ls > &3ls -1, !l. Bang commands like !! and !-1 also works.Smart auto-completion just as expected
Tab, is provided to enable command line auto-completion.git sta and press Tab. It will auto-completes to git status . You can easily add your own sub-commands completion via JSON files.Thread management allows multiple commands running in parallel
&) at the end of a normal command, e.g. httpserver &. It can be terminated by the kill command using its job ID.jobs to list current running background jobs.kill to kill a running job.fg to bring background jobs to foregroundCZ button (Ctrl-Z) to send a foreground job to backgroundCommand line history management. Three UI buttons are provided to navigate through the history.
On-screen virtual keys - an extra row of keys on top of the on-screen keyboard to provide control functions and easier access to symbols
~/.-*|>.
VK_SYMBOLS option in stash config file (default is .stash_config).Swipe on the virtual key row to position cursor (similar to what Pythonista builtin editor offers)
External keyboard support
You can run (almost) any regular python scripts from within StaSh
python your_script.py, you can just call it from within StaSh by just typing your_script_stash('pwd').You can give it a resource file, similar to .bashrc, to customize its behaviour. Like the Bash resource file, aliases, environment variables can be set here. The default resource file is .stashrc under StaSh installation root (i.e. ~/Documents/site-packages/stash).
PROMPT environment variable.
\w - current working directory with HOME folder abbreviated as ~\W - last path component of current working directoryPROMPT='[\W]$ 'Easy self update to keep update with the development by running a single selfupdate command from within the shell.
The UI can be configured via configuration file to customize its font size and color. The default config file is .stash_config or stash.cfg under StaSh installation root.
The usage of StaSh is in principle similar to Bash. A few things to note are:
The search paths for executable scripts is set via an environment variable called BIN_PATH as PATH is used by the system. The default BIN_PATH is ~/Documents/bin:$STASH_ROOT/bin.
The executable files are either Python scripts or StaSh scripts. The type of script is determined by looking at the file extensions ".py" and ".sh". A file without extension is considered as a shell script.
selfupdate and find the file selfupdate.py to execute.Commands can only be written in a single line. No line continuation is possible. However, multiple commands can be written in a single line by separating them with semicolons, e.g. ls -1 > file_list; cat file_list.
There are many Python scripts provided along with StaSh. These scripts range from performing regular shell tasks to advanced utilities like ssh and git. Note the scripts are by no means complete when compared to a real Linux shell. The collection will be gradually expanded should the need arise. It is also expected and appreciated that the community would come up with more scripts.
alias.py - Define or print aliasescat.py - Print contents of filecd.py - Change current directoryclear.py - Clear consolecp.py - Copy filecrypt.py - File encryption using AES in CBC modecurl.py - Transfer from an URLcut.py - Cut out selection portions of each line of a filedu.py - Summarize disk usage of the set of FILEs, recursively for directoriesecho.py - Output text to consoleedit.py - Open any text type files in Pythonista editorfind.py - Powerful file searching toolfg.py - Bring a background job to foregroundgit.py - Git client ported from shellistagrep.py - search contents of file(s)httpserver.py - A simple HTTP server with upload function (ripped from https://gist.github.com/UniIsland/3346170)jobs.py - List all jobs that are currently runningkill.py - Terminate a running jobls.py - List filesmail.py - Send emails with optional file attachmentman.py - Show help message (docstring) of a given commandmc.py - Easily work with multiple filesystems (e.g. local and FTP) synchronously.md5sum.py - Print or check MD5 checksumsmkdir.py - Create directorymv.py - Move fileopenin.py - Show the open in dialog to open a file in external apps.pbcopy.py - Copy to iOS clipboardpbpaste.py - Paste from iOS clipboardpip.py - Search, download, install, update and uninstall pure Python packages from PyPI.printenv.py - List environment variablesprinthex.py - Print hexadecimal dump of the given filepwd.py - Print current directorypython.py - Run python scripts or modulesquicklook.py - iOS quick look for files of known typesrm.py - delete (remove) filescp.py - Copy files from/to remote servers.selfupdate.py - Update StaSh from its GitHub reposha1sum.py - Print of check SHA1 checksumssha256sum.py - Print of check SHA256 checksumssort.py - Sort a list, also see uniquesource.py - Evaluate a script in the current environmentssh.py - SSH client to either execute a command or spawn an interactive session on remote servers. pyte is used for terminal emulation and gives the command the feel of a full-fledged SSH client.ssh-keygen.py - Generate RSA/DSA SSH Keys.stashconf.py - Change StaSh configuration on the flytar.py - Manipulate archive filestouch.py - Update timestamp of the given file or create it if not existuniq.py - Remove duplicates from list, also see sortunzip.py - Unzip file, also see zipversion.py - Show StaSh installation and version informationwc.py - Line, word, character countingwget.py - get data from the netwhich.py - Find the exact path to a command scriptwol.py- Wake on LAN using MAC address for launching a sleeping systemxargs.py - Command constructing and executing utilityzip.py - Zip file, also see unzipls.py, cp.py, mv.py, are taken from ShellistaExt with some modifications.AttributeError as if the class definition cannot be found.
@JonB said:
I would suggest simply putting #!python2 at the start of launch_stash.py, to force stash to use the python2 interpreter. you can still keep your default interpreter as py3, but run stash using py2.
This is probably a much better solution than porting the whole thing to py3?
A follow-up question is : how can stash run a python script with the other Python interpreter (3.5) while stash itself is running in 2.7? Or vice versa, what if stash is running with Python 3.5 and the script has a python2 shebang?
Currently stash just uses the exec function to run a python script which does not seem to honour the shebang. I'd guess this is possible with objc_util, but I am not sure where to start. Any tips are appreciated.
Maybe @omz can provide a formal API to allow this kind of cross interpreter call?
This was caused by a bug in pip when it registers installed package, which is backed by RawConfigParser. The RawConfigParser has its own string interpolation rule which relies on the percentage sign.
The bug has now been fixed and you can get it by selfupdate -f.
It cannot be done. greenlet does not work in Pythonista.
greenlet is a pure C extension. It does not have any Python modules to be installed. That is what caused the error. C extension installation generally requires compiling C code which is impossible in Pythonista.
I tried to download setuptools and copy its pkg_resources sub-folder into site-packages. Then import pygal just worked. Maybe we can make this a standard process to install pkg_resources the first time stash pip is called.
By the way, these are the commands I used to install pkg_resources.
pip download setuptools
tar -zxvf setuptools-25.1.0.tar.gz
cp setuptools-25.1.0/pkg_resources site-packages/
If there are any import errors afterwards, try restart Pythonista.
This is the use case that StaSh was initially created for. You can invoke your script from within StaSh similar to what you would do on a PC. You can redirect the output to a file as the follows:
your_script.py > output.txt
More details here https://github.com/ywangd/stash
If you have previous experience with Linux shell, things should be quite familiar.
OmniClass is a stub class defined in StaSh pip. So maybe somehow it was getting in the way. Try restart Pythonista, i.e. swipe up to remove from task list.
Thanks a lot @dgelessus ! One cannot ask for a better answer!
@omz @dgelessus
The following simple code using pythonapi works well in Python 2 but errors out in Python 3.
import ctypes
p3 = ctypes.pythonapi
state = p3.PyGILState_Ensure()
p3.PyRun_SimpleString('print(42)')
p3.PyGILState_Release(state)
The error is name 'p' is not defined which is very weird as it suggests that the API does not even parse the given string correctly. It somehow tries to get a variable named p which is in fact the first character of print.
Thanks @dgelessus
The use of PyDLL worked for some initial tests!
@omz
ctypes.pythonapi always points to the C API of Python 3 regardless of the default interpreter setting. Is there anyway to access the Python 2 version of pythonapi object? It would be even more fantastic if both of them can be accessed without switch interpreter setting.
I also tried to manually load the library with
ctypes.CDLL(os.path.join(os.path.dirname(sys.executable), 'Frameworks/PythonistaKit.framework/PythonistaKit'))
Although it seems to load the Python 2 API and Py_GetVersion does show the version to be 2.7. But it is somehow not really usable. Many API calls working with the Python 3 API would not work or even simply crash the app.
Any help is appreciated.
@korakot @plessner There was a bug in stash pip command that prevented it from parsing package names with uppercase letters. The bug is now fixed and you can get the updated version via selfupdate.