This article in the NY Times came across Neohawk IT this morning. Looks like Amazon offers three new services for ecommerce or online financial transactions; Amazon Checkout, Amazon Simple Pay, and Flexible Payments Services(for developers). Amazon will now compete with Paypal and Google Checkout.

Strikes me that advantage with Amazon is that a whole lot of people have accounts at Amazon and won’t need to register their information like credit cards again, but can take advantage of what they already have registered. That’s handy.

I’ll need to check out the pdfs and code samples to see how easy it is to integrate into a website. I have one in mind for which Amazon may be the better solution than what we have now.

For now, I have turned off the Japanese planets, Planet Ohio-Japan and Planet Uchina. There is something decidedly odd with them as they eat up all my memory. Not sure what it is at this point, and don’t really have time right now to fix ‘em. I’ll get to them eventually, but for now they are down.

Yesterday at the “Sausalito Sprint“, a bunch of folks started merging some backwards-incompatible changes to the django trunk. So if you are developing off of trunk beware and forewarned, if you hadn’t already known.

I wasn’t aware it was happening this weekend, and all of a sudden a little site I’m developing went kaplooie. (Is that a word?). II knew that I had updated my django source from the trunk, so I didn’t panic. Made some minor changes, and at least my local dev server would start. In particular, I removed the prepopulate_from = (_(‘title’)) from my models. So I want to localhost:8000/admin but none of my models were there.

Which isn’t surpising now that I have actually read the backwards incompatible changes page. With the merging of newforms and using newforms in the admin, some other changes have also been implemented. One is that you now need to separate a separate AppNameAdmin(model.Admin) class. And you need to import xxx . So for example, I have a simple model (still under development) that describes “prints”. I had to add the following:

Once I added this and resynced the db, the Print model showed up in /admin. I haven’t figured out how to do radio buttons with choices yet, but I just started catching up here. I also had to update the django-tagging module from trunk, and after doing so that worked just fine. I know need to go through the various modules I’ve used to see what’s been updated.

At the same time, due to the shear number of changes that look to be coming in the run up to the Django 1.0 release, I’m not sure I want to be touching anything that’s already running until these changes are finished. For example, I am going to postpone using S3 as the ability to use different, including remote storage like S3, appears to be part of the 1.0 feature set. So I might as well wait a month, until those changes are final.

Now it’s time to find out what else has changed!

今朝、やっとPlanet Ohio JapanとPlanet Uchinaを直した。　この間、アップグレードした時から いくつかのフィードがhtmlそのまま表示されていた。　修正方法は簡単だったのだが、なんかなんか、時間をとれず、修正していなかった。

今はPlanet Uchinaを削除しようかなと考えています。　アクセスは殆んどないし、　実は自分もあんまり見ていないっす。　というか、自分のRSSリーダーによほど沖縄関連内容が多いためそこを使っている。そして、他の方も興味がないそうで、サーバー資源を考えたら不要かなと重い始めています。

もし、残して欲しければ、コメントを残してください。今月末までにコメントがなければ削除します。