[Zope-Checkins] SVN: Zope/trunk/ Updated documentation to new version number.
Log message for revision 100457: Updated documentation to new version number. Changed: U Zope/trunk/doc/CHANGES.rst U Zope/trunk/doc/WHATSNEW.rst U Zope/trunk/doc/WINDOWS.rst D Zope/trunk/doc/ZOPE3.rst U Zope/trunk/doc/conf.py U Zope/trunk/doc/index.rst U Zope/trunk/inst/WinBuilders/mk/zope.mk U Zope/trunk/inst/generate_index.py U Zope/trunk/inst/versions.py U Zope/trunk/setup.py -=- Modified: Zope/trunk/doc/CHANGES.rst === --- Zope/trunk/doc/CHANGES.rst 2009-05-27 12:22:59 UTC (rev 100456) +++ Zope/trunk/doc/CHANGES.rst 2009-05-27 12:45:04 UTC (rev 100457) @@ -2,8 +2,8 @@ = This file contains change information for the current Zope release. -Change information for previous versions of Zope can be found in the -file HISTORY.txt. +Change information for previous versions of Zope can be found at +http://docs.zope.org/zope2/releases/. Trunk (unreleased) -- @@ -11,460 +11,12 @@ Restructuring + -- Removed all use of ``zope.app.pagetemplate`` by cloning / simplifying - client code. +* Updated documentation to new version number. -- Use ``zope.pagetemplate.engine`` instead of ``zope.app.pagetemplate.engine``. - (update to versions 3.5.0 and 3.7.0, respectively, along with version 3.8.1 - of ``zope.app.publisher``). - -- Use ``IBrowserView`` interface from ``zope.browser.interfaces``, rather than - ``zope.publisher.interfaces.browser``. - -- Use ``IAdding`` interface from ``zope.browser.interfaces``, rather than - ``zope.app.container``. - -- No longer depend on ``zope.app.appsetup``; use the event implementations - from ``zope.processlifetime`` instead. - Features Added ++ -- zExceptions.convertExceptionType: new API, breaking out conversion of - exception names to exception types from 'upgradeException'. -- Launchpad #374719: introducing new ZPublisher events: - PubStart, PubSuccess, PubFailure, PubAfterTraversal and PubBeforeCommit. - -- Testing.ZopeTestCase: Include a copy of ZODB.tests.warnhook to silence - a DeprecationWarning under Python 2.6. - -- Updated packages: - - * python-gettext 1.0 - * pytz 2009g - * zope.app.applicationcontrol = 3.5.0 - * zope.app.appsetup 3.11 - * zope.app.component 3.8.2 - * zope.app.container 3.8.0 - * zope.app.form 3.8.0 - * zope.app.http 3.6.0 - * zope.app.interface 3.5.0 - * zope.app.pagetemplate 3.6.0 - * zope.app.publication 3.7.0 - * zope.app.publisher 3.8.0 - * zope.browser 1.2 - * zope.component 3.7.0 - * zope.componentvocabulary 1.0 - * zope.container 3.8.2 - * zope.formlib 3.6.0 - * zope.lifecycleevent 3.5.2 - * zope.location 3.5.4 - * zope.processlifetime 1.0 - * zope.publisher 3.8.0 - * zope.security 3.7.0 - * zope.testing 3.7.4 - * zope.traversing 3.7.0 - Bugs Fixed ++ -- Launchpad #374729: Encoding cookie values to avoid issues with - firewalls and security proxies. - -- Launchpad #373583: ZODBMountPoint - fixed broken mount support and - extended the test suite. - -- Launchpad #373621: catching and logging exceptions that could cause - leaking of worker threads. - -- Launchpad #373577: setting up standard logging earlier within the startup - phase for improving the analysis of startup errors. - -- Launchpad #373601: abort transaction before connection close in order to - prevent connection leaks in case of persistent changes after the main - transaction is closed. - -- Fix BBB regression which prevented setting browser ID cookies from - browser ID managers created before the ``HTTPOnly`` feature landed. - https://bugs.launchpad.net/bugs/374816 - -- RESPONSE.handle_errors was wrongly set (to debug, should have been - ``not debug``). Also, the check for exception constructor arguments - didn't account for exceptions that didn't override the ``__init__`` - (which are most of them). The combination of those two problems - caused the ``standard_error_message`` not to be called. Fixes - https://bugs.launchpad.net/zope2/+bug/372632 . - -- DocumentTemplate.DT_Raise: use new 'zExceptions.convertExceptionType' - API to allow raising non-builtin exceptions. - Fixes https://bugs.launchpad.net/zope2/+bug/372629 , which prevented - viewing the Try tab of a script with no parameters. - -Zope 2.12.0b1 (2009/05/06) --- - -Restructuring -+ - -- No longer depend on ``zope.app.locales``. Zope2 uses almost none of the - translations provided in the package and is not required for most projects. - The decision to include locales is left to the application developer now. - -- Removed the dependency on ``zope.app.testing`` in favor of providing a more - minimal placeless setup as part of ZopeTestCase for our own tests. - -- updated to ZODB 3.9.0b1 - -Features Added -++ -- zExceptions.convertExceptionType: new API, breaking out conversion of - exception names to exception types from
[Zope-Checkins] SVN: Zope/trunk/ Include zope.app.cache 3.6.0 in the KGS
Log message for revision 100477: Include zope.app.cache 3.6.0 in the KGS Changed: U Zope/trunk/doc/CHANGES.rst U Zope/trunk/versions.cfg -=- Modified: Zope/trunk/doc/CHANGES.rst === --- Zope/trunk/doc/CHANGES.rst 2009-05-27 16:14:22 UTC (rev 100476) +++ Zope/trunk/doc/CHANGES.rst 2009-05-27 16:16:23 UTC (rev 100477) @@ -16,7 +16,10 @@ Features Added ++ +* Updated packages: + - zope.app.cache 3.6.0 + Bugs Fixed ++ Modified: Zope/trunk/versions.cfg === --- Zope/trunk/versions.cfg 2009-05-27 16:14:22 UTC (rev 100476) +++ Zope/trunk/versions.cfg 2009-05-27 16:16:23 UTC (rev 100477) @@ -33,7 +33,7 @@ zope.app.appsetup = 3.11 zope.app.basicskin = 3.4.0 zope.app.broken = 3.5.0 -zope.app.cache = 3.5.0 +zope.app.cache = 3.6.0 zope.app.catalog = 3.8.0 zope.app.component = 3.8.2 zope.app.container = 3.8.0 ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/ Integrated zLOG package back into this package. There's really no reason why anyone should want to use that one stand-alone
Log message for revision 100487: Integrated zLOG package back into this package. There's really no reason why anyone should want to use that one stand-alone Changed: U Zope/trunk/doc/CHANGES.rst U Zope/trunk/setup.py A Zope/trunk/src/zLOG/ -=- Modified: Zope/trunk/doc/CHANGES.rst === --- Zope/trunk/doc/CHANGES.rst 2009-05-27 18:11:01 UTC (rev 100486) +++ Zope/trunk/doc/CHANGES.rst 2009-05-27 20:46:37 UTC (rev 100487) @@ -11,6 +11,8 @@ Restructuring + +* Integrated zLOG package back into this package. + * Updated documentation to new version number. Features Added Modified: Zope/trunk/setup.py === --- Zope/trunk/setup.py 2009-05-27 18:11:01 UTC (rev 100486) +++ Zope/trunk/setup.py 2009-05-27 20:46:37 UTC (rev 100487) @@ -113,7 +113,6 @@ 'tempstorage', 'transaction', 'zdaemon', - 'zLOG', 'zope.component', 'zope.configuration', 'zope.container', ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/ zope.server = 3.6.0
Log message for revision 100493: zope.server = 3.6.0 Changed: U Zope/trunk/doc/CHANGES.rst U Zope/trunk/versions.cfg -=- Modified: Zope/trunk/doc/CHANGES.rst === --- Zope/trunk/doc/CHANGES.rst 2009-05-27 21:00:14 UTC (rev 100492) +++ Zope/trunk/doc/CHANGES.rst 2009-05-27 21:01:42 UTC (rev 100493) @@ -22,6 +22,7 @@ - zope.app.cache = 3.6.0 - zope.app.pagetemplate = 3.7.1 + - zope.server = 3.6.0 Bugs Fixed ++ Modified: Zope/trunk/versions.cfg === --- Zope/trunk/versions.cfg 2009-05-27 21:00:14 UTC (rev 100492) +++ Zope/trunk/versions.cfg 2009-05-27 21:01:42 UTC (rev 100493) @@ -119,7 +119,7 @@ zope.securitypolicy = 3.6.0 zope.sendmail = 3.5.1 zope.sequencesort = 3.4.0 -zope.server = 3.5.0 +zope.server = 3.6.0 zope.session = 3.9.1 zope.site = 3.6.1 zope.size = 3.4.1 ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
Re: [Zope-dev] [Checkins] SVN: zope.app.http/trunk/ - Replaced thedependency on zope.deprecation with BBB imports
On 2009-05-26, Roger Ineichen d...@projekt01.ch wrote: Some people think it's better to have a nice clean log then deprecation warnings on server startup. I still don't understand the reason if there is any. Probably others can explain why we skip the deprecation warnings which is a hugh win for migration tasks. Main reason: often you get buried in deprecation warnings which then drown out potentially more important warnings. When migrating: yes, such deprecation warnings are handy. But in 99% of the cases you'll just be *using* the various libraries and you still get a load of warnings. Complaints/questions about the huge list of deprecation warnings in earlier plone versions were a regular occurrence on the mailinglists. So: yes, there's a reason. Perhaps not the best one, but still. Reinout -- Reinout van Rees - rein...@vanrees.org - http://reinout.vanrees.org Software developer at http://www.thehealthagency.com Military engineers build missiles. Civil engineers build targets ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zsql and oracle CLOB column
Dear list,
While inserting data into one of the oracle table's CLOB column using
zsql via python script, we observed that zope process (running in debug
mode) is getting terminated/killed if length of text data = 4094 with
message on command prompt
Input string too long, limit 4096
Whereas for text data with length =4001 and =4093 - It throws
following error
OperationalError on Products.mxODBCZopeDA.ZopeDA.DatabaseConnection
DSN=test_clob_oracle thread 3672/3672 at 0x3ac3530: ('HY000', 1704,
'[Oracle][ODBC][Ora]ORA-01704: string literal too long\n', 6113)
python script details:
print context.clob_zsql_test(i_description='A'*4095).
return printed
zsql details -
INSERT INTO CLOB_TEST(description) VALUES(dtml-sqlvar i_description
type=string)
Table/column details :
id - number
description - clob
Where as if we use mxODBCZopeDA execute API with following insert query
syntax
string_value = 'A'*5000
query = INSERT INTO CLOB_TEST(document) VALUES(?)
result = test_connection.execute(query, string_value)
it works fine even with text data having length 1
After googling on the same found that execute method uses/support
parameters binding (is it similar to oracle bind varibles ? thats may be
reason why it works well). Do we have similar support for zsql or is
there other workaround ?
Configuration/other details are as follows :
RDBMS : Oracle Database 10g Release 10.2.0.1.0
ODBC used : Oracle ODBC which shipped with Oracle-Client-10g
Python adapter : mxODBC Python ODBC Interface - 2.1
Related Zope Product : mxODBCZopeDA-1.0.10
Zope : Zope 2.11.1-final
Python : python 2.4.4
Operating system : win32
ZEO setup : Yes
No of ZEO nodes : one
Threads per ZEO node : 10
Any kind of pointers/suggestions would be of great help.
Thanking you,
Harshad.
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 2 OK
Summary of messages to the zope-tests list. Period Tue May 26 12:00:00 2009 UTC to Wed May 27 12:00:00 2009 UTC. There were 2 messages: 2 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Tue May 26 20:47:30 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011801.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Tue May 26 20:49:34 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011802.html ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zope.app.http/trunk/ - Replacedthedependency on zope.deprecation with BBB imports
Hi Reinout Betreff: Re: [Zope-dev] [Checkins] SVN: zope.app.http/trunk/ - Replacedthedependency on zope.deprecation with BBB imports On 2009-05-26, Roger Ineichen d...@projekt01.ch wrote: Some people think it's better to have a nice clean log then deprecation warnings on server startup. I still don't understand the reason if there is any. Probably others can explain why we skip the deprecation warnings which is a hugh win for migration tasks. Main reason: often you get buried in deprecation warnings which then drown out potentially more important warnings. When migrating: yes, such deprecation warnings are handy. But in 99% of the cases you'll just be *using* the various libraries and you still get a load of warnings. Complaints/questions about the huge list of deprecation warnings in earlier plone versions were a regular occurrence on the mailinglists. So: yes, there's a reason. Perhaps not the best one, but still. I think there is something else wrong if someone is using code with deprecation warnings in a production setup. The deprecation warning should never show up on a production server because you have to make sure that you don't use deprecated code. That's the only goal of the deprecation system. Your reason says that you like to use packages with deprecated code in a production setup. On the other side developer which take care on deprecated code can't be sure that we use deprecateded code or not. That's not nice. I was afraid excatly of this use case. Skiping deprecation warnings is a workarround for official release and use deprecated code instead of update everything. A good solution whould prevent to use deprecated code in a production setup and not only skip the deprecation warnings because we as developer know that this will also works. btw, I also think indirect imports are not the same as deprecated imports. Of corse a deprecated import is a indirect import but a indirect import is not implicit a deprecated import. That's just a very ugly pattern for do something which should be done in another way. Parsing # BBB comments whould be a better solution for find deprecated imports. Regards Roger Ineichen Reinout -- Reinout van Rees - rein...@vanrees.org - http://reinout.vanrees.org Software developer at http://www.thehealthagency.com Military engineers build missiles. Civil engineers build targets ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zope.app.http/trunk/ - Replacedthedependency on zope.deprecation with BBB imports
Hi there, Before we have this discussion yet again, I will record the official stance in the zope toolkit decisions document, and I'll quote it here: * When code moves to a new location to import it from (in the same or another package), use a ``from foo import bar`` statement, with a ``#BBB`` comment to indicate the import is only there to support backwards compatibility. In the CHANGES.txt of a package, state that an import location got deprecated and where the new location is (making this a feature release, not a bugfix release). Reasons: * it avoid a dependency on zope.deprecation, which is quite involved in its implementation, using proxies. * A ``from .. import ..`` is immediately comprehensible to any Python programmer as well as tools. * Deprecation warnings make it hard to write a library that supports multiple versions of another library; a change in an indirect dependency can create deprecation warnings that the original developer does not care about. * We are in the process of developing a testrunner extension that will report on indirect imports, and a ZODB upgrade procedure. Feel free to discuss it, either to add arguments to refine this, or to attempt to overthrow this decision entirely. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zope.app.http/trunk/ - Replacedthedependency on zope.deprecation with BBB imports
Hi Martijn Betreff: Re: [Zope-dev] [Checkins] SVN: zope.app.http/trunk/ - Replacedthedependency on zope.deprecation with BBB imports Hi there, Before we have this discussion yet again, I will record the official stance in the zope toolkit decisions document, and I'll quote it here: * When code moves to a new location to import it from (in the same or another package), use a ``from foo import bar`` statement, with a ``#BBB`` comment to indicate the import is only there to support backwards compatibility. In the CHANGES.txt of a package, state that an import location got deprecated and where the new location is (making this a feature release, not a bugfix release). Reasons: * it avoid a dependency on zope.deprecation, which is quite involved in its implementation, using proxies. * A ``from .. import ..`` is immediately comprehensible to any Python programmer as well as tools. * Deprecation warnings make it hard to write a library that supports multiple versions of another library; a change in an indirect dependency can create deprecation warnings that the original developer does not care about. * We are in the process of developing a testrunner extension that will report on indirect imports, and a ZODB upgrade procedure. Feel free to discuss it, either to add arguments to refine this, or to attempt to overthrow this decision entirely. The only thing I could say about this concept is that we didn't start to remove #BBB marked imports. Just wait till we start remove the BBB imports and the packages from install_requires ... Regards Roger Ineichen Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope] Zsql and oracle CLOB column
harshad behere wrote:
Dear list,
While inserting data into one of the oracle table's CLOB column using
zsql via python script, we observed that zope process (running in debug
mode) is getting terminated/killed if length of text data = 4094 with
message on command prompt
Input string too long, limit 4096
Above one more looks like issue/bug with oracle odbc driver rather than
zsql/zope issue.
http://164.100.150.68/downloads/oracle/Oracle_InstantClient/Oracle/instantclient10_1/ODBCRelnotesUS.htm
http://www.dbatools.net/doc/bug10203.html
http://mail.python.org/pipermail/python-list/2007-March/603644.html
Whereas for text data with length =4001 and =4093 - It throws
following error
OperationalError on Products.mxODBCZopeDA.ZopeDA.DatabaseConnection
DSN=test_clob_oracle thread 3672/3672 at 0x3ac3530: ('HY000', 1704,
'[Oracle][ODBC][Ora]ORA-01704: string literal too long\n', 6113)
python script details:
print context.clob_zsql_test(i_description='A'*4095).
return printed
zsql details -
INSERT INTO CLOB_TEST(description) VALUES(dtml-sqlvar i_description
type=string)
Table/column details :
id - number
description - clob
Where as if we use mxODBCZopeDA execute API with following insert query
syntax
string_value = 'A'*5000
query = INSERT INTO CLOB_TEST(document) VALUES(?)
result = test_connection.execute(query, string_value)
it works fine even with text data having length 1
After googling on the same found that execute method uses/support
parameters binding (is it similar to oracle bind varibles ? thats may be
reason why it works well). Do we have similar support for zsql or is
there other workaround ?
Configuration/other details are as follows :
RDBMS : Oracle Database 10g Release 10.2.0.1.0
ODBC used : Oracle ODBC which shipped with Oracle-Client-10g
Python adapter : mxODBC Python ODBC Interface - 2.1
Related Zope Product : mxODBCZopeDA-1.0.10
Zope : Zope 2.11.1-final
Python : python 2.4.4
Operating system : win32
ZEO setup : Yes
No of ZEO nodes : one
Threads per ZEO node : 10
Any kind of pointers/suggestions would be of great help.
Thanking you,
Harshad.
___
Zope maillist - z...@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Test failure in zope.traversing 3.7.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tres Seaver wrote: Andreas Jung wrote: I get the following failure while running the Zope 2.12 tests: aj...@suxmac2:~/sandboxes/Zope-2.12/2.12 bin/alltests Test-module import failures: Module: zope.traversing.tests.test_vhosting Traceback (most recent call last): File /Users/ajung/.buildout/eggs/zope.traversing-3.7.0-py2.5.egg/zope/traversing/tests/test_vhosting.py, line 28, in module from zope.app.zptpage.zptpage import ZPTPage File /Users/ajung/.buildout/eggs/zope.app.zptpage-3.5.0-py2.5.egg/zope/app/zptpage/__init__.py, line 18, in module from zptpage import ZPTPage File /Users/ajung/.buildout/eggs/zope.app.zptpage-3.5.0-py2.5.egg/zope/app/zptpage/zptpage.py, line 29, in module from zope.app.pagetemplate.engine import AppPT ImportError: No module named engine 'alltests' is likely to break frequently during refactorings, I'm afraid. I ran 'bin/test --all' before committing changes, but didn't run that one. That test is intrinsically broken on a couple of axes: - It depends on 'zope.app.zptpage' to create a renderable object (ACK!) - It depends on other 'zope.app.*' packages inappropriately. - It imports a bunch of stuff at module scope. - It tests too much in individual methods. I will update the tests to remove all 'zope.app' dependencies, which will fix this problem when I release the new egg. Ugh. I got stuck trying to fix the tests, which are pretty nasty. As a workaround, I just released zope.app.pagetemplate 3.7.1, which restores the importabiltiy of the names from 'zope.app.pagetemplate.engine' via BBB imports from 'zope.pagetemplate.engine'. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKHXEY+gerLs4ltQ4RAvPLAKDcb46vite8XhxjhJCpjlPO7KPTEwCgpQVC r4xLlk7rbrJsI5g58r1eTtA= =41fU -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zope.app.http/trunk/ - Replacedthedependency on zope.deprecation with BBB imports
On Wed, May 27, 2009 at 02:06:03PM +0200, Roger Ineichen wrote: I think there is something else wrong if someone is using code with deprecation warnings in a production setup. Do you not use any third-party code? Often, the deprecation warnings are emitted by code not under your control. - PW -- Paul Winkler http://www.slinkp.com ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zope.app.http/trunk/- Replacedthedependency on zope.deprecation with BBB imports
Hi Paul Betreff: Re: [Zope-dev] [Checkins] SVN: zope.app.http/trunk/- Replacedthedependency on zope.deprecation with BBB imports On Wed, May 27, 2009 at 02:06:03PM +0200, Roger Ineichen wrote: I think there is something else wrong if someone is using code with deprecation warnings in a production setup. Do you not use any third-party code? No not really, just python, zope and z3c libraries, on windows some win32 or ctypes. Often, the deprecation warnings are emitted by code not under your control. I think using packages with deprecated code is just a workarround if someone needs to use new features which is built in a newer version of a package and can't use all the newer versions of the packages this package depends on. (BBB) The better way is to use the old package or the new set of packages. I agree that this is not always possible. But we should not excuse us and tink that this is correct. It still has a hugh potential of problems because the set of versions is based on BBB and this part is not well tested or test are removed. Most the time if you will run into unexpected problems, some untested old BB code is involved. Take a look at the old registry code in our zope packages as a sample. Regards Roger Ineichen - PW -- Paul Winkler http://www.slinkp.com ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zope.app.http /trunk/- Replacedthedependency on zope.deprecation wit h BBB imports
On Wednesday 27 May 2009, Roger Ineichen wrote: I think using packages with deprecated code is just a workarround if someone needs to use new features which is built in a newer version of a package and can't use all the newer versions of the packages this package depends on. (BBB) The better way is to use the old package or the new set of packages. I agree that this is not always possible. But we should not excuse us and tink that this is correct. It still has a hugh potential of problems because the set of versions is based on BBB and this part is not well tested or test are removed. Most the time if you will run into unexpected problems, some untested old BB code is involved. Take a look at the old registry code in our zope packages as a sample. I have been following this discussion and just want to mention that I fully agree with Roger. If you release a final version of Zope or a package that spews deprecation warnings or has not fixed the imports, then this should be considered bad releasing. Regards, Stephan -- Entrepreneur and Software Geek Google me. Zope Stephan Richter ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope] Error packing database
Dear list, when trying to pack my data base, I get the following error: --- 2009-05-26T18:30:52 ERROR ZODB.DB packing Traceback (most recent call last): File /var/www/zope/lib/python/ZODB/DB.py, line 605, in pack self._storage.pack(t, referencesf) File /var/www/zope/lib/python/ZODB/FileStorage/FileStorage.py, line 1377, in pack self._commit_lock_release() error: release unlocked lock -- 2009-05-26T18:30:53 ERROR Zope.SiteErrorLog http://localhost:8080/Control_Panel/Database/main/manage_pack Traceback (innermost last): Module ZPublisher.Publish, line 115, in publish Module ZPublisher.mapply, line 88, in mapply Module ZPublisher.Publish, line 41, in call_object Module App.ApplicationManager, line 426, in manage_pack Module ZODB.DB, line 605, in pack Module ZODB.FileStorage.FileStorage, line 1377, in pack error: release unlocked lock -- I searched the web for help, but did not find anything really helpful. Is this due to some timeout of the web browser? The Data.fs is quite large (7 GB). Should I rather pack the data base via shell and not using the ZMI? What is the command to do so? Thanks, Fabian ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Zsql and oracle CLOB column
Dear list,
While inserting data into one of the oracle table's CLOB column using
zsql via python script, we observed that zope process (running in debug
mode) is getting terminated/killed if length of text data = 4094 with
message on command prompt
Input string too long, limit 4096
Whereas for text data with length =4001 and =4093 - It throws
following error
OperationalError on Products.mxODBCZopeDA.ZopeDA.DatabaseConnection
DSN=test_clob_oracle thread 3672/3672 at 0x3ac3530: ('HY000', 1704,
'[Oracle][ODBC][Ora]ORA-01704: string literal too long\n', 6113)
python script details:
print context.clob_zsql_test(i_description='A'*4095).
return printed
zsql details -
INSERT INTO CLOB_TEST(description) VALUES(dtml-sqlvar i_description
type=string)
Table/column details :
id - number
description - clob
Where as if we use mxODBCZopeDA execute API with following insert query
syntax
string_value = 'A'*5000
query = INSERT INTO CLOB_TEST(document) VALUES(?)
result = test_connection.execute(query, string_value)
it works fine even with text data having length 1
After googling on the same found that execute method uses/support
parameters binding (is it similar to oracle bind varibles ? thats may be
reason why it works well). Do we have similar support for zsql or is
there other workaround ?
Configuration/other details are as follows :
RDBMS : Oracle Database 10g Release 10.2.0.1.0
ODBC used : Oracle ODBC which shipped with Oracle-Client-10g
Python adapter : mxODBC Python ODBC Interface - 2.1
Related Zope Product : mxODBCZopeDA-1.0.10
Zope : Zope 2.11.1-final
Python : python 2.4.4
Operating system : win32
ZEO setup : Yes
No of ZEO nodes : one
Threads per ZEO node : 10
Any kind of pointers/suggestions would be of great help.
Thanking you,
Harshad.
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Error packing database
- Original Message - From: Fabian Schoeck fabian.scho...@physik.uni-erlangen.de To: zope@zope.org Sent: Wednesday, May 27, 2009 4:08 AM Subject: [Zope] Error packing database I searched the web for help, but did not find anything really helpful. Is this due to some timeout of the web browser? The Data.fs is quite large (7 GB). Should I rather pack the data base via shell and not using the ZMI? What is the command to do so? Google manage_pack. Jonathan ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zsql and oracle CLOB column
harshad behere wrote:
Dear list,
While inserting data into one of the oracle table's CLOB column using
zsql via python script, we observed that zope process (running in debug
mode) is getting terminated/killed if length of text data = 4094 with
message on command prompt
Input string too long, limit 4096
Above one more looks like issue/bug with oracle odbc driver rather than
zsql/zope issue.
http://164.100.150.68/downloads/oracle/Oracle_InstantClient/Oracle/instantclient10_1/ODBCRelnotesUS.htm
http://www.dbatools.net/doc/bug10203.html
http://mail.python.org/pipermail/python-list/2007-March/603644.html
Whereas for text data with length =4001 and =4093 - It throws
following error
OperationalError on Products.mxODBCZopeDA.ZopeDA.DatabaseConnection
DSN=test_clob_oracle thread 3672/3672 at 0x3ac3530: ('HY000', 1704,
'[Oracle][ODBC][Ora]ORA-01704: string literal too long\n', 6113)
python script details:
print context.clob_zsql_test(i_description='A'*4095).
return printed
zsql details -
INSERT INTO CLOB_TEST(description) VALUES(dtml-sqlvar i_description
type=string)
Table/column details :
id - number
description - clob
Where as if we use mxODBCZopeDA execute API with following insert query
syntax
string_value = 'A'*5000
query = INSERT INTO CLOB_TEST(document) VALUES(?)
result = test_connection.execute(query, string_value)
it works fine even with text data having length 1
After googling on the same found that execute method uses/support
parameters binding (is it similar to oracle bind varibles ? thats may be
reason why it works well). Do we have similar support for zsql or is
there other workaround ?
Configuration/other details are as follows :
RDBMS : Oracle Database 10g Release 10.2.0.1.0
ODBC used : Oracle ODBC which shipped with Oracle-Client-10g
Python adapter : mxODBC Python ODBC Interface - 2.1
Related Zope Product : mxODBCZopeDA-1.0.10
Zope : Zope 2.11.1-final
Python : python 2.4.4
Operating system : win32
ZEO setup : Yes
No of ZEO nodes : one
Threads per ZEO node : 10
Any kind of pointers/suggestions would be of great help.
Thanking you,
Harshad.
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope-DB] [Zope] Zsql and oracle CLOB column
harshad behere wrote:
Dear list,
While inserting data into one of the oracle table's CLOB column using
zsql via python script, we observed that zope process (running in debug
mode) is getting terminated/killed if length of text data = 4094 with
message on command prompt
Input string too long, limit 4096
Above one more looks like issue/bug with oracle odbc driver rather than
zsql/zope issue.
http://164.100.150.68/downloads/oracle/Oracle_InstantClient/Oracle/instantclient10_1/ODBCRelnotesUS.htm
http://www.dbatools.net/doc/bug10203.html
http://mail.python.org/pipermail/python-list/2007-March/603644.html
Whereas for text data with length =4001 and =4093 - It throws
following error
OperationalError on Products.mxODBCZopeDA.ZopeDA.DatabaseConnection
DSN=test_clob_oracle thread 3672/3672 at 0x3ac3530: ('HY000', 1704,
'[Oracle][ODBC][Ora]ORA-01704: string literal too long\n', 6113)
python script details:
print context.clob_zsql_test(i_description='A'*4095).
return printed
zsql details -
INSERT INTO CLOB_TEST(description) VALUES(dtml-sqlvar i_description
type=string)
Table/column details :
id - number
description - clob
Where as if we use mxODBCZopeDA execute API with following insert query
syntax
string_value = 'A'*5000
query = INSERT INTO CLOB_TEST(document) VALUES(?)
result = test_connection.execute(query, string_value)
it works fine even with text data having length 1
After googling on the same found that execute method uses/support
parameters binding (is it similar to oracle bind varibles ? thats may be
reason why it works well). Do we have similar support for zsql or is
there other workaround ?
Configuration/other details are as follows :
RDBMS : Oracle Database 10g Release 10.2.0.1.0
ODBC used : Oracle ODBC which shipped with Oracle-Client-10g
Python adapter : mxODBC Python ODBC Interface - 2.1
Related Zope Product : mxODBCZopeDA-1.0.10
Zope : Zope 2.11.1-final
Python : python 2.4.4
Operating system : win32
ZEO setup : Yes
No of ZEO nodes : one
Threads per ZEO node : 10
Any kind of pointers/suggestions would be of great help.
Thanking you,
Harshad.
___
Zope maillist - z...@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
___
Zope-DB mailing list
Zope-DB@zope.org
http://mail.zope.org/mailman/listinfo/zope-db
