Bug list for beta release 160037

Wizardofozzie

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!

ccc

@georg-viehoever was referring to @techteej 's bug report on emptying the trash.

JonB

bug: View.touch_enabled cannot be changed.

JonB

inconsistency: View.present popover_location does not accept a ui.Point.

JonB

convert_point and convert_rect do not work properly with a None argument if the view is a sheet. not as bad as fullscreen, but there is an extra offset equal to the top left corner, as if that were being accounted for twice.

zencuke

The files window ion an iPhone 6+ is not as wide as the screen. A stripe of the file screen shows on the right. I hope this is a bug. I'd rather have the full width of the screen to show longer file names.
iPhone screenshot

Webmaster4o

@zencuke this is not a bug. It's more obvious on iPad, but it's a conscious UI choice.

zencuke

Missing documentation. The current process for adding an icon to execute an extensions script directly doesn't seem to be documented. I think the current documentation refers to an earlier process. I looked in "Pythonista Modules/appex - Using the Pythonista Sharing Extension" doc and .extensions/_Readme.md and didn't see it in either place.

zencuke

@Webmaster4o: Intentional or not I'm having difficulty understanding the value of this. The tiny view of the file on the right adds no useful functionality to the UI. It just takes away functionality from the file list window. The iPhone screen is small as it is. Squeezing it even more is a pain, especially for no benefit. It may mean something on the iPad but it looks like a bug on the iPhone. It is bad enough on the iPhone 6 plus. It must be even worse on smaller iPhones like the regular iPhone 6. The edit window gets a whole screen. The console and doc screens get to be full width but for some reason the file list has to be narrower? With no useful functionality in exchange? Makes no sense.

JonB

Not sure if this is a bug or just not well documented. in the latest beta, wait_modal seems to stop any ui.in_background from getting executed until after the view is closed.

Wizardofozzie

@ccc said:

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

😋
I had no idea about this! Thx!

Olaf

I love the the possibilities offered by obcj_util. While exploring these, I ran into an error.

I managed to end up with an ObjCInstanceMethod without method attribute, which (not surprisingly) makes Pythonista exit when called

>>> f = ObjCClass('UIDevice').currentDevice().batteryMonitoringEnabled
>>> f.encoding
'B0@0:0'
>>> f.method
Traceback (most recent call last):
  File "<string>", line 1, in <module>
AttributeError: 'ObjCInstanceMethod' object has no attribute 'method'
>>> f()
Bye bye

I believe this is causes by the final if statement in ObjCInstanceMethod._ _ init _ _ in objc_util, which neither assigns self.method nor raises an exception in case self.encoding is True-ish.
I guess this should be something like

if method:
	self.method = method
	if not self.encoding:
		self.encoding = method_getTypeEncoding(method)
else:
	raise AttributeError('No method found for selector "%s"' % (self.sel_name))

Alternatively, ObjCInstanceMethod._ _ call _ _ could check.

My details: iOS 9.1, iPad Air 2, Pythonista Beta 160036

omz

@Olaf Thanks, looking into it now. The problem seems to be that batteryMonitoringEnabled is a property, and uses a custom selector name (isBatteryMonitoringEnabled).

Olaf

Yes, @omz, you're right on

...batteryMonitoringEnabled is a property, and uses a custom selector name (isBatteryMonitoringEnabled).

I found this isn't unique to battery. The same happens for property AVCaptureDevice.connected that needs translation into method isConnected. I noticed it happens to boolean properties, as e.g. AVCaptureDevice.localizedName works fine.
Hope this helps