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.
Python 3.x Progress Update
-
@omz importcompletion is not relevant for the template? if so is it removed?
-
@Tizzy No, it's not relevant there, and I've essentially removed it to speed up launching standalone apps.
-
UPDATE: figured out there is a built in tool in sublime text to convert spaces to tabs in indentation.
View > Indentation > Convert Indentation to SpacesPS - anyway to scale the size of images posted here?
Also, the traceback popover doesn't seem to let me jump to the actual spot of the error as it seems to usually do in Pytonista 2, but it does show the file and line number. The last spot it lets me jump to is the import statement of the module where the error is actually at, not the module itself...
Also noticed there is a "convert tabs" action built into Pythonista 3 not yet implemented....I'm guessing this will do the same thing.
Ok, so I just tried running my app in Pythonista 3 beta. The tool to 2to3 seems to work.
But I've bumped into something right away. Seems to be much less forgiving in terms of tabs/spaces? Can anyone recommend a tool for sublime text to fix this kind of stuff? I've looked at it and it looks alright. I might have copy pasted it from another part of the code...?
"TabError: inconsistent use of tabs and spaces in indentation"
-
-
I am using Pythonista since december 2015.
I am wondering a little bit about one behaviour of the editor. I just checked on iPhone4 with iOS7 and Pythonista 1.5 compared to Pythonista 2.0x and Pythonista 300001.
If I am on the beginning on a line with indent in v1.5 and press return it preserve the indent. But in all newer versions I am in column 1. I like the behaviour of version 1.5 in this case.
I am sure there is a good explanation why this have changed (and I am sure this was not accidentally).cursor at position ^:
____ line1
____ ^ line2
____line3after pressing return in version > 1.5
____line1line2
____ line3 -
I found an issue in ui editor. I have assigned an image to an button in the version 201002 or earlier. This button is no longer assigned in version 3000001. If I assign another image in version 2010004 (only) this image on the button is also available in version 300001.
And it would be great , if after assigning an image that the image is still selected in the image selection.
-
@wnMark said:
I am sure there is a good explanation why this have changed (and I am sure this was not accidentally).
Well, to be honest, this is just something I haven't gotten round to yet. It's been on my todo list for a while. The reason it changed in 2.0 is basically that I re-wrote large parts of the editor to make it more modular and reusable, mostly so that I can share a larger code base with Editorial, but also to enable features like syntax highlighting for different languages. This has worked pretty well, but there are still a few little things that worked better in the old version.
-
@wnMark said:
I found an issue in ui editor. I have assigned an image to an button in the version 201002 or earlier. This button is no longer assigned in version 3000001. If I assign another image in version 2010004 (only) this image on the button is also available in version 300001.
The image picker in 2.0 (and betas before 2010004) was extremely buggy, and it's difficult to maintain backwards-compatibility with that because it essentially saves incorrect image names to the pyui file. This should be fixed in 201004 (and 3.0), but it may unfortunately be necessary to fix old pyui files manually by re-selecting the images.
-
@omz said:
The image picker in 2.0 (and betas before 2010004) was extremely buggy, and it's difficult to maintain backwards-compatibility with that because it essentially saves incorrect image names to the pyui file. This should be fixed in 201004 (and 3.0), but it may unfortunately be necessary to fix old pyui files manually by re-selecting the images.
@omz
I understand, not a big problem for me -
Just tried the appex module. Using appex.get_url() from the extensions console I got the error:
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/var/mobile/Containers/Bundle/Application/3DC76E83-91BE-4A1F-A8A2-2A00120079CC/Pythonista3.app/Frameworks/PythonistaKit3.framework/pylib/site-packages/appex.py", line 114, in get_url
return _path2url(url)
File "/var/mobile/Containers/Bundle/Application/3DC76E83-91BE-4A1F-A8A2-2A00120079CC/Pythonista3.app/Frameworks/PythonistaKit3.framework/pylib/site-packages/appex.py", line 5, in _path2url
import urlparse
ImportError: No module named 'urlparse' -
-
Isn't it called
urllib.parse
in Python 3?@omz Bug with
ui.TableView.delete_rows
: when deleting rows from a table with sections, the tuples indicating the rows to delete have to be reversed, i. e. currently you have to writetableview.delete_rows([(row, section)])
, and what I would expect to be correct istableview.delete_rows([(section, row)])
(as described in the docs forui.TableView.insert_rows
). -
I am missing the keyboard shortcuts (callable with COMMAND key) in 300001. They are available in 201004
Ole @Omz if you fix this, more shortcuts would be great. Like Page Up/Down (At the moment CONTROL-Up/Down and COMMAND-Up/Down do the same and go to start or end of file).
OPTION DOWN is going two lines downwards and only one line upwards. More lines would be great (or goto end/start of a logical "block")Or instead of Page Up/Down, goto prev/next "def()"
-
No shortcuts in V3? They are not working for me, thanks
-
Doing the 2to 3 conversion with that file
-
- If you are in the Console and the press ? to get the Online Help
- The press the top left button to open the split screen (the shaded one)
- Then the right portion of the screen (Console) the fonts at the top/search bar and Help title "Overview" will all be overlapped and messed up
- If you try to press again the split screen button (shaded one) you get the pull down menu for Overview
-
Also, using appex.get_url fils because there is not urlparse
-
@filippocld This has been mentioned elsewhere.
-
Congrats on finally getting this project done. I just signed up to beta test and would like to offer help specifically with the template and any feature that directly speaks to users who wish to use Pythonista to write their own Apps for the AppStore.
From a feature perspective:
-
I would like to see the template kept in sync with the build so that developers would get bug fixes as soon as any other user. I would love to hear about why this is such a problem but can surmise that the template project is currently "hand built" or requires a great deal of manual work for some reason. Let's fix that once and for all.
-
I would like to hear about any progress that has been made in supporting integration with third party projects like OpenCV. I have noticed that other development environments support "plug-ins" that seem to be shared libraries and manage to make it through the App/AppStore process just fine. I have no idea yet how they are accomplishing this but I would be happy to research this and report back if we could make it a project to get this done for Pythonista.
I have been thinking a lot about the template and it purpose and future and believe that it is actually a product all by itself. It needs to have a defined purpose and a set of use cases and then offered in the AppStore for a fair price for what it delivers. For anyone using it to do professional level App development you should be able to charge a hefty price and look at paying someone to maintain it for you.
I am going to stop writing now. This is getting too off topic.
UPDATE: I have been syncing up with all the posts from the last 4 days and notice that the template was updated on GitHub at the same time as the 3.x beta - so part of my question may already be answered there. I won't post again until I actually install the new beta and download that template.
-
-
- All the built-in functions and types seem to be missing docstrings and signature info. In Pythonista 2,
help(tuple)
would print at least the docstrings, in Pythonista 3 only the method and attribute names are shown. Method signature info for built-in functions (part of the "argument clinic", which I think is an overhaul of function argument processing in C code) is a new feature in Python 3, which would be very nice to have. - Using an external Apple wireless keyboard, when typing dead keys (such as ^ or ~ or ` or ´) they appear once too often. For example, if I type
~
-space, I get~~
, and when I type~n
I get~ñ
. I've tried many combinations and there is no practical way to suppress the double character. - The Pythonista 3 share sheet action is elegantly named "PythonistaAction3".
- All the built-in functions and types seem to be missing docstrings and signature info. In Pythonista 2,