General bug report thread
The problem is, your action and accessory action must be define BEFORE your load your view, if the pyui references them.
In test1, when you load the pyui first, the actions are not defined, thus nothing happens, until you run the second time, at which point it is defined.
When you run test2 first, you are defining the accessory action, which gets used when you load the pyui.
The solution: in test1.py, define your actions, before you load the pyui. I posted a comment on your gist.
@JonB yes that's it! Thanks so much.
I guess I'll leave this conversation here - although it's not a bug, the default behavior should be to throw a
NameErrorexception instead of using a "cached" method from a totally different script.
If you don't want old scripts to carry over, you can set Clear Global Variables before run in the interpreter options menu. That way it is more like the python commandline. Default behaves more like an interactive interpreter, which personally I prefer, but you do have to be wary of leftover globals that make otherwise invalid code run without exceptions. So, your case 2 doesn't bother me.
I was surprised that case 1 failed silently. For other actions, like button, if the function cannot be found it doesn't generate a NameError, but does at least print a warning to the console. If delegate actions just fail silently, that may be a bug, or at least an oversight.
Warning: Couldn't bind action 'some_undefined_action' of 'button1'
Yeah it fails silently in both cases if Clear Global Variables is on.
1)Since upgrading to iOS 8.x any alert that takes input doesn't open the keyboard.
console.login_alert, when prompted for
keychain.master_password. Before iOS 8 the keyboard would automatically pop up.
- switching to a 3rd party keyboard and using it, then switching to another keyboard (maybe only 1st party?) crashes Pythonista.
The current Paramiko module (version 1.13.0) in Pythonista is not compatible with newer OpenSSH versions
(I already told Ole on twitter - but just want to put it in the forums also)
blmacbeth last edited by
@omz I have been playing around with the
ui.Imagemodule and have found what I may think is a bug. When I use
ui.Image.named('Test_Lenna')it works as expected, but when I do the following:
None. For now, I have a work-around, where I first open the image in
PILand then convert the Image to a bytes and then use
Let me know if there is something obvious I have overlooked or if this kind of picture importing is not possible. Thank you!!!
Sebastian last edited by
@blmacbeth If it's not a built in image, I believe you have to use the image's full path.
Perhaps not technically a bug, but a common source of incompatibilities:
sys.stdin, std.stdout, and sys.stderrshould have an
isatty()method which returns false. This might not technically be a "bug", since python docs don't seem to require all file methods to be implemented, except maybe
write, many other external libraries assume a file-like object.