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.
Pythonista for Python 3.x.
-
Personally I wonder why @omz would continue with Pythonista now that Editorial is well established. Is there something I'm missing here?
In addition to what @ccc and @jonmoore said, Pythonista is actually more successful commercially than Editorial (currently about 2x-3x). Of course, part of that may be due to Editorial not being optimized for iOS 7 yet etc., but I still think Pythonista can appeal to a lot of people with a Python background that I couldn't easily reach with Editorial. While there's a lot of shared functionality, the focus of the apps is just very different, and I'd guess that a lot of folks find Pythonista just by searching for "Python" in the App Store.
I also have quite a lot of ideas to differentiate the apps a bit more going forward, starting with numpy/matplotlib in Pythonista...
And to clarify my question above, I understand that the Pythonista app can't have both 2.7 and 3.4 Python distributions in the same app. My question was whether an IAP can direct the user to a fresh download that isn't publicly available. It's more a question of App Store policy as most IAP's I've encountered effectively switch on content/modules within an existing App.
That's not possible. In-App-Purchases can basically just unlock existing functionality within the app or download content (e.g. new levels in a game, an e-book...), but not any kind of executable code. It's also not possible to have separate apps that are only downloadable via IAP in a different app.
-
I'm glad to read that Pythonista is more successful commercially than Editorial. I'm not a Python programmer, but I could use Pythonista for coding exercise and brainstorming, especially on the go, or while relaxing on the bed or couch. That really helps for my use case. :)
-
@omz, @ccc and @jonmoore I also have both but really only use Editorial. I guess my focus is text but could become more interested in Pythonista if I can fit it into my workflow which would, for example, feature graphics.
I still think Editorial needs better GUI components - such as a list picker - and that might be where Pythonista comes in. Dunno.
Anyhow I'd happily buy Version 2/3 of both.
-
I still think Editorial needs better GUI components - such as a list picker - and that might be where Pythonista comes in. Dunno.
Both will get better GUI components, but a list picker is already available Editorial (the "Select from List" workflow action). Or did you mean something different?
-
Thanks @omz I probably just failed to notice it :-) unless the list isn't programmatically generatable. In which case I didn't. :-( :-)
-
@MartinPacker – You can generate the list programmatically by using workflow variables. Because each list item is a separate line, individual items cannot contain linebreaks though.
-
For what it' worth, I love the simplicity of the existing 'select from list' action, especially when combined with the tab delimiting functionality. Simple but very useful for creating workflows that trigger other workflows. My whole bookmark bar is populated with 'select from list' workflows. :)
-
-
@omz Will play with it. I guess I'm too hung up on everything being a single Python script. Talking of which back to the Python 3 discussion. :-)
-
Gee, I go away for a little bit and miss all the fun...
Personally, since the next versions of Pythonista and Editorial are going to involve some radical changes anyway, I'd vote for making them "Pythonista2" and "Editorial2", with Python 3.x (only), and keep the existing versions around in maintenance mode
I would disagree with this as I still believe a version of Pythonista that supports 2.7 should be publicly available and this strategy will mean that only those that already own Pythonista will be able to access a version that supports Python 2.7.
To be clear, by "maintenance mode" I wasn't suggesting pulling the current versions from the store, just not upgrading them beyond bugfixes. They both work fine on iOS 7 as is.
Short of "no Python 3.x ever", and given that both flavors can't run in the same executable, the remaining choices are either to switch both existing apps to Python 3.x at some point (leaving users with no choice), or to release new "v2" (or "v3", if you will) versions of the apps and keep the current (Python 2.x based) apps around, in which case Ole can either put extra work into keeping all four of the apps in sync, featurewise, or he can leave the current ones pretty much as-is (save for bugfixes) and concentrate new work and features on the Python 3.x versions going forward. I was voting for this latter case (and yes, I completely get that it's Ole's baby, this isn't a democracy, and we can only make suggestions / express preferences).
I was promoting the idea of doing the change at this point because (aside from "hey, more new toys for us"), Ole's recent work points towards releasing new versions of both apps simultaneously, with significant user-visible changes (sounds like Editorial's workflow entry has been "reimagined" because of the iPhone), and with Editorial going Universal.
If Ole doesn't hard-switch both apps (and all the users) over to Python 3.x at some point in the future, there will eventually need to be new Editorial3 / Pythonista3 apps, and casual users will want to see substantial user-visible changes when facing the prospect of paying for a brand new "edition" of an app (particularly on the Editorial side, since it presents to the casual user as "merely" a text editor - Pythonista users, on the other hand, will tend to see Python 3.x itself as a new major feature), and Ole's got those kind of changes in hand already, so it'd be a fitting time to make the jump.
And now I'll stop talking (sorry, I sometimes explain at length in cases where it looks like I'm arguing vigorously for or against something, when I'm actually just trying to clearly convey the precise "flavor" of my point - that's sort of what's going on here - sure, I'd like to see Python 3.x sooner vs. later, but what I'm most anxiously awaiting is the iPhone version of Editorial, so I'll be able to use the same text editor on both iPhone/iPad).
-
Python 2.7.7 was released today: http://hg.python.org/cpython/raw-file/f89216059edf/Misc/NEWS
That leaves just two remaining Python 2 releases: 2.7.8 in 6 months and 2.7.9 in 12 months.
-
Python 2.7.8 was released on 01 July 2014 so there is now just one remaining release of Python 2.
-
That's not quite true. Python 2.7 will be supported until 2020. See PEP 373
Nevertheless I would also like to see Python 3 support in Pythonista. Python 2 is in maintenance mode, Python 3 is where the cool new things are being developed.
I wouldn't mind paying anew for Pythonista 3. If it were possible to have both interpreters in one version, this would be even better, of course. To decide which interpreter to use, it could use the shebang line, if present, else a user preference.
-
Yes. That history is in my posts above but...
We are at Python 2.7.8 now and Python PEP 404 makes clear that there will never be a Python v2.8.
So, how many more release numbers can you fit into the formula:
2.7.8 < version_number < 2.8.0
?Python3 is the way to go.
-
As many as you like.
-
@ccc
2.7.10, 2.7.11, etc. -
You are correct... http://legacy.python.org/dev/peps/pep-0373 now forecasts the following Python 2 releases:
Planned future release dates: 2.7.9 December 2014 2.7.10 June 2015 beyond this date, releases as needed
-
Hi
Has this discussion run out of steam. I am a hobbiest and a code for fun user of the iPad, a fairly recent acquisition. Apple seem to be determined to drive coders towards their Mac. products. The iPad certainly needs a functional coder app, As far as my searches go it would seem that Pythonista is top of the list. However it would seem that anyone starting now could well get nicely settled down, happily coding away when ' bang' , they find they are saddled with an outdated system.
We now have I0S-8.1 that won't accept SWIFT and Pythonista that doesn't like the look of Python 3.4. I was hoping to move up from playing around with BBC Basic for Windows. Perhaps I should buy a Raspberry PI to satisfy my fun to learn coding needs.
Steep - 86+ looking for enlightenment. 😉 -
Python 2 is highly functional. RPi is awesome but can you really take it with you in the same way that you do with your iPad?
-
Hi ccc. - My desktop PC and my laptop are in my home office. I practice my computer hobby from an armchair.😊
I've got 'Python 3.4 for IOS' on my iPad but can't get IDLE. If push comes before pull, then suppose I will have to settle for 2.7 on Pythonista.
When I became a silver surfer and the proud owner of an iPad I thought that was it, but things do move on rather quickly in this day and age.