#27 — ImportError: cannot import name transaction

by Lukas Zdych — last modified Jan 05, 2009 09:32 AM
State Resolved
Version:
Area Functionality
Issue type Bug
Severity Medium
Submitted by Lukas Zdych
Submitted on Dec 20, 2005
Responsible
—
Target release:
—
Return to tracker




Import Error of not existing module in Archetypes 1.3.5 (included in Plone 2.1.1).



2005-12-20 19:22:00<br />failed:<br />Traceback (most recent call last):<br /><br /> File "/home/zope/moje_zope02/Products/CMFQuickInstallerTool/QuickInstallerTool.py", line 311, in installProduct<br /> res=install(portal)<br /><br /> File "/home/zope/zope/zope2.8.4-final/lib/python/Products/ExternalMethod/ExternalMethod.py", line 225, in __call__<br /> try: return f(*args, **kw)<br /><br /> File "/home/zope/moje_zope02/Products/Poi/Extensions/Install.py", line 133, in install<br /> install = ExternalMethod('temp','temp',PROJECTNAME+'.AppInstall', 'install')<br /><br /> File "/home/zope/zope/zope2.8.4-final/lib/python/Products/ExternalMethod/ExternalMethod.py", line 111, in __init__<br /> self.manage_edit(title, module, function)<br /><br /> File "/home/zope/zope/zope2.8.4-final/lib/python/Products/ExternalMethod/ExternalMethod.py", line 134, in manage_edit<br /> self.getFunction(1)<br /><br /> File "/home/zope/zope/zope2.8.4-final/lib/python/Products/ExternalMethod/ExternalMethod.py", line 141, in getFunction<br /> f=getObject(self._module, self._function, reload)<br /><br /> File "/home/zope/zope/zope2.8.4-final/lib/python/App/Extensions.py", line 148, in getObject<br /> exec execsrc in m<br /><br /> File "/home/zope/moje_zope02/Products/Poi/Extensions/AppInstall.py", line 7, in ?<br /> from Products.Poi.Extensions.Migrations import migrate<br /><br /> File "/home/zope/moje_zope02/Products/Poi/Extensions/Migrations.py", line 12, in ?<br /> from Products.Archetypes import transaction<br /><br />ImportError: cannot import name transaction<br />

Steps to reproduce:
Untar "Poi 1.0 beta 2 svn/unreleased build 5" into Products directory
Open QuickInstaller in portal_setup
Check Poi for installation
Click on "install" button
Added by Martin Aspeli on Dec 20, 2005 11:19 PM
Issue state: unconfirmed → open
Right. It appears I inadvertently made Poi dependent on AT 1.3.6. This should be released with Plone 2.1.2 very shortly. This whole mess is a pain in the back side.

I'm undecided whether we should just depend on 2.1.2 (this is not in a release of Poi anyway) or jump through more hoops to get Zope 2.7-8-9 to like itself.
Added by Rocky Burt on Dec 21, 2005 12:25 AM
This becomes a bit of a toss up.  Personally I would have no problems depending on Plone 2.1.2.  But, you will certainly narrow the initial audience wanting to use Poi if that happens.


Added by (anonymous) on Dec 21, 2005 07:44 AM
I also don't have problem with depending on Plone 2.1.2 (will be out very soon and I'm looking forward to upgrade ;). But you has to specify it somewhere in readme. I though that it is about AT 1.3.6 but common user of Plone shouldn't know where is the problem when they get install result like this.
Added by Rocky Burt on Dec 28, 2005 05:19 PM
Issue state: open → resolved
After recent discussion with optilude it was confirmed that Poi 1.0 will indeed require Plone 2.1.2+.  I've updated README.txt to reflect this.


No responses can be added.