PUBLIC MARKS with tags package & python

A simple tool to backup your Github and Bitbucket repositories, which might save in a massive crash situation...

Easy Install is a python module (easy_install) bundled with setuptools that lets you automatically download, build, install, and manage Python packages.

The officially recommended way to create .deb packages for the maemo platform is to use dpkg-buildpackage within Scratchbox. For me, Scratchbox is a pain to install for two main reasons. First, there is no RPM package of the scratchbox environment, so apparently I need to run some scripts as root, let my system get a little messier, which I am not willing to do. Second, the docs advise to turn off SELinux in order to get the Scratchbox environment to work, which again I am not keen to do.

Veusz is a scientific plotting package written in Python. It uses PyQt (Wiki) and Numpy. Veusz is designed to produce publication-ready Postscript output.

The Python Package Index is a repository of software for the Python programming language.

ctypes is an advanced ffi (Foreign Function Interface) package for Python 2.3 and higher. In Python 2.5 it is already included.

VPython is a package that includes: * the Python programming language * the IDLE interactive development environment * "Visual", a Python module that offers real-time 3D output, and is easily usable by novice programmers * "Numeric",

"Eggs are to Pythons as Jars are to Java..." Python Eggs are zipfiles using the .egg extension, that support including data and C extensions as well as Python code. They can be used with Python 2.3 and up, and can be built using the setuptools package (see the Python CVS sandbox for source code, or the EasyInstall page for current installation instructions). Once the implementation is far enough along, we plan to propose it for inclusion with the standard library beginning in Python 2.5. The primary benefits of Python Eggs are: * They enable tools like the "Easy Install" Python package manager (NEW!) * They are a "zero installation" format for a Python package; no build or install step is required, just put them on PYTHONPATH or sys.path and use them * They can include package metadata, such as the other eggs they depend on * They allow "namespace packages" (packages that just contain other packages) to be split into separate distributions (e.g. zope.*, twisted.*, peak.* packages can be distributed as separate eggs, unlike normal packages which must always be placed under the same parent directory. This allows what are now huge monolithic packages to be distributed as separate components.) * They allow applications or libraries to specify the needed version of a library, so that you can e.g. require("Twisted-Internet>=2.0") before doing an import twisted.internet. There are also other benefits that may come from having a standardized format, similar to the benefits of Java's "jar" format.