Pythonista for Python 3.x.
Are there any plans to release a Python 3.x variant of Pythonista?
@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.
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
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.
Just so we are clear,
Python 3.4 for iOSis utterly useless.
It is based on Python 3.4.0__a0__ (which never existed) instead of the current Python 3.4.2. It does not support any of the new features of Python 3.4 (asyncio, etc.). Has not been updated in the past 20 months (as you say, things do move quickly these daze). Its author has not logged in its user forum in the past 20 months. It has no support for sound, graphics, UI, numpy, etc. And finally, it crashes left and right. In summary, it is not highly functional.
0k ccc - Pythonista it is. I'll be back 😊
@Steep I use RPi via prompt ssh client on ipad. I use a combination of pythonista and vim over ssh for my coding needs. It works really well. I use pythonista ui module for my ipad interfaces and tkinter for pc interfaces. To transfer projects back and forth I use shellistas, ssh/scp plugin. You can also run SimpleHTTPServer in pythonista and use wget on the rpi to grab files.
I'm going to add my request / vote / plea for a version of Pythonista that embeds Python 3. I've been developing some scripts, on my Macbook, with Python 3 and I quite like the language improvements over Python 2. I'd love to be able to use those same language features on my iPad as well. My credit card is out and I'm ready to buy "Pythonista 3" whenever it hits the app store.
IMO, I'd prefer Pythonista to stick with 2.7.x as long as that remains the default install on OS X. That way, scripts I write on my Mac or on my iPad are portable between the two systems with as little hassle as possible.
roosterboy: Agreed—I'm holding onto Python 2 as long as I can. Even if Python 3 is better, there are still things that don't support it, and I'd rather be consistent.
I mostly agree with @roosterboy - the preferred version for Pythonista should be what's included in the latest version of OS X. On the other hand, Python 3 is going to become more popular as time goes on, and eventually when we switch, a lot of things are going to break.
@omz, you mentioned you can't include two versions - is this an Apple limitation?
Here's what I'd like to see in the ideal case. First of all, Python 3 support should be a major paid release. That's a lot of work and you deserve the support. ;) I'd also be perfectly happy waiting for P3 support until Apple makes it the default. When you do, assuming it's possible to have both versions, include P3 and make it the default interpreter, but allow files to have a special comment that, included as the first line of the script, will make it use Python 2.x. You could even add that line to each file as part of the upgrade process, then warn users that new Python 3.x scripts won't be compatible with the old ones.
Most importantly, don't worry about moving along too quickly. I'd rather have an older, stable Pythonista than an unstable version with the newest language features. ;)
I too would be willing to pay for a version of python 3. I think there should be both 2.X and 3.X both sperate applications. That would allow those who have appliations in 2.X to continue to run their applications and allow those who want to write new applications in 3.x to do so. Going from 2.x to 3.x is a major upgrade and it's only fair that you should be conpensated for all your hard work.