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.
Bug list for beta release 160037
-
I figured I would start a thread to document bugs in one place.
As of
160036160037 (starting to test in 2.0):bugs
extended keyboard still does not work in console on iPad 3/ios8.On Ipad 3, typing a two single quotes after an equal sign in the editor results in='''
instead of=''
. pressing a space before the = properly inserts a pair of quotes.- On Ipad 3, fullscreen convert_point, convert_rect, do not work correctly in fullscreen. see here. This was a bug in 1.5 as well, though I thought it was fixed in a recent beta build
- Similar problems with convert_point converting from a
sheet
to None.. the result has the sheet screen position added in twice. Thus 0,0 gets converted to (2x,2y) instead of (x,y) View.close
does not work for panel mode (not new)- Keyboard focus stays in editor, but shows console
Keyboard displays white keys after dismissing view.- View.touch_enabled = False has no effect:
>>> v=ui.View() >>> v.touch_enabled True >>> v.touch_enabled=False >>> v.touch_enabled True
- popover_location does not accept ui.Point [verified in 2.0]
SegmentedControl().subviews does not work properly- image_quad from arguments are incorrectly scaled. (workaround seems to be to multiply by 2, though i suspect this may depend on device)[not tested yet in 160037]
- ui editor does not save the currently editing view when switching focus to console (unlike script editor, which does). This leads to confusion when loading/presenting a view from the console( why the $!?& is the button action i added not getting called?). It does seem to save when switching to a different file tab. Seems like whenever console input gets focus, play is pushed, or an action run, any dirty files should be written to disk first.
- editor strips off trailing newlines from files.
- syntax highlighting for multiple same line imports (
import ui, os
) only highlights first module - SpriteNode without a texture=None does not work.
- IndentationErrors in the traceback viewer do not navigate to, or highlight the offending line, despite listing the line number in the traceback.
- TableView does not honor
flex
orframe
in constructor. - ~~App Extension does not work on 32 bit devices. ~~
- autocomplete in console: autocomplete after an equal sign (without a space) results in whole line getting replaced.
- If a quote is opened in the console input, copy/paste from the console does not work (copy is from the input, not output)
- scene.ShapeNode requires a
path
argument, otherwise attribute error occurs. - Vector2, etc type error when using future.division.
- Rect.inset does not work correctly when the Rect has negative widths (need to change sign of inputs)
suggestions
- (suggestion) Views presented as panel should have the "dock" button to return to the editor (rather than first tabbing to console). This goes for webbrowsers too.
- (suggestion) option to open contextmenu help in docked doc window rather than popover quickhelp. or, a button in quickhelp to open same page in full docs.
- (suggestion) ability to manage
editor
tabs. - (suggestion) Community forum link should open in an internal webbrowser, rather than launching safari. Or, this should be an option. With the new docking mode, it is now much easier to paste back and forth between editor and forums.
updated 11/13
-
extended keyboard still does not work in console on iPad 3. Can anyone confirm on 64 bit?
Is this on iOS 8 or 9?
-
sorry, ios 8
-
I see, thanks. The extended keyboard uses a completely different implementation on iOS 8, and I somehow forgot to fix that as well.
-
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 movingsk
functionality intoscene
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
wsgirefxhtml2pdf yaml
-
@ccc I see a Cloud Jump 2 revive coming soon ;)
-
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.
-
(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.
-
Looks like the < > navigation buttons have disappeared in the help browser in this release
-
@Phuket2 They're at the bottom now. This works better in "docked" mode.
-
@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 :)
-
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
-
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. -
@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 movingsk
functionality intoscene
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
wsgirefxhtml2pdf 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!)
-
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 (egphotos
,dialogs
,clipboard
) have already been loaded, however ere is no such issue if the module is run first (Link to come)
- closing Pythonista or locking the iPad while watching a video (mp4) using
-
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. -
@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. -
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
-
@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. -
When clicking empty trash, the trash empties but Pythonista also crashes.
iOS 9.0.2 - iPad 3