Bug list for beta release 160037

omz

I see, thanks. The extended keyboard uses a completely different implementation on iOS 8, and I somehow forgot to fix that as well.

ccc

First off, a massive congratulations to you @omz for the scene rewrite and especially the new docs for that module. The intro will rapidly get any wannabe game developer hooked!! It will break a few things but your moving sk functionality into scene is brilliant and performance seems impressive.

Bugs

Almost all third party modules are not current with PyPI.
Many third party modules are present but not listed in the documentation: Crypto ctypes dateutil ecdsa flask html2text html5lib httplib2 itsdangerous jedi jinja2 mechanize midiutil mpmath oauth2 parsedatetime pycparser pyflakes pygments pyparsing PyPDF2 pytz reportlab simpy six sqlalchemy sympy thrift werkzeug ~~wsgiref~~ xhtml2pdf yaml

techteej

@ccc I see a Cloud Jump 2 revive coming soon ;)

JonB

The application extension does not seem to be working on ios 8/ 32 bit. Clicking "run pythonista script" from the share sheet results in... nothing.

Possibly my .extension folder is screwed up, one of the previous betas moved Documenta into .Extension (so the folder is pretty large), though i think this still worked with the last beta.

userista

(Suggestion) on the iPhone it's hard to tell when a line wraps - perhaps a line wrap glyph and/or line numbers would be a nice improvement.

Phuket2

Looks like the < > navigation buttons have disappeared in the help browser in this release

omz

@Phuket2 They're at the bottom now. This works better in "docked" mode.

Phuket2

@omz , opps, sorry. So they are :) maybe you need to say people over 50 can not be beta testers :) the eye sight is so bad. The Whiskys also don't help :)

Webmaster4o

This is a bug.

If my keyboard is open when I present a view, it looks like this when I two-finger swipe to dismiss the view

Sebastian

Every time I try to create a new script or file, I get an error saying "The new file/project couldn't be created. Please make sure that you entered a valid file name." Am I the only one who gets this error? I'm using an iPhone 5S with iOS 8.1.

Edit:
Everything works fine now, I reinstalled Pythonista and now the error message is gone.

Wizardofozzie

@ccc said:

First off, a massive congratulations to you @omz for the scene rewrite and especially the new docs for that module. The intro will rapidly get any wannabe game developer hooked!! It will break a few things but your moving sk functionality into scene is brilliant and performance seems impressive.

Bugs

Almost all third party modules are not current with PyPI.

Many third party modules are present but not listed in the documentation: Crypto ctypes dateutil ecdsa flask html2text html5lib httplib2 itsdangerous jedi jinja2 mechanize midiutil mpmath oauth2 parsedatetime pycparser pyflakes pygments pyparsing PyPDF2 pytz reportlab simpy six sqlalchemy sympy thrift werkzeug ~~wsgiref~~ xhtml2pdf yaml

Out of interest, how do you find these modules?
For example:

import oauth2, os
odir = os.path.dirname(oauth2.__file__)
# odir = /var/mobile/Containers/Bundle/Application/C370CA19-1410-4DA3-975F-CBA563809E66/Pythonista.app/Frameworks/PythonistaKit.framework/pylib/site-packages/oauth2
# so oauth2 dir is in site-packages/oauth2

If I use Stash to look for the ~/site-packages/oauth2 directory, it's not there. What gives?

Edit: In Stash:
cd ~/Documents/site-packages
ls -a1
cd oauth2 <- ERROR

(Excuse what may be a very basic question!)

Wizardofozzie

Quick bug:

closing Pythonista or locking the iPad while watching a video (mp4) using Quick View does not stop the video (and audio) from playing
Importing ripemd160 module raises a NoneType not Callable when Pythonista modules (eg photos, dialogs, clipboard) have already been loaded, however ere is no such issue if the module is run first (Link to come)

JonB

the built in modules come preloaded in the app library, not in docs. You can view these folders from the Standard Library in the file browser, or grab the name as you already did, then navigate there in stash. There is no direct way to get there from Documents, because of the way apple sandboxing works. Actually, we probsbly should open a pull request in stash to provide an environment variable to the library folder.

as for ripemd160.... are you doing an from xxx import *? If so, you can often expect issues with namespace clashes. Also, if you aborted an import, that usually results in failure to import later, unless you restart pythonista. In the rare event that this is real, do
import pdb; pdb.pm() to figure out what is trying to be called.

Wizardofozzie

@JonB said:

the built in modules come preloaded in the app library, not in docs. You can view these folders from the Standard Library in the file browser, or grab the name as you already did, then navigate there in stash. There is no direct way to get there from Documents, because of the way apple sandboxing works. Actually, we probsbly should open a pull request in stash to provide an environment variable to the library folder.

as for ripemd160.... are you doing an from xxx import *?

Yep :)

If so, you can often expect issues with namespace clashes. Also, if you aborted an import,

Can you clarify this? Would

try:
    from urllib import add_opener # python3
except ImportError:
    from urllib2 import add_opener # python2

trigger the error?

that usually results in failure to import later, unless you restart pythonista. In the rare event that this is real, do
import pdb; pdb.pm() to figure out what is trying to be called.

@JonB said:

the built in modules come preloaded in the app library, not in docs. You can view these folders from the Standard Library in the file browser, or grab the name as you already did, then navigate there in stash.

Forgive me if this is a basic question, but how do I go about this? Ie how do I use stash to navigate to the Std Library directory?

as for ripemd160.... are you doing an from xxx import *? If so, you can often expect issues with namespace clashes. Also, if you aborted an import, that usually results in failure to import later, unless you restart pythonista. In the rare event that this is real, do
import pdb; pdb.pm() to figure out what is trying to be called.

ccc

grab the name [ ... ] and navigate there in stash.

Means type the following into stash:

cd /var/mobile/Containers/Bundle/Application/C370CA19-1410-4DA3-975F-CBA563809E66/Pythonista.app/Frameworks/PythonistaKit.framework/pylib/site-packages/
ls

JonB

@simcity4242

Also, if you aborted an import,
I mean if you press the X button to abort a script in the middle of a long import, the subsequent import will generally fail in confusing ways.

techteej

When clicking empty trash, the trash empties but Pythonista also crashes.

iOS 9.0.2 - iPad 3

JonB

I could not reproduce this on ipad 3/ ios8

georg.viehoever

@techteej I Did see no problems on my ipad2 ios9.1
Georg

Phuket2

@georg.viehoever , where?if you look on the thread, you don't have an entry. So somehow, when you submitted it didn't work!