Python

Run Python 2.7.3 and 3.3.0 on OSX Together

November 30th, 2012 0 Comments

Any Django developer has been using Python 2.7.x for some time now, but as Django 1.5 continues to move toward release, there will likely be a large number of developers officially moving to the Python 3.x track. You have to love how flexible Python is to work with, and this scenario is also evident of that.

You can run BOTH Python 2.7.3 and 3.3.x on OSX together, at the same time, and without conflict (not even in terminal). To accomplish this, just follow these simple steps:

(optional) Python should be installed by default, but if you like you can install the 64 bit version of Python 2.7.3 b downloading here and running the dmg. Be sure you CONTROL-CLICK the installer package, and choose to open with Installer (this way even OSX 10.8 systems will have no issues). Follow all the default prompts.

1. You can verify your Python installation in Terminal by simply typing python, which will output the current version and prompt, and close with exit()

2. Now download the 64 bit version of Python 3.3.x from here and running the dmg. Be sure you CONTROL-CLICK the installer package, and choose to open with Installer (this way even OSX 10.8 systems will have no issues). Follow all the default prompts.

BAM… you now have Python 3.3.x installed.

3. Now open a new Terminal and type python3, and you will now have the prompt for Python 3.3.x running, and if you exit() and simply type python, you will still have Python 2.7.3.

Wow… that was simple, and a perfect demonstration just how easy it is to work with Python. And with your new Python 3 installation, grab yourself Django 1.5 beta and get testing this release.

Django 1.5 Beta Released

November 30th, 2012 0 Comments

Django is an amazingly powerful framework for Python developers. Unfortunately it’s been trapped in the 2.7.x branch of Python for some time now, which is what Django 1.4.x runs on. But alas, there is progress being made, and milestones being reach to port to the Python 3.x branch. At this time, Python is currently progressing at 3.3.x and forward, so this move is greatly needed and Django developers are ready.

On November 27, 2012, Django 1.5 has officially reached beta 1 release status. Here’s more information:

“As part of the Django 1.5 release process, today we’ve released Django 1.5 beta 1, a preview/testing package that gives a little taste of some of the new stuff coming in Django 1.5. As with all alpha and beta packages, this is not for production use, but if you’d like to try out some of the new goodies coming in 1.5, or if you’d like to pitch in and help us fix bugs before the final 1.5 release (due in December), feel free to grab a copy and give it a spin.

You can get a copy of the 1.5 beta package from our downloads page, and we recommend you read the release notes. Also, for the security conscious, signed MD5 and SHA1 checksums of the 1.5 alpha package are available.

Also, please note that Django 1.5 now requires a minimum of Python 2.6; Python 2.5 is no longer supported. Python 3.x releases, starting with Python 3.2, are experimentally supported in this release. For more information on Python 3 support, and the testing Django 1.5 will still need, see this blog post.”

Source: https://www.djangoproject.com/weblog/2012/nov/27/15-beta-1/

Download Here and follow the installation directions:


tar xzvf Django-1.5b1.tar.gz
cd Django-1.5b1
sudo python3 setup.py install

Don’t Forget… you need Python 3.3.x installed for this, but the great thing about Python, you can have both 2.7.x and 3.3.x installed at the same time… how cool is that? This way you can continue to develop with Django 1.4, while testing out and helping the testing of 1.5. Happy coding!

5 Things When Considering A Web Development Framework

May 10th, 2011 0 Comments

There are so many frameworks in web development that, to be frank, most developers find it confusing at times. Many developers are jumping around from one to another, if for no other reason, to add it to their resume. This article is designed to help cut through the confusion, and the bias online, and provide some thoughts that will help in your decisions.

This is a basic list of things to consider when choosing a framework:

1. Who’s behind the framework? Is it backed and endorsed by a large company, or perhaps a small group of developers looking to make a name, or otherwise just a new company looking to emerge? This should be very important in making a decision with not only the current framework you use with your projects, but even deeper, the platform and technology direction overall.

2. Is the code constantly being updated, tested, and maintained by a large professional team of developers? Technology changes, and so should the frameworks you use. It’s a constant pursuit to improve and debug that requires a lot of resources and man hours.

3. The code base should be of the highest quality, fully standardized and professional coding practices that will stand the test of time. It’s not about being a perfectionist, but it is about creating real solutions with solid products that have a reasonable life cycle.

4. A framework is only as good as it’s documentation and support. If it’s not easy to use, if it’s doesn’t produce better products, if it’s not speeding the time of development, then there is no point at all in even attempting to use it. This happens from great efforts to clearly document and to demonstrate common scenarios with written and video tutorials, etc.

5. What kind of work do you want? Do you want to work with professional organizations and long term contract work or jump from client to client with short turn around low level work? You must choose the technology path that meets your goals, and just the same, the framework goes nearly hand in hand with that direction.

Now that we know how you should choose, let’s look at the current options:

Tier 1:
Microsoft – .NET
JAVA – JSF

Tier 1 options are driven by large commercial for-profit companies with a large number of developers supporting and maintaining them, a large amount of money backing them, and are solid “enterprise worthy” directions. As a result, they are found as your tier 1 options.

Tier 2:
JAVA – Struts
JAVA – Spring
PHP – Zend Framework
Python – Django

Tier 2 options are also driven by quality companies with a large number of developers supporting them, and are solid directions that are considered “enterprise worthy” in many cases. Django may be a surprise by some, however, Python has proven to be a force to reckon with in the development community, and Django has played a large part in that movement. The other options in this tier should be no surprise.

Tier 3:
Ruby – Rails
PHP – Yii
PHP – Symfony
PHP – CodeIgniter

Tier 3 options are solid options, however, they are for the most part community driven by a smaller group of developers. Tier 3 options tend to be popular for a few years, then lose traction. They are also prone to complete overhauls where the framework is built again from the ground up to address issues and poor long term vision, which may break functionality of existing projects.

Tier 4:
If you’re not in the first 3 tiers, one should question whether you’re willing to roll the dice on such a development path for your projects. Sure, anyone can build their own framework, and many of the tier 4 and lower options are just not stable enough to guarantee their future.

Some may agree with the assessments, and of course, some will not as their favorite framework falls lower on the scale then expected. However, the vast majority of non-biased software/web/mobile architects will agree with these findings. With that said, there is no “wrong” framework to use provided it eases your development process, but if you’re looking for career paths and long term life cycles, you should consider these 5 points.