Entries for label: python

Found 3 entries.

Things I Like about AppEngine

SO far, I've been enjoying playing with AppEngine. It's been a long process for me, since I've been learning Python at the same time, but very productive I think.

I just thought I'd give a quick list about what I like about AppEngine. However, please not that very soon I'll also be doing a "What I Don't Like about AppEngine".

  • quick and easy development environment (one command to start the server listening on a local port)
  • simple deployment process (one command to upload the application, update indexes and task queues)
  • versioning on the server side, so you can run something like 'stable' and 'experimental' all against the same datastore
  • simple logging, import logging then they capture any logging.info() etc statements into the AppEngine console
  • sending email is pretty easy too mail.send_mail(to, from, subject, body) makes it nice and simple to alert someone
  • no sysadmin maintenance to do! This is a big bonus for me not having to keep servers up to date

... and finally, this isn't really a feature of the platform, but just being allowed to play around with a schemaless datastore has been a whole heap of fun.

Other Sites for Lollysite

I also thought I'd mention that Lollysite is now being used for both chilts.org and the new KohaCon sites. In fact, to get the other theme going wasn't really that hard but better than that, I didn't actually have to change that much in Lollysite itself.

Labels: appengine, python

Inserted: 2009-12-12 19:59 (2 years, 2 months ago)

Site now on AppEngine

It's been a long time coming, but recently I've been learning a lot about Google AppEngine.

It's been a very interesting journey too. Not only have I been learning Python but I've also started a new interest in schemaless datastores (key/value stores, whatever you want to call them).

I even gave a short and unprepared presentation to Wellington PerlMongers about one called Redis. That one looks my favourite so far but yeah, my interest started with AppEngine's Datastore.

Schemaless Datastores

So far I'm enjoying playing with AppEngine's datastore though I find there are some things which are quite finicky about it, mainly due to the Python classes that are being used to help stick data in and get it back out again. Migrations of datastore entities seem to be difficult or as yet some of the techniques to do it are unknown to me (though I have started a list of techniques to help).

Otherwise, once you get your head around not only the data being schemaless but duplicating data so that you can get faster speed and more scaleability, then you're on to a winner. Relations like in a tradition RDBMS are also out of the window though you can reference other objects so it's not completely gone.

Things about AppEngine

Again, so far most things about AppEngine I like, though there seems to be a few things which are harder than necessary.

I managed to find a peculiar bug in AppEngine the other day but still no answer on the Google Group. This is particularly weird as far as I can tell.

And of course, the perenial problem that if something is wrong with AppEngine, all of the developers at Google seem to disappear. And then appear with "Nothing was wrong". Whilst I understand why they do it, it's not great customer relations.

Yet at the same time, the pull of running a site on someone else's servers, that they administer and you don't have to do lots of SysAdmin work, is too great to be ignored. As to whether I'd use it for Mission Critical Applications yet, I don't know.

Overall, it's been a fun (if longer than expected) experience but I'm happy with it so far.

Finally, the CMS/Blog I have written is called Lollysite and check out the project home on Gitorious.

Labels: appengine, python, perlmongers, redis, google

Inserted: 2009-12-06 05:18 (2 years, 2 months ago)

Octal Numbers in Code

I always thought putting a single zero in front of Octal numbers in code was pretty bad, or at least, pretty error-prone. But someone is doing something about it.

In this article, Python 3000 Status Update, Guido van Rossum is putting a new syntax in for Octal numbers and Binary numbers too (see 'Other Significant Changes' towards the bottom).

Not that I ever use them much, but I think it will help. In fact, I said to someone at least a few years ago that '0o....' should be used for Octal numbers :-)

Labels: python, code

Inserted: 2007-06-22 11:52 (4 years, 8 months ago)