CodeInvestigator version 0.14.0 was released on August 6.
Required Python version: >= 2.6 and < 3.0
Changes:
Unicode characters.
They are handled better.
Performance changes:
The database is written more efficiently, so that recording
takes less time.
Performance tip: deleting ALL runs at the same time is
fastest; I then initialize the database.
CodeInvestigator is a tracing tool for Python programs.
Running a program through CodeInvestigator creates a recording.
Program flow, function calls, variable values and conditions are all
stored for every line the program executes.
The recording is then viewed with an interface consisting of the
code. The code can be clicked: A clicked variable displays its
value,
a clicked loop displays its iterations.
You read code, and have at your disposal all the run time details of
that code. A computerized desk check tool and another way to learn
about your program.
http://sourceforge.net/project/showfiles.php?group_id=183942
0.8.6 fixes some last minute compatibility issues with py.test 1.0
final, it also includes experimental glue code to be used just with
plain standard library unittest.py
about the latter see this post to testing in python:
http://lists.idyll.org/pipermail/testing-in-python/2009-July/002119.html
About OE jskit:
jskit contains infrastructure and in particular a py.test plugin to
enable running unit tests for JavaScript code inside browsers. The
plugin requires py.test 1.0
The approach also enables to write integration tests such that the
JavaScript code is tested against server-side Python code mocked as
necessary. Any server-side framework that can already be exposed through
WSGI can play.
More information and downloading at:
http://pypi.python.org/pypi/oejskit
including a changelog, documentation and the talk I gave at Europython.
jskit was initially developed by Open End AB and is released under the
MIT license.
In various incarnations it has been in use and useful at Open End for
more than a year, we are quite happy to share it.
Samuele Pedroni for Open End
________________________________________________________________________
ANNOUNCING
eGenix.com pyOpenSSL Distribution
Version 0.9.0-0.9.8k
An easy to install and use repackaged distribution
of the pyOpenSSL Python interface for OpenSSL -
available on Windows, Mac OS X and Unix platforms
This announcement is also available on our web-site for online reading:
http://www.egenix.com/company/news/eGenix-pyOpenSSL-Distribution-0.9.0-0.9.…
________________________________________________________________________
INTRODUCTION
The eGenix.com pyOpenSSL Distribution includes everything you need to
get started with SSL in Python. It comes with an easy to use installer
that includes the most recent OpenSSL library versions in pre-compiled
form.
pyOpenSSL is an open-source Python add-on (http://pyopenssl.sf.net/)
that allows writing SSL aware networking applications as well as
certificate management tools.
OpenSSL is an open-source implementation of the SSL protocol
(http://www.openssl.org/).
For more information, please see the product page:
http://www.egenix.com/products/python/pyOpenSSL/
________________________________________________________________________
NEWS
Due to popular demand, we've added .egg file versions for Windows
and Linux to the available download options. This should make things
easier for people using e.g. zc.buildout and other egg-file based
installers.
As always, binaries include both pyOpenSSL and the necessary OpenSSL
libraries.
________________________________________________________________________
DOWNLOADS
The download archives and instructions for installing the package can
be found at:
http://www.egenix.com/products/python/pyOpenSSL/
________________________________________________________________________
UPGRADING
Before installing this version of pyOpenSSL, please make sure that
you uninstall any previously installed pyOpenSSL version. Otherwise,
you could end up not using the included OpenSSL libs.
_______________________________________________________________________
SUPPORT
Commercial support for these packages is available from eGenix.com.
Please see
http://www.egenix.com/services/support/
for details about our support offerings.
Enjoy,
--
Marc-Andre Lemburg
eGenix.com
Professional Python Services directly from the Source (#1, Aug 04 2009)
>>> Python/Zope Consulting and Support ... http://www.egenix.com/
>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
________________________________________________________________________
::: Try our new mxODBC.Connect Python Database Interface for free ! ::::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
Registered at Amtsgericht Duesseldorf: HRB 46611
http://www.egenix.com/company/contact/
Hi all,
i am happy to announce pylib/py.test 1.0.0, a MIT-licensed
library geared towards advanced testing and elastic distributed
programming with Python. It features the mature cross-project
py.test automated testing tool with many new features, aiming to:
* allow writing zero-boilerplate automated tests in Python
* offer strong debugging and reporting of test failures
* rapidly run and ad-hoc distribute tests to multiple CPUs/platforms
* support unit-, functional and integration testing
* be easy to extend and tackle growing testing needs,
(current prime example oejskit, a live-browser javascript
unittesting 3rd party plugin)
Please check things out at: http://pytest.org or read the blogged
release announcement:
http://tetamap.wordpress.com/2009/08/04/pylib-1-0-0
or read on for some ...
Distinctive new features shipping with py.test 1.0.0
------------------------------------------------------
For those already knowing about the older 0.9.2 release or
being experienced with other testing approaches i'll try to
give a summary of the distinctive testing features
shipping with 1.0.0:
* test function arguments ("funcargs"): With this, python test
functions can name arguments and one writes factory functions to
provide instances for such "fixture" arguments. This page
http://codespeak.net/py/dist/test/funcargs.html
contains reference info and tutorial examples.
Test function arguments also allow for natural test parametrization -
one provides several different argument values,
no changes to the test function needed, no magic "yield" for
generating tests anymore - although 1.0 still allows them and
of course still supports traditional xUnit-style setup_module/class/function
or (new) direct runs of unittest.TestCase style tests.
* distributed testing: distributing test runs among Linux/OSX/Windows
hosts and across python-2.4 till python-2.6 interpreters
works reasonably stable now. This means that you can easily
iron out test-module/function specific problems across a
variety of platforms, accelerating the change & test feedback cycle.
* xfail: a new way to mark tests as "expected to fail" which
means they run normally but are reported/counted specially.
This "xfail" mark is meant to mark missing / wrong implementation
rather than missing dependencies / wrong platforms for which one
uses "skip". Especially for larger test suites making
this distinction is very helpful.
* IO-capturing: output of test functions is captured per-test,
by default including any output from sub processes.
This works on all platforms and also (now) interacts well
with the logging module without importing/using it itself so
there are no interferences.
* pastebin: new command line option "--pastebin" to send your test
session output or individual test failures to the Pocoo pastebin
service and prints out URLs. Convenient for quick IRC/messaging
communication.
* plugins: it is now easy to write plugins by implementing one
or more of the 37 hooks which py.test calls to implement
the testing process. There are many examples, among them
the "oejskit" plugin which integrates testing of javascript
code in real-life browsers into a regular test run.
Apart from such separately distributed "cross-project" plugins
you can also write per-project plugins/extensions that lives
with your testing code.
cheers & have fun,
holger
--
Metaprogramming, Python, Testing: http://tetamap.wordpress.com
Python, PyPy, pytest contracting: http://merlinux.eu
RunPON 0.3 can be downloaded from here:
http://erlug.linux.it/~da/soft/runpon/http://bitbucket.org/alberanid/runpon/ (mercurial repository)
RunPON is a small Python program useful to run the pon/poff scripts.
It shows the elapsed connection time and periodically checks if a given
network interface is still active.
It can run as a stand-alone application (with a status icon in the tray)
or as a Gnome panel applet (and compatible panels).
Obviously, modifying its configuration, it can run any program you like.
It's still under heavy development, and so far its configuration is
still hard-coded. If you want to help, please contact me at:
da (AT) erlug.linux.it
--
Davide Alberani <alberanid(a)libero.it> [GPG KeyID: 0x465BFD47]
http://erlug.linux.it/~da/
ABOUT THE MODULE
================
AwstatsReader is an attempt at a pythonic interface to AWStats data
cache
files. Using it, you can access year, month, and individual data points
via dictionary-like accessors.
Download here: http://azariah.com/open_source.html
ABOUT THE AUTHOR
================
Joshua Kugler (joshua(a)azariah.com) is a programmer and system
administrator
with over 10 years of industry experience. He is currently looking for
a
job. Happen to have one you could offer him? :)
Resume at: http://jjncj.com/papers/KuglerAll.pdf
DISCLAIMER
==========
This is a "release early, release often" release, codnamed Joshua-hopes-
somebody-downloads-this-and-likes-code-quality-and-hires-him.
This is an early release...probably pre-alpha. There are no tests yet
(haven't
generated cache files I can release publically), not much documentation,
and the interface may change (but I hope not too much).
And I haven't even put this in a public repository, as the name might
(but
probably won't) change.
I wrote this via examples from an AWStats cache file, so I'm sure there
are
sections for which I do not have definitions. If you would send me
those
sections, I'll be sure to add them.
The error handling is probably a little light. Certainly could be
improved.
Right now, this will parse and display cache files from AWStats 6.5.
I've
not
tested other versions yet, as 6.5 is the only version I've had access to
so
far.
INSTALLATION
============
See INSTALL
LICENSE
=======
See COPYING
EXAMPLE
=======
import AwstatsReader
obj =
AwstatsReader.AwstatsReader('/path/to/awstats_logs', 'example.com')
print obj[2007]
print obj[2008][6]
m = obj[2009][7]
print m['general']
# Access like a dictionary...
print m['general']['LastLine']
#...or like an object attribute
print m['general'].LastLine
print m.general.LastLine
FEEDBACK
========
Please send questions/comments/suggestions to awstatsreader(a)azariah.com
For now, you can find the latest version here:
http://azariah.com/open_source.html
The ninth PyWeek challenge will run between:
Sunday 30th August to Sunday 6th September (00:00UTC to 00:00UTC)
The PyWeek challenge invites entrants to write a game in one week from
scratch either as an individual or in a team. Entries must be developed
in Python, during the challenge, and must incorporate some theme chosen
at the start of the challenge.
REGISTRATION IS NOW OPEN --
Visit the challenge website to sign up, join discussions in the
message board or read the timetable and rules:
http://www.pyweek.org/9/
PLANNING FOR THE CHALLENGE --
Make sure you have working versions of the libraries you're going to
use.
The rules page has a list of libraries and other resources.
Make sure you can build packages to submit as your final submission (if
you're going to use py2exe, make sure you know how to use it and that it
works).
If you don't have access to Linux, Windows or a Mac to test on, contact
friends, family or other competitors to find someone who is able to test
for you.