Bug list for beta release 160037

JonB

With the built in traceback viewer, IndentationError (expected an indented block) does not highlight the line number in the editor. This is strange, as IndentationError is a subclass of SyntaxError, which does highlight the offending line.

omz

@JonB said:

Can anyone on ios8 using a 32 bit device check if the extension works? i.e safari share sheet, does clicking Run Pythonista Scropt do anything? this is the second build for me where it does not.

Thanks, I just tested it on an iPad mini with iOS 8, and it doesn't work here either. I'm looking into it, not sure yet what to make of the crash log.

omz

@JonB Turns out I had accidentally left some testing code there that was using ReplayKit (iOS 9 only).

JonB

Not sure if this one is new or now, but the editor seems to be stripping of trailing newlines from files. I have not completely confirmed this yet, or whether it is a dulwich thing, or an editor thing, but my git is showing any file i open gets the final newline removed.

dgelessus

No, this is a feature of the editor, and it's been in for a while. (IIRC I included it on one of my long bug/suggestion lists at some point.)

JonB

autocomplete bug in console: any autocomplete in console that occurs after an equal sign results in the whole line getting replaced with the autocompleted item. Pressing a space after equals makes things work as espected.

JonB

bug: selecting /copying text from console output in split console mode does not work. Instead, select targets the console input. This is similar to a bug for the main console tthat was fixed in 160036 or earlier.

edit: actually this happens in either mode, but only when a quote is opened in the console input. i.e, typing

ObjCClass('

then trying to copy a class name from a previous console output does not work

Olaf

Though path is an optional argument to scene.ShapeNode(…), omitting it causes an attribute error because None has no line_width. Probably should be optionally assigned in line 287 of module scene:

if path is not None:
    self.line_width = path.line_width

The workaround is to use an empty path in scene.ShapeNode(path=ui.Path()).

ccc

Or start scene.ShapeNode.__init__() with path = path or ui.Path()

Olaf

While

import scene
v=scene.Vector2(3,4)
print(v/2)

works as advertised, adding

from __future__ import division

yields a type error (unsupported operand types). See operator.__truediv__ why this is so.
The workaround is to multiply (print(v*(1/2))), but obviously scene.Vector2.__truediv__ = scene.Vector2.__div__ would be much preferred.

Olaf

@ccc, your code works well, but what I didn't explain before is that I want to create a ShapeNode without an initial path, and set the path later. Creating a dummy path at initiation works, but seems wasteful. Also took me some time to figure out, why my code wouldn't work

Phuket2

Documentation Error
@omz, the Rect.inset api text appears to be wrong. The Rect param to pass in is not listed, omitted.
Is
Rect.inset(top, left[, bottom, right])
Think it should be
Rect.inset(other_rect , top, left[, bottom, right])

omz

@Phuket2 The inset method doesn't have an other_rect parameter (and I'm not sure what you'd expect it to do, maybe there's a misunderstanding about what the method does?).

dgelessus

Maybe inset is a normal method that you should call on a Rect instance (like a_rect.inset(...)), and you're trying to call it as a static method (like Rect.inset(a_rect, ...)).

Phuket2

@omz , yes I see now. Title should have said brain error. Too much alcohol of Christmas and new year. Oh, well sorry.
@dgelessus , you are right. I was not calling on an instance as I should have been 🤐 I am going to go and crawl under a rock now. With a whisky of course 😱

Webmaster4o

One documentation bug is that under documentation for the string module as well as for the built-in-type str, after all methods being listed, they are all listed again under deprecated methods, with only the actually deprecated methods having badges as such.

JonB

@JonB
in 2.0: (starting to update the running list as these are tested in 2.0)
* Deleting editor actions (from wrench) crashes pythonista in ios8.4.1 on ipad3.
* Copying from console does not work reliably if keyboard is shown (copy option is not shown, only paste. Can always be reproduced if opening s single wuote in console input, then trying to copy console output, but occurs in other situations as well)

Webmaster4o

In console prompt, if tapping an autocorrect prompt, it replaces your entire text
On the extended keyboard on iPad, long pressing on a key in the top row will show a pop up, but this popup is invisible for the bottom row.

JonB

The link to the forums in 2.0 seems to be broken. it points to
http://omz-software.com/pythonista/forums
which returns an object not found error.

Webmaster4o

@JonB The link you just posted redirects to https://forum.omz-software.com/category/5/pythonista for me.