Hello! I don't know why the issues are not enabled at https://bitbucket.org/logilab/logilab-common/overview
After all, bug trackers are better at tracking bugs than inboxes. Anyway, running "python setup.py develop" in logilab-common succeeds, but the result is not satisfactory. pylint (run without arguments) reports: ImportError: No module named logilab.common.decorators I understand that nobody is actively developing logilab-common. However, the "develop" function should either work properly or fail at the install time. There are good reasons to support "develop". Somebody may want to add debug statements to the code while trying to understand how the code works or debug an issue. It's better not to worry whether the debugging code has been installed after each change. I believe logilab-common should be restructured to have the source directory hierarchy correspond to the installed hierarchy. That probably means moving code from the top level directory to logilab/common. I know, it's intrusive, but it would make the code developer-friendly, which might pay off in the the long term. -- Regards, Pavel Roskin _______________________________________________ Python-Projects mailing list Python-Projects@lists.logilab.org https://lists.logilab.org/mailman/listinfo/python-projects
