In the installer, can be the check of dependence?

[caf2for4@…]

When executing the "Windows installer (32-bit Python)" on the Windows7 32bit OS, the installer was successfully completed. However , an error has occurred in the lack of dependent package at the time of project creation.

Since to resolve each problem of the dependency takes also time and effort, can be the check of dependence in the installer?

C:\Users\xxx>trac-admin C:\Trac\Projects\TestProject initenv
Traceback (most recent call last):
  File "C:\Python\Python27\Scripts\trac-admin-script.py", line 5, in <module>
    from pkg_resources import load_entry_point
  File "C:\Python\Python27\lib\site-packages\pkg_resources\__init__.py", line 3084, in <module>
    @_call_aside
  File "C:\Python\Python27\lib\site-packages\pkg_resources\__init__.py", line 3070, in _call_aside
    f(*args, **kwargs)
  File "C:\Python\Python27\lib\site-packages\pkg_resources\__init__.py", line 3097, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "C:\Python\Python27\lib\site-packages\pkg_resources\__init__.py", line 651, in _build_master
    ws.require(__requires__)
  File "C:\Python\Python27\lib\site-packages\pkg_resources\__init__.py", line 952, in require
    needed = self.resolve(parse_requirements(requirements))
  File "C:\Python\Python27\lib\site-packages\pkg_resources\__init__.py", line 839, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'Genshi>=0.6' distribution was not found and is required by Trac

[Ryan J Ollos]

Replying to caf2for4@…:

Since to resolve each problem of the dependency takes also time and effort, can be the check of dependence in the installer?

We use python setup.py bdist_wininst to create the installer (TracDev/ReleaseChecklist#Createdistpackages). As far as I know setuptools does not provide a mechanism for specifying dependencies when creating the windows installer. I'm not sure the Windows installer even has a mechanism. Probably, the preferred mechanism is to bundle the dependency in the installer, which is outside the scope of what we are delivering in the release, but is something that third parties like ​Bitnami provide.

If you can research and provide some recommendations on how to solve the issue we will gladly consider. Otherwise, the ticket will probably be closed as cantfix.