Some Zope distributions are missing Data.fs.in
Hi all, I'm using win2k and zope2.5.1 and python 2.1.2. And I don't have the file Data.fs.in. I have the others files. Am I suppose to have this file on win32. tia, - James
Good to hear that! However, I have received the following report:
---8<---
I do have a 'Data.fs', 'Data.fs.lock' and 'Data.fs.tmp' files in the '/usr/lib/zope/var' directory, but no 'Data.fs.in' file. =( Is this bad?
My zope is 2.5.1 and I'm using python 2.1.3. I installed zope using the debian "apt-get" command...
_________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx
James Johnson wrote:
Hi all, I'm using win2k and zope2.5.1 and python 2.1.2. And I don't have the file Data.fs.in. I have the others files. Am I suppose to have this file on win32. tia, - James
You don't need it; it merely provides a bootstrap of what Zope does on startup if there is no Data.fs anyway.
Matt, You need Data.fs.in to run unit tests. The Testing package does not work without it. See lib/python/Testing/custom_zodb.py. Stefan --On Mittwoch, 11. September 2002 16:25 -0400 "Matthew T. Kromer" <matt@zope.com> wrote:
James Johnson wrote:
Hi all, I'm using win2k and zope2.5.1 and python 2.1.2. And I don't have the file Data.fs.in. I have the others files. Am I suppose to have this file on win32. tia, - James
You don't need it; it merely provides a bootstrap of what Zope does on startup if there is no Data.fs anyway.
-- Those who write software only for pay should go hurt some other field. /Erik Naggum/
Stefan H. Holek wrote:
You need Data.fs.in to run unit tests. The Testing package does not work without it. See lib/python/Testing/custom_zodb.py.
FWIW, I'm looking into removing that requirement. With a tweaked custom_zodb.py and minor changes to the sessioning machinery, all but three tests pass. (And if I recall correctly, the failing tests are ZEO tests.) Shane
Shane, You are talking about the Zope core unit tests, aren't you? Can you be equally sure you do not break third party tests people wrote for their own products and packages? Please keep in mind that ZC is not the only one using the Testing package to write their unit tests. I am wondering why such a change would be necessary at all. If it is just "for the heck of it" I politely ask to reconsider that decision. ;-) TIA, Stefan On Wed, 11 Sep 2002, Shane Hathaway wrote:
Stefan H. Holek wrote:
You need Data.fs.in to run unit tests. The Testing package does not work without it. See lib/python/Testing/custom_zodb.py.
FWIW, I'm looking into removing that requirement. With a tweaked custom_zodb.py and minor changes to the sessioning machinery, all but three tests pass. (And if I recall correctly, the failing tests are ZEO tests.)
Shane
Stefan H. Holek wrote:
You are talking about the Zope core unit tests, aren't you? Can you be equally sure you do not break third party tests people wrote for their own products and packages? Please keep in mind that ZC is not the only one using the Testing package to write their unit tests.
I am wondering why such a change would be necessary at all. If it is just "for the heck of it" I politely ask to reconsider that decision. ;-)
We are planning to do away with Data.fs.in at some time. That's not "for the heck of it". ;-) Shane
Stefan H. Holek wrote:
Shane,
You are talking about the Zope core unit tests, aren't you? Can you be equally sure you do not break third party tests people wrote for their own products and packages? Please keep in mind that ZC is not the only one using the Testing package to write their unit tests.
I am wondering why such a change would be necessary at all. If it is just "for the heck of it" I politely ask to reconsider that decision. ;-)
It is our intent to remove Data.fs.in from distributions; any third party tests relying on this file existing should be altered to not rely upon it. -- Matt Kromer Zope Corporation http://www.zope.com/
participants (4)
-
James Johnson -
Matthew T. Kromer -
Shane Hathaway -
Stefan H. Holek