bin/scriptzope fails with ImportError: No module named paths

Bug #185219 reported by Marius Gedminas
4
Affects Status Importance Assigned to Milestone
Zope 3
Won't Fix
Undecided
Unassigned

Bug Description

zopeskel/bin/scriptzope.in contains the following two lines:

  import paths
  paths.addPackagePaths()

but there's no paths.py in the Zope 3 tree. Users complain that running zopectl run script.py gives them an ImportError: No module named 'paths'.

runzope/debugzope scripts don't have these statements. I suspect this is some legacy from Zope 2, and these two lines ought to be removed. I'm completely unfamiliar with this scriptzope, so I'm reluctant to just go and remove it without knowing how to test it. Apparently it has no tests, or the bug would've been noticed before.

Revision history for this message
Christian Theune (ctheune) wrote :

This is a remnant of the old build/installation procedure, I think we won't fix that anymore.

Changed in zope3:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.