The PythonAnywhere newsletter, June 2016


Summer is just around the corner in the northern hemisphere – here in London we can tell because the rain is just that little bit warmer. We’re taking full advantage of the lighter and later grey in the sky by working even longer hours to make PythonAnywhere better. How? Just read on…

Better databases!

Over a year ago, we started supporting Postgres databases. Since then, we’ve found that we’ve been able to optimise the service so that it scales better than we thought, so we’re pleased to pass on the cost savings to you.

Postgres is now $7/month instead of $15, so if you’ve ever thought about checking it out but been put off by the price, now’s the time to take a look!

We’ve also applied the new price to existing Postgres users for their next bill. So that’s more moolah in your pockets dear users, don’t spend it all at once ;)

Also – the way we handle MySQL databases needed some work to make it faster, more efficient, and more scalable. Over the last month we’ve learned more about obscure aspects of database administration than we ever wanted to know… but the end result for you should be that your database access is faster and smoother. Let us know how it’s going!

Useful tips and interesting ideas

The inside scoop from our forums

New modules

Although you can install Python packages on PythonAnywhere yourself, we like to make sure that we have plenty of batteries included.

We haven’t added any new ones since our last newsletter :-( – but we’ve got a bunch in the pipeline – more next time!

New whitelisted sites

Paying PythonAnywhere customers get unrestricted Internet access, but if you’re a free PythonAnywhere user, you may have hit problems when writing code that tries to access sites elsewhere on the Internet. We have to restrict you to sites on a whitelist to stop hackers from creating dummy accounts to hide their identities when breaking into other people’s websites.

But we really do encourage you to suggest new sites that should be on the whitelist. Our rule is, if it’s got an official public API, which means that the site’s owners are encouraging automated access to their server, then we’ll whitelist it.

Here are some sites we’ve added since our last newsletter:

  • archive.org and web.archive.org – the Internet Archive!
  • ifttt.com and maker.ifttt.com – If This Then That
  • *.cartodb.com – “the easiest way to map and analyze your location data”
  • blockcypher.com – Blockchain web services
  • api.coinbase.com – more Bitcoin goodness
  • api.geonames.org – a geographical database
  • api.greenhouse.io and app.greenhouse.io – APIs for human resources applications
  • api.infobip.com – enterprise messaging
  • api.ipify.org – an API for digging up information about IP addresses
  • api.locu.com – a GoDaddy service for posting your details to aggregators like Google, Yelp, and so on.
  • api.trackingmore.com – parcel tracking
  • api.tropo.com – phone and text APIs
  • api.yummly.com – a recipe site
  • lapi.transitchicago.com – Chicago Transit Authority

And that’s it

Thanks for reading our newsletter! Tune in the same time next month (ish) for more news from PythonAnywhere.

comments powered by Disqus