Get a Python Package Version
Part of maintaining a Django-based application like MDN's kuma is ensuring Python packages are up to date. I was recently testing an upgrade on a remote system and needed to ensure that a given Python package was at the version number it should be. Here's how I retrieved the package version:
import nose # Nose is a test utility. Replace with your desired package here.
nose.__version__
# Output: 0.3.1
The __version__ property returns the exact version number for a Python package. Some Python packages use a VERSION property as well, but __version__ should be the most reliable.
![fetch API]()
One of the worst kept secrets about AJAX on the web is that the underlying API for it, XMLHttpRequest, wasn't really made for what we've been using it for. We've done well to create elegant APIs around XHR but we know we can do better. Our effort to...
![Create Namespaced Classes with MooTools]()
MooTools has always gotten a bit of grief for not inherently using and standardizing namespaced-based JavaScript classes like the Dojo Toolkit does. Many developers create their classes as globals which is generally frowned up. I mostly disagree with that stance, but each to their own. In any event...
![Create a Custom “:selected” Pseudo Selector in MooTools]()
![Translate Content with the Google Translate API and JavaScript]()
Note: For this tutorial, I'm using version1 of the Google Translate API. A newer REST-based version is available.
In an ideal world, all websites would have a feature that allowed the user to translate a website into their native language (or even more ideally, translation would be...
Every once in a while a package might not define either
VERSIONor__version__, since they’re conventions, not required. You can always get the installed version with pkg_resources, though:>>> import pkg_resources >>> pkg_resources.get_distribution("PIL").version '1.1.7'@James,
__version__is recommended by PEP 396