When Apple announced the Safari 4 Beta, I was itching to try it out right away, but I knew that if I installed it, the current WebKit would get wiped out my system. This might be acceptable for most, but I would like to keep testing my sites against Safari 3 at least for another year before moving on. So I waited until someone came up with a solution to install them side by side. Brian Mastenbrook’s package extractor seems like exactly what I need, it works very well for me so far.
I love the Google Maps API, it’s fairly easy to use, well documented, has lots of features to tweak and extend beyond the obvious. However, it’s hefty. The initial load with map assets can easily total 300K, and visibly slow down your site especially if you are providing more than one map on a single page. So, to solve these issues I decided to write a thin layer around the Maps API.
I am currently working on a Django project that will run on FreeBSD when deployed. I had never worked with this distro before, so it took a bit of getting used to, and I ended up reading man pages and Googling mailing list archives until the wee hours of the morning. One issue that really caught me by surprise was recompiling Apache 2.2 with the proxy modules, so I thought I would jot down my notes here.
After a few days of work, I finally reached a preliminary release of the little scraping project I mentioned before. I wanted to test this version on my production server, so I deployed it, and immediately started seeing some weird parsing issues with Beautiful Soup.
I started working on a little project for myself today and since it involved parsing some content from a site that doesn’t publish APIs, I turned to Beautiful Soup for help. After a couple of hours of coding, I was already starting to scrape nicely formatted data when I got a parser error!
© Copyright 2001-2010 Taylan Pince. All rights reserved.