Celery - Distributed Task Queue — Celery v2.0.0 (stable) documentation. Working with virtualenv — Arthur Koziel. SingleFileExecutable - py2exe.org. The "extending" example that comes with Py2Exe shows a nicely integrated approach for using Inno Setup to create single file executables.
This example isn't so nicely integrated, but it uses NSIS instead of Inno Setup in case you prefer that. Drop a copy of this script in your source directory alongside setup.py and modify the first two lines. The first points to py2exe's output directory and the second is the name of the executable in that directory as well as the name of the executable that NSIS will create. You can also select compression behavior - NSIS' LZMA compression (based on 7-Zip) is pretty impressive - wxPython applications start at about 3.5 - 4 MB instead of 10 - 12 MB. Compression may slow startup time for your executable somewhat. Once you've built your executable with py2exe, then compile the installer script with NSIS and an executable will be created in the same folder as the script. Pycron. Pycron Instructions A good introductory article about pycron can be found at "This article will discuss using a Cron type system, as used on Unix and Linux systems, to bring the flexibility, scalability and a need for more out of a task automation tool, to the Win32 environment.
" Juno: A Lightweight and Simple Web Framework. EasyExtend. Abstract EasyExtend is a constructive approach to extend the Python language using pure Python.
EasyExtend is developed as a Python framework depending only on tools provided by the CPython interpreter suite ( compiler ) and standard library as well as some pieces of code borrowed from the PyPy project. Opposite to toolkits for writing extension modules in C ( or RPython in future ) the EasyExtend framework is dedicated to extend the language itself by adding new grammar rules and transformation of parse trees. Acting directly on the nodes of syntax trees makes EasyExtend safe and extensible.
Moreover the parser and the transformations are considerably fast. Overview 0. How to find the source tree and what it contains. 1. Explains the very basics of EE - the world of CST surgery. 2. Ruby/Python Documentation. Python packaging: a few observations, cabal for a solution ? « Nothing to say. The python packaging situation has been causing quite some controversy for some time.
The venerable distutils has been augmented with setuptools, zc.buildout, pip, yolk and what not. Some people praise those tools, some other despise them; in particular, discussion about setuptools keeps coming up in the python community, and almost every time, the discussion goes nowhere, because what some people consider broken is a feature for the other. It seems to me that the conclusion of those discussions is obvious: no tool can make everybody happy, so there has to be a system such as different tools can be used for different usage, without intefering with each other. The solution is to agree on common format and data/metadata, so that people can build on it and communicate each other. You can find a lot of information on people who like setuptools/eggs, and their rationale for it. Distutils limitation Most of those tools are built on top of distutils, which is a first problem. College: Computer Science: PIL (Python Imaging Library)
PIL (aka the Python Imaging Library) is used in many of the Carleton College Intro CS courses.
NOTE: PIL is NOT available for Python 3. This page contains installation instructions for Python 2.x: WINDOWS XP and Vista and 7: The latest downloads of PIL for windows can be found at the current release: click on the downloaded executable. And that will install PIL. Enthought Download the installer: the installer and follow the instructionsRun Canopy onceYour python shell should now be using Enthought's version of python.
If you want to investigate other options talk to Mike Tie, or look at MacPorts If you have any questions about installing PIL for Windows, Mac, or any other operating system, please contact Michael Tie (email@example.com x4067) Python Memory Management. Tracing Python memory leaks. Python's getattr : orestis.gr. An interesting question So, yesterday I was asked an interesting question: Int: Are you familiar with Python's getattr?
Me: Um, yes? Interviewer clarifies what it's all about Int: So I now want you to implement __getattr__ in such a way that when a method is called with the prefix print it'll print it's name before calling it. Before that, we had a discussion about decorators, where I created a decorator called printme: def printme(func): def decorated(*args, **kwargs): print func.func_name #well, it was "print func", but now I know better :) return func(*args,**kwargs) return decorated So after a bit of confusion (writing code like that in a piece of paper with two pairs of eyes looking at you can be tricky), I ended up with something that may have looked like this: Can you spot the error?
Well, we didn't have access to a console, so we didn't. >>> f = Foo() >>> f.hi() Hello! So far, so good. >>> f.blah() Traceback (most recent call last): File "<stdin>", line 1, in ? So, how does it work? Step by step: Compiling extensions with MS Visual C++ Toolkit 2003 - msvccompiler-patch.txt (0/1)