Programmer blog

One of main features and troubles for Django projects is the Django version you are using. Example for this would be the occasion of starting project for Django 1.4.x version. Trying to run it under Django 1.7.x would lead to various troubles, counting template changes, misconfiguration errors and so on. Solution is to use virtual environment. The tool for this is called Virtualenv . It is a wrapper for a python interpreter. It enables you to have multiple versions of python packages that run independently. The Virtualenv creates you a standalone environment. Basically it copies and keeps a system Python of yours in a specified directory. All the python packages will be installed there. (In case you have not forgot to activate it first, of course) Lets get started then. We need Virtualenv itself for the first. There are many ways to install it depending on your system . Most obvious to use pip. Your installation command will look something like that: pip install virtualenv Thi...

I have had a problem with compiling Pillow recently. the error was with Pillow/Pil compilation. pillow install error clang: error: unknown argument: '-mno-fused-madd' [-Wunused-command-line-argument-hard-error- in -future] Apple updated command line tools. So the cc command was updated too. $ gcc --version Configured with : --prefix= /Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 Apple LLVM version 5.1 (clang- 503.0 . 38 ) (based on LLVM 3.4 svn) Target: x86_64-apple-darwin13. 1.0 Thread model: posix The bug is in GCC. It is quite serious because those flags support will be dropped in future. Fortunately there is a worakround for now: export ARCHFLAGS= "-Wno-error=unused-command-line-argument-hard-error-in-future" It works for Pillow 2.4.0 and I can compile it with Apple LLVM 5.1 (That is current now), as of Xcode 5.1. Hope my findings will help someone.

I'm a fan of IDE's. Also I'm a fan of GUI's. I also use console where needed, but why waist time typing commands when you can just point and click. I've been using Eclipse + PyDev for almost a year and recently switched to PyCharm. Why I prefer PyCharm: - Template Debugging. (you can set a normal breakpoints in templates) - Easy Virtualenv connection. (Set an interpreter from your virtualenv and you're ready to roll) - Has excellent set of most common CVS integrations (Git, SVN, Redmine, etc...) - Has looots of tiny tasty things for coding and proper code highlighting over JS and HTML out of the box) - Has proper and shiny themes out of the box. So I'm a blind minded blond, it seems now. But design of this IDE is really attractive IMHO :) - OH and it's quite quick and has ALL the functions I need. Here is a brief instruction to setup PyCharm IDE to work with my typical Django project. 1.  First thing you need is a PyCharm installation. Y...

Like lots of Apple fans around the world I've finally decided to upgrade my OS to Lion release. I have bought a new laptop and it was the case. I've waited for a weekend to prepared myself for sex. And it was it. Now I want to share my experience with you guys. For you not to spend to much time on those issues, I've did. Anyway what I'm usually using is a Fresh 2.7 Python , Django , PIL , virtualenv and many many minor tools which exceed scopes of this article. I also use Eclipse IDE for Python Dev. So all this I had to install and make spinning till monday. If anybody tells me that Macs do not have good tools for this. He will not be right. Maybe there some itches and scratches of head about: "Why is not those things working" or "Why do they work not as preferred". But there always is a good "Googled" decision to handle that. Anyway lets go to installing stuff. Short brief Plan of out work: 1. Install Apple Development SDK + ...

Hi! Many people use Virtualenv. It has become common pattern now days. I like Virtualenv but it has no debugger. You can run ' python manage.py runserver ' but it will newer help you see somthing like runtime variables and code flow. I like PyDev  debugger. It helps me a lot. Anyway I faced a problem recently. My employer wants me to run code at virtualenv. I needed to download and run project. I made it creating New virtualenv called 'venv' inside a project folder. Command is: virtualenv - - no - site - packages venv It will create dir 'venv' inside current directory. So you should be at where you need to store your virtualenv (your project directory for e.g.). --no-site-packeges  parameter says that your new virtual environment will not have packages installed in system. It's a must if you want to avoid collisions with newer versions of code. Now we have a dir inside your project called venv  containing our separated python environment. Lets activ...

Prologue Hi! Let's talk about Django ways to code. First you have to have environment installed for work with Django. Today I'll try to show you my way of using virtual environment ( python virtualenv ). It's ok to handle package dependencies in Django apps by simply manually putting libraries, are in need for your project, into project PYTHONPATH. It's an easy way to do it. BUT what if you would like to make another project with this environment (e.g. the same modules, plugins or app's set)... You will have to add all those modules to your new project. Another issue that if would like to code for existing project, like for e.g. open someone's work and add some modules to it.  Virtualenv is a newly fashioned package which aims to combine the best features of a workingenv with a virtual Python install . Also you can say that it is a tool to create isolated in a sandbox Python environments. So... This article is about how to set up, run and conn...

Let's talk about common programming practice. You love to code yourself. Everyday you write tons of code. Making lots of common tasks is interesting and challenging. No? A-ha! You love plugins too! :) I'm making a startup. Everyday there are some ideas coming to my head. Some are easy to implement, some are not, but I often download tons of plugins. There are lots of ways to use plugins without installing them to main system. Python virtualenv is easy and common to use for this purposes. Soon I'll write an article about it too. But the main problem of Python Virtualenv is it's complexity. You basically need to install something, make an environment and so on... What if you just need to implement nice and easy "Django way". Here direct copy comes in mind. It's the easiest way, as for me. Basic concept is:    - download plugin (be it in egg, zip, tar.gz or any other format)    - unpack it     - copy to django app dir ...