1. 18 Nov, 2024 4 commits
  2. 15 Nov, 2024 25 commits
  3. 14 Nov, 2024 1 commit
  4. 13 Nov, 2024 3 commits
  5. 12 Nov, 2024 2 commits
  6. 11 Nov, 2024 5 commits
    • Jérome Perrin's avatar
      stack/erp5: depends on Products.TemporaryFolder · 54606432
      Jérome Perrin authored
      Prevents error like this in the log for ZODB with a tmep_folder
      
      2024-10-04 14:14:53,288 ERROR Zope.ZODBMountPoint Failed to mount database. <type 'exceptions.ImportError'> (No module named TemporaryFolder)
      Traceback (most recent call last):
        File "./eggs/Products.ZODBMountPoint-1.3-py2.7.egg/Products/ZODBMountPoint/MountedObject.py", line 255, in _getOrOpenObject
          obj = self._traverseToMountedRoot(root, parent)
        File "./eggs/Products.ZODBMountPoint-1.3-py2.7.egg/Products/ZODBMountPoint/MountedObject.py", line 213, in _traverseToMountedRoot
          obj = blazer.traverseOrConstruct(real_path)
        File "./eggs/Products.ZODBMountPoint-1.3-py2.7.egg/Products/ZODBMountPoint/MountedObject.py", line 81, in traverseOrConstruct
          container = self._construct(container, part)
        File "./eggs/Products.ZODBMountPoint-1.3-py2.7.egg/Products/ZODBMountPoint/MountedObject.py", line 108, in _construct
          klass = jar.db().classFactory(jar, self.module_name, self.class_name)
        File "./eggs/Zope-4.8.7-py2.7.egg/Zope2/Startup/datatypes.py", line 288, in simpleClassFactory
          m = __import__(module, _globals, _globals, _silly)
      ImportError: No module named TemporaryFolder
      54606432
    • Jérome Perrin's avatar
      component/zodbtools: switch to always using a git checkout · e3d55223
      Jérome Perrin authored
      This ease the development and version updates
      e3d55223
    • Jérome Perrin's avatar
      software/erp5/test: remove a leftover db.close() from debugging · 9d2c06af
      Jérome Perrin authored
      This is not needed because we are using a closing context manager
      9d2c06af
    • Jérome Perrin's avatar
    • Kirill Smelkov's avatar
      pygolang: Accompany python-interpreter with gpython-interpreter to run gpython... · 1e9a9019
      Kirill Smelkov authored
      pygolang: Accompany python-interpreter with gpython-interpreter to run gpython instead of std python
      
      With python-interpreter staying the default for pyprog, but possible to adjust.
      
      We will need gpython-interpreter for ERP5 to use bstr+ustr as builting string types.
      
      Remove [gpython] script in favour of gpython-interpreter since both provide the
      same thing but via slightly different ways internally ([gpython] was generating
      bin/gpython via setuptools and [gpython-interpreter] does it by hand with
      user-visible result staying the same).
      
      /cc @kazuhiko, @jerome
      1e9a9019