Beta Status Update

blmacbeth

@JonB thanks for pointing that out. I played around with the Physics Clock and it did everything you said it would. I think that my problem comes from the sprite kit editor. If you set the physics from the editor (not programmatically) then it keeps the defaults that where in the editor. I can fix this by manually changing them from the program.

@omz the bug is that the default physics attributes from the sprite kit editor don't change if you change them from the editor.

123npszjhl

Will Pythonista support pyd pyo pyx etc. in the future? Many useful modules require these formats.

dgelessus

pyd files are dynamic libraries. As far as I know they don't have a specific format - on Windows for example they are just dlls with a different extension, on other operating systems that's probably also the case. This means that most pyds would not be compatible with the iOS kernel in the first place and would need to be recompiled from source code. Because Apple doesn't allow apps to dynamically link to custom libraries it wouldn't be possible to use those anyway.

pyo files are optimized Python bytecode. (Optimized means that any assert statements, and sometimes docstrings, have been removed.) Their format is the same as for pyc files, which Pythonista already generates to improve module loading speed. These files are usable in Pythonista - IIRC someone has done this before - but there's little point in doing that, you might just as well use the Python source code for the files.

pyx files are Pyrex or Cython code. Both are languages that are syntactically similar to Python, but compile to C source code and can use C types and libraries. The problems with these are the same as with pyds that I explained above.

zencuke

I upgraded my iPhone 6 to iOS 8.3 and Platformer game works now. Unfortunately I don't remember the iOS version that failed.

polymerchm

I am getting a repeatable crash of pythonista 1.6 when editing a meduim sized file. It comes when I type anything after I type the instace of a tableview and then the period. I beleive this is an autocompletion issue. But I can't figure out how to disable autocompletion to test it.

dgelessus

Does clearing the code completion cache change anything? If not, mind uploading the code in question to Gist? Interestingly I don't get any code completion at all for a TableView instance.

AFAICT it isn't possible to disable code completion (or switch it to "simple" mode) anymore in the latest beta. There isn't even an option for that in the com.omz-software.Pythonista.plist file anymore.

JonB

I do get TableView instances to code complete, though the first time takes a few seconds.
I have observed requests objects, and Gittle objects take a really really long time to complete(like minutes....I think the innards of these are very dynamic) in 1.5, which locked everything up until a completion popped up! The workaround was to type a space, then period followed by your attribute, then go back as backspace out the space. This prevents autocomplete from happening, at least in the console. Misspelling the object name also works,etc.

JonB

Blmacbeth, where are you setting the physics? Make sure you are setting it AFTER calling sk.load, otherwise load overwrites anything you have set already.

polymerchm

I've uploaded pyuiEdit as a repo here. The offending code is in the script walker.py at line 312.

Gcarver166

node.copy() does not copy the physics body correctly. The node copy points to a physics body but I think it's the same as the original. I have to manually make a copy.

polymerchm

More on autocompletion explosions. I opening up chordcalc.py and typed

tvCapos.delegate = fred

When I went to the file menu to switch files, the app crashed.

JonB

Re: platformer grey screen. I found on IOS 8.2 that removing the [`orientations='landscape'] from the last line, then rotating my device after pressing play, the game was playable.

polymerchm

It's fine in 8.3.

blmacbeth

@JonB, I am setting up the physics through the sprite kit editor, not through the script editor. The first thing I do in the script is things = sk.load('things.pysk, sk.Node()). I would assume that the numbers I set in things.pysk would load there. However, when I run the following: (where I have set restitution in things.pysk to 0.5 )

ball = things['ball']
print ball.physics_body.restitution

I get 0.2 and not 0.5. I found a work around by setting the restitution in the script editor.

polymerchm

Hooked up to my Mac and used XCODE to look for a crash report. None.

dgelessus

(Thought I had posted this before...)

I manually imported jedi and tried to get a code completion on one of the problematic spots. At some point it ends up in an infinite recursion loop, until the interpreter throws an exception due to exceeding the recursion limit. Why exactly this happens I can't say though.

polymerchm

An off switch would be nice. This was not a problem (in 1.5). @degelessus: Which version of jedi did you try? The installed jedi in 1.6 is 0.9.0. Perhaps a rollback to 0.8.1?

mteep

@polymerchm It seems that only crash reports with file names ending in ".ips" are shown in Xcode. Those that have been transferred are renamed on the device to ".ips-transferred" or similar. Those from the Pythonista beta end in ".ips-beta" or so. Fortunately, they call all be viewed on the device, if you go to Settings -> Privacy -> Diagnosis ... -> Diagnosis ... (or something close to that).

polymerchm

@OMZ Do you automatically get crash logs, or can I send them to you? Will sync device tonight and see if I have logs relevant to the autocomplete bug (now that I know where to find them).

Omega0

I've found an issue where editor.make_new_file() causes the app to crash. It doesn't seem to matter what arguments I pass to it the app just shuts down.