Document Management Software is a little vague. What do you want it
to do? In general though, when someone says content management and
Python, the general response is Zope, usually with Plone on top.
--
http://mail.python.org/mailman/listinfo/python-list
Giles, you keep mentioning syntax errors as the (/a) cause of the
problem. I suggest you avoid such problems, so that the import sethook
approach, et al. will actually work. The easiest thing to do is to run
PyChecker on your script prior to executing it. PyChecker will catch
your syntax errors
As Konstantin alludes, your request is not specified clearly enough.
In all-caps you write APPLICATION MONITORING SYSTEM, yet your only
use-case is it lets the it employee enter the name of the application
and gives him all the details about it, where the details are ... a
bunch of fields that
Reasonable enough. As per Mike's suggestion below, building a few web
pages to document the apps is a good start. To expand on that idea,
you could write daemons/cron jobs, perhaps in Python if Python runs on
OS/400, that monitor each app's status and log that information to the
web server. You
.
Regards,
--
Marc-Andre Lemburg
eGenix.com
Thank you very much for your patience and insight.
Cheers,
---Peter Herndon
--
http://mail.python.org/mailman/listinfo/python-list
:) Knock away, as my info isn't scientific anyway. In my case, ASA is
*not* local. The db is running on a 500MHz x 2 server with 768MB RAM,
over 100BaseT connection. That same server is also running the MSSQL
instance, and IIS.
Running your benchmark, I ran into a couple of interesting points.
I switched around the order, both in the actual application and in my
tests as replied to Francois Lepoutre above. Results were consistent,
after the first run of any given test, which unsurprisingly took a bit
longer.
--
http://mail.python.org/mailman/listinfo/python-list
possible
solutions to find the one that best fits his needs.
---Peter Herndon
On 4/15/05, M.-A. Lemburg [EMAIL PROTECTED] wrote:
Peter Herndon wrote:
Another option is adodbapi, which in my experience is much faster than
mx.ODBC.
Much faster ?
See
http://www.microsoft.com/technet
If you have three different implementations, and can read all three of
them well enough to understand the code, use all three.
If you are going to port software from one language to another, and
want to reimplement it properly in your target language, you won't be
porting word-for-word anyway.
