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
-
-
Another thing. The ability to switch between the script and the associated UI file with a touch of a button. The tabs system is cool, but for switching between scripts. Separately opening a pyui file is a lot of work) Because I find the "+" button in the code editor rather useless, maybe there could be a shortcut to a UI file in its place?
P.S. Is this the official bug reporting topic? Cause I have a feeling it's not so I feel bad about flooding :p
-
@omz so: your most recent update is amazing. I love it. But it came with a removed feature that was really amazing in the other versions. Alignment. In the UI designer it is so hard to align elements properly in relation to each other due to the removal of the alignment feature.
-
@omz said:
@zense I don't check every day if new people have signed up, and right now, iTunes Connect is down, so I can't send invites (or upload betas) at the moment.
Ah...
Just did a quick check. Apparently there is a workaround. Just go via developer.apple.com rather than itunesconnect... Saw this via some tweets
-
@zense Yes, I saw that too (doesn't seem to be necessary anymore). You also should have gotten an invite already. Maybe check your spam folder?
-
I discovered a very small issue in 3000005 (and same in 201005).
I have send some selected files and a sub folder with mail. The folder was summarized in one file without extention ZIP. No problem after I renamed the file everything worked fine!
-
I am using iphone6 in "zoomed view mode". In this case in setup I am missing the option "Show Line Numbers". If I am in "standard view mode" I can switch to this option and the lines still remain in "zoomed mode". I suggest to ofer this option in every mode and also for other iphones in lower resolution.
-
Moar stuff, this time it is about the docs in the new beta.
Slightest issue:raw_input
is mentioned in the console module docs, however, as you know, it no longer exists.
The contacts module documentation badly needs renewing. First of, the examples are given in Python 2 so running them results in an error (mostly the prints). Then, the indentation is 2 spaces. Like wow, that just took me a second to deal with it and proceed :)
Also, the reminders module docs are in Python 2 as well.
That's not something that desperately needs fixing but it would be nice -
If I make a "Indent" on a marked text, it work fine with indent of context menu, but if I make the indent with the key on additional keyboard or with tab on a bluetooth keyboard, the selected text is deleted.
-
Trying to get the dropbox sync script working in P3 and running into OAuth errors. Google is telling my its to do with dropbox not supporting python3 and that I need to install the new SDK https://github.com/dropbox/dropbox-sdk-python
Is this something I can install myself somehow or does pythonista need to be updated?
-
I thought @omz had included the Python 3 versions of all modules with Pythonista 3. Can you post the error that you get (and the code, if you made any changes)? Then we might be able to help you.
-
I've updated most modules for Python 3, but I think I might have missed
dropbox
... -
Hi, any update or timeline on the new beta or final release? thanks
-
+1 @OI ... We are only 6 or 7 weeks away from Python 3.6 alpha 1 being released and it would be great to have Pythonista3 (.5.1) released before Python 3.5.1 is no longer the latest and greatest Python release. Pythonista is still Python 2.7.5 vs. 2.7.11 being current so it would be great to have a shipping Pythonista that is the current version of Python.
I really think that Pythonista3 is not perfect but it is good enough to ship and I doubt that users would be displeased by its current fit and finish. The perfect is the enemy of the good.
But of course the decision rests with @omz where it belongs.
-
The final version of Python 3.6 is still quite a long way off, so I'm not too concerned about that...
The current beta is taking a bit longer because I'm in the process of making some pretty substantial changes. In short, I've found out that my assumptions about using Python 2 + 3 in the same app were incorrect, and that it is in fact possible to do this, even without having to restart the app when switching interpreters.
As I really only want to have one version of Pythonista, to avoid confusion and backwards-compatibility woes, my current plan is to make Pythonista 3 support both Python 2.7 and 3.5. It's actually working quite well already, but there are just a lot of little details to consider, things to move around, refactor, etc.
This doesn't change my plan to make this a paid upgrade btw.
-
You never cease to blow my mind! Super impressive. The duplicate standard library and duplicate docs size is not going to cause the combined app to be too big?!? Pythonista 2 on the App Store is already 236 MB.
-
The duplicate standard library and duplicate docs size is not going to cause the combined app to be too big?!? Pythonista 2 on the App Store is already 236 MB.
I do think that 3.0 will end up being bigger than 2.0, there's probably no way around that, but I'm fairly optimistic that I can keep the size increase reasonable.
I've already optimized a couple of things, e.g. by compressing the documentation in recent betas, and parts of the documentation can probably be the same for 2 + 3 (e.g. matplotlib, which is actually the biggest part).
The standard library will have to be duplicated of course. I'll have to look at the third-party packages individually, to see which of them can be shared (some have separate Python 3 code bases).
Right now, my priority is to get everything working smoothly, so the first betas of this "universal" version will likely end up being bigger than they strictly need to be, but optimizing the size of the final app is definitely on my todo list.
-
Sounds great! This will probably make the move to Python 3 much easier for people who aren't used to it or have lots of Python 2 code. And it should make it quite obvious which version new people should buy, if PythonistaSix supports all of Pythonista 2's features and adds Python 3 support.
@omz If it's possible to switch between Python 2 and 3 interpreters without killing the app, would it be possible to do a proper interpreter restart before each script run? I do like keeping my interactive environment when running scripts, but having a proper reset function would also be useful. Lots of obscure bugs can happen when something unexpectedly isn't reset between runs (e. g. attributes of non-user modules) and some programs intended for "normal computers" can fail if they aren't run in a fresh environment (e. g.
setuptools
/pip
caches package installation state in a global module). -
@omz, wow you never stop amazing me, you keep raising the bar!!! Looking forward for the paid upgrade.
-
I'll have to look at the third-party packages individually, to see which of them can be shared (some have separate Python 3 code bases).
@omz, just a thought. I am guessing you had it already. But a way for the user to download 3rd party documentation separate from the install. Could streamline a lot of things for you. I can't see that should be burdensome for the user. Also would give you a way to update the help without app updates. I am sure many other benefits.