transAuction/0.1.1
------------------
A small database program for sellers to track transactions on online
auctions.
A small database program for sellers to track transactions on online
auctions.
URL: transacution.sourceforge.net
License: LGPL
Platform: Win32, Linux
Gui: Tkinter
Categories: Applications, Personal Database
Craig Hurley (sobit(a)impudence.net)
--
<a href="transacution.sourceforge.net">transAuction/0.1.1</a> -- A small
database program for sellers to track transactions on online auctions.
Release 0.6.3 fixes Linux/GTK bugs discovered after the 0.6.2 release.
Support was also added for localized resource files to simplify
internationalization of PythonCard apps. A FAQ, tutorial, and updated
documentation describing the framework was added to the main web site.
All the information you need about PythonCard can be found on the project
web page at: http://pythoncard.sourceforge.net/
You can download the latest release at:
http://sourceforge.net/project/showfiles.php?group_id=19015
For a list of the samples that have been built with PythonCard and some
screenshots of them in action go to:
http://pythoncard.sourceforge.net/samples.html A description of each sample
is included in the readme.txt file in each sample directory.
The kind people at SourceForge host the project:
http://sourceforge.net/projects/pythoncard/
If you want to get involved the main contact point is the Mailing list:
http://lists.sourceforge.net/lists/listinfo/pythoncard-users
PythonCard requires Python 2.1.x or later and wxPython 2.3.2.1 or later and
runs on every platform those are available for. wxPython can be downloaded
at http://www.wxpython.org/
ka
---
Kevin Altis
altis(a)semi-retired.com
We plan to have a Birds of a Feather (BOF) session at the Python 10
Conference, http://python10.org, on a Python distributed transaction
framework.
The Zope object database, ZODB, includes frameworks
for persistence and transaction management. These frameworks
depend very little on the rest of ZODB and will be factored
out of ZODB and made into separate packages in the next generation
of ZODB, ZODB 4.
We have experience using the transaction framework
with other persistence mechanisms in Zope, including relational
databases and the light-weight directory access protocol, LDAP.
This allows distributed transactions to be coordinated among
multiple database systems. If a transaction is committed or rolled
back, the commit or rollback happens for each of the participating
databases. This is very useful. It would be useful to make this
capability available to other Python applications.
In particular, it would be worthwhile to explore integrating
distributed transactions with the Python database API to make it
easier to coordinate among multiple databases and to better support
distributed transactions in the Python database API, for example by
including interfaces to underlying distributed-transaction APIs not
currently exposed by the Python database API.
We'd like to kick off an effort to design a transaction framework
to encompass ZODB, relational databases, and other persistence
systems.
The talk BOF begin with a presentation of the ZODB Transaction
framework.
The BOF will take place at lunch time on Tuesday, February 5.
Jim
--
Jim Fulton mailto:jim@zope.com Python Powered!
CTO (888) 344-4332 http://www.python.org
Zope Corporation http://www.zope.comhttp://www.zope.org
We plan to have a Birds of a Feather (BOF) session at the Python 10
Conference, http://python10.org, on a Python persistence framework.
The Zope object database, ZODB, includes frameworks
for persistence and transaction management. These frameworks
depend very little on the rest of ZODB and will be factored
out of ZODB and made into separate packages in the next generation
of ZODB, ZODB 4.
The ZODB persistence framework provides significant benefits to
Python programmers:
- Objects are automatically loaded and stored. The programmer
doesn't have to keep tack of when objects have been
modified. The objects track modification and notify the
transaction manager of changes. The transaction manager
coordinates storing data. Data are loaded when needed, with
loads triggered by access from other objects.
- An object cache automates moving data out of memory when no
longer needed. A cache invalidation protocol helps to keep object
consistence across multiple applications or application
threads.
We would like to see these benefits made available for other
databases. We'd especially like to see a persistence framework
using relational databases, reusing object-relational mapping
efforts, such as MiddleKit and others.
We'd like to kick off an effort to design a persistence framework
to encompass ZODB, relational databases, and other persistence
systems.
The BOF will begin with a presentation of the ZODB Persistence
framework.
The BOF will take place the evening of Wednesday, February 6.
Jim
--
Jim Fulton mailto:jim@zope.com Python Powered!
CTO (888) 344-4332 http://www.python.org
Zope Corporation http://www.zope.comhttp://www.zope.org
I'm please to announce the first official release of StandaloneZODB,
the Python object persistency system also known as the Z Object
Database. ZODB is the object-oriented database underlying Zope; the
StandaloneZODB project's goal is to provide those same facilities to
non-Zope related Python applications.
Today we are releasing StandaloneZODB 1.0 release candidate 1. We
expect to release the final version on 1-Feb-2002.
StandaloneZODB is based on the same code as the ZODB in Zope, albeit
on a separate release branch. Its inspiration comes from Andrew
Kuchling's StandaloneZODB project on SourceForge. While there are
still some differences, the Standalone 1.0 release is the first on the
path toward convergence. Subsequent releases should complete the
merge of Andrew's and Zope Corporation's packages.
The StandaloneZODB release includes the following components:
- Core ZODB, including the persistence machinery
- Standard storages such as FileStorage
- Supporting modules such as ExtensionClass
- The persistent BTrees modules
- ZEO
- Experimental Berkeley storages
- Some documentation <wink>
See the README file for details on building and installing
StandaloneZODB. For details on using ZODB, see Andrew's included user
guide.
StandaloneZODB 1.0c1 is released under the ZPL 2.0. It should be
compatible with all Python versions from Python 2.1 to Python 2.2. It
may or may not work with versions earlier than Python 2.1.
Download StandaloneZODB-1.0c1.tgz from:
http://www.zope.org/Products/StandaloneZODB
and visit the StandaloneZODB Wiki page at:
http://www.zope.org/Wikis/ZODB/StandaloneZODB
See also:
http://www.zope.org/Wikis/ZODB/FrontPage
for more information about our long-range ZODB plans.
Enjoy,
-Barry
Barry A. Warsaw
Zope Corporation, Pythonlabs
barry(a)zope.com
You can get the latest Pyro version (2.4) at http://pyro.sourceforge.net
What's new:
Event server fixes, including new example
Bug fixes in core and examples
Oneway method call, including callback example
Preliminary Jython compatibility (client-only).
Documentation updates.
What is Pyro?
Pyro is an acronym for PYthon Remote Objects. It is a basic Distributed
Object Technology system written entirely in Python.
It is extremely easy to implement a distributed system with Pyro, because
all network communication code is abstracted and hidden from
your application. You just get a remote Python object and invoke methods
on the object on the other machine.
Pyro offers you a Name Server, an Event Service, mobile objects, remote
exceptions, dynamic proxies, remote attribute access, automatic
reconnection, a detailed manual, and many examples to get you started
right away.
Irmen de Jong
The 'arrayfrombuffer' package features support for Numerical Python
arrays whose contents are stored in buffer objects, including
memory-mapped files. This has the following advantages:
- loading your array from a file is easy --- a module import and a
single function call --- and doesn't use excessive amounts of
memory.
- loading your array is quick; it doesn't need to be copied from one
part of memory to another in order to be loaded.
- your array gets demand-loaded; parts you aren't using don't need to
be in memory or in swap.
- under memory-pressure conditions, your array doesn't use up swap,
and parts of it you haven't modified can be evicted from RAM without
the need for a disk write
- your arrays can be bigger than your physical memory
- when you modify your array, only the parts you modify get written
back out to disk
This is something that's been requested on the Numpy list a few times
a year since 1999.
arrayfrombuffer lives at
http://pobox.com/~kragen/sw/arrayfrombuffer/
The current version is version 2; it is released under the X11 license
(the BSD license without the advertising clause).
<kragen(a)pobox.com>
<P><A
HREF="http://pobox.com/~kragen/sw/arrayfrombuffer/">arrayfrombuffer
2</A> - creates Numeric arrays from memory-mapped files. (23-Jan-02)
Roundup 0.4.0 - an issue tracking system
If you are upgrading please read MIGRATION.txt.
Roundup requires python 2.1.1 for correct operation. Support for dumbdbm
requires python 2.1.2 or 2.2.
Big stuff in this release:
- Use of transactions to prevent partial data commits
- Zope Product front-end
- Message threading
- Nicer, more consistent change message generation
- More bug fixes and unit tests
- Much, much more: see the release info for details.
Source and documentation is available at the website:
http://roundup.sourceforge.net/
Release Info (including CHANGES since 0.3.0):
http://sourceforge.net/project/shownotes.php?release_id=71660
Mailing lists - the place to ask questions:
http://sourceforge.net/mail/?group_id=31577
About Roundup
=============
Roundup is a simple-to-use and -install issue-tracking system with
command-line, web and e-mail interfaces. It is based on the winning design
from Ka-Ping Yee in the Software Carpentry "Track" design competition.
Note: Ping is not responsible for this project. The contact for this project
is richard(a)users.sourceforge.net.
Roundup manages a number of issues (with flexible properties such as
"description", "priority", and so on) and provides the ability to
(a) submit new issues,
(b) find and edit existing issues, and
(c) discuss issues with other participants.
The system will facilitate communication among the participants by managing
discussions and notifying interested parties when issues are edited. One of
the major design goals for Roundup that it be simple to get going. Roundup
is therefore usable "out of the box" with any python 2.0+ installation. It
doesn't even need to be "installed" to be operational, though a
disutils-based install script is provided.
It comes with two issue tracker templates and three database back-ends.