Fred Drake wrote:
On 9/2/05, Dmitry Vasiliev <[EMAIL PROTECTED]> wrote:
Before the fix (rev. 38239):
['buildsupport', ..., 'src']
After the fix:
['src','buildsupport', ...]
Ok, I think I understand this now. Appearantly you have some version
of ZConfig installed elsewhere that is get
Fred Drake wrote:
On 9/2/05, Dmitry Vasiliev <[EMAIL PROTECTED]> wrote:
I now agree that the change is reasonable. It needs a comment that
it's protecting against importing *installed* versions of ZConfig.
It would also be nice if it used .insert() instead of a [:0] slice.
--
Benji York
Senior
On 9/2/05, Dmitry Vasiliev <[EMAIL PROTECTED]> wrote:
> Before the fix (rev. 38239):
>
>['buildsupport', ..., 'src']
>
> After the fix:
>
>['src','buildsupport', ...]
Ok, I think I understand this now. Appearantly you have some version
of ZConfig installed elsewhere that is getting pic
Fred Drake wrote:
Ugh, the problem is in new setup.py at line 24:
site.addsitedir(buildsupport)
'src' directory now appended at the end of the sys.path and old version of
ZConfig had been imported by zpgsetup.
This is surprising. The sys.path.insert(0, ...) line (which you
removed) was inte
On 9/2/05, Dmitry Vasiliev <[EMAIL PROTECTED]> wrote:
> There is a problem to build extensions for the Zope3 trunk (and I guess
> for ZODB trunk as well) - all extension module names is lowercased now.
> For example:
This is a symptom of getting the wrong ZConfig version. This setup
requires 2.3.
Dmitry Vasiliev wrote:
There is a problem to build extensions for the Zope3 trunk (and I guess
for ZODB trunk as well) - all extension module names is lowercased now.
For example:
gcc -pthread -shared
build/temp.linux-i686-2.4/src/persistent/TimeStamp.o -o
src/persistent/timestamp.so
I g
There is a problem to build extensions for the Zope3 trunk (and I guess for
ZODB trunk as well) - all extension module names is lowercased now. For example:
gcc -pthread -shared build/temp.linux-i686-2.4/src/persistent/TimeStamp.o -o
src/persistent/timestamp.so
I guess the problem that the
