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
-
@Leva7 I'll add a setting for that. It's unfortunately not possible to use the system setting.
-
Still accepting new beta testers? I've applied but not yet been accepted. Excited to try this! I've been wanting 3 forever π
-
@davidskeck said:
Still accepting new beta testers? I've applied but not yet been accepted. Excited to try this! I've been wanting 3 forever π
so has my friend. Normally new ones are sent out at every new beta release, but he hasn't gotten it in the last two releases.
-
@Webmaster4o I've actually checked the signups an hour ago or so, and I've added everyone on the list (I've also added about 100 people yesterday). Could you ask your friend to check his spam folder or send me his email address privately, so I can check if he's on the list?
-
No, he hasn't got it. I'll have him resubmit.
-
@omz I also applied for beta testing some days ago using Google Forms, but neither have I received an invitation. I have just re-applied.
We use Python 3 as main programming language for our EE, math and physics grades (since 2010) so I have a high interest in the new Pythonista with Python 3.x support.
-
Just wanted to chime in and say thanks! Just got the beta and it's great! I've been wanting this ever since I learned Python could be interpreted on iOS, and this is a lovely implementation of it.
-
@Webmaster4o @jmas I've just sent invites to these email addresses (I've obfuscated them, but I hope you're able to tell if yours is on the list):
niβββββββes@gmaill.com
pβ.tβ.gβ@gmaill.com
jβββββe@gmaill.com
jβββββββa.aβββββe@eβu.es
bβββn.hββββββββn@uββc.uββββββo.ca
bβy@eβββββββo.com -
Hi omz,
same issue here: Applied for the beta a few days ago, but I'm not on the list (nor did I receive a testflight invitation).
Unlucky me :/ -
@omz Invitation received, thanks!
-
@omz I believe his is the second one. I'll ask if he got it.
-
@omz really 2 ll's in "gmaill" ?
-
@MartinPacker No, I think that's a mistake.
-
@omz By the way, how about that keyboard dismiss? The way it is now is not so convenient since it actually makes you scroll the code and lose the position. A button or something like that would be great :) Is that a possibility or you've completely switched to swiping down?
-
@Leva7 I think I'll keep it the way it is. It's pretty difficult to find a place for a "dismiss keyboard" button on such a small screen.
-
I just registered here after seeing this thread.
I am a new python programmer and am - right now - shunning 2.7 as I am starting to learn python on 3.xThis is the best news ever and I am anciously awaiting the full release.
Best,
zielperson -
@omz A few suggestions regarding the new autocomplete feature:
- When the user has fully typed a suggestion out by hand, then make Enter behave like normal and insert a newline. The current behavior can be a little surprising, for example when typing
return self
you need to hit Enter twice to insert a newline - first to accept the suggestion, then for the newline. Same goes for typing a bare variable name in the interactive prompt to display it. - Related to the previous suggestion - when there is only one suggestion and that has been fully typed out, hide the suggestion popup entirely.
- Allow dismissing the suggestion popup with Escape on an external keyboard.
- Please take the caps of what the user typed in account when showing suggestions. When I write
typ
, I probably wanttype
, and when I writeTyp
, I probably wantTypeError
.
- When the user has fully typed a suggestion out by hand, then make Enter behave like normal and insert a newline. The current behavior can be a little surprising, for example when typing
-
Also, how hard would it be to check for a
@property
decorator in the autocomplete and then not put in parentheses? -
Any decorator really should not have parentheses added automatically. Some decorators allow arguments using closures, but there are many that do not take arguments and do not even allow empty parens. This includes most built-in decorators, like
property
,classmethod
andstaticmethod
.Speaking of parens - when editing an already typed line, the autocompletion often inserts extra parens before an existing function call. For example, say I have this line of code:
mylist.append("foo")
Then I decide I want to use
insert
instead. I double-tapappend
, typeins
, and hit Enter to accept the suggestion. The output I get ismylist.insert()("foo")
In this case I would expect it to detect the existing parens and not add extra ones.
-
I will admit I didn't like the insensitive matching originally, but zi do find it useful in objc... though I agree the typed case should be given priority to other matches.
Also, i think attributes starting with underscores should have lower priority (unless user starts typing an underscore). Pretty much every object has a dozen magic double underscore attributes which are rarely needed -- put _ and __ at the end of the non-matching list.