loggerhead doesn't work with the bzr standalone win32 installer; should be included in it

I think you can fix this by separately installing the Python paste package.

As far as the installer goes the options seem to be:

1- include loggerhead (and also paste) in the bzr installer
2- make a separate loggerhead installer
3- encourage people to use eg easy_setup to install it

"I think you can fix this by separately installing the Python paste
package."

But since I don't actually have a 'standalone' installation of Python - only the underlying components supplied by the Windows binary (.exe) installer for Bazaar 1.16 - it isn't obvious to me how I would meaningfully install the Python paste package. I guess that relevant bits of it need to go into the bzrlib shipped with bzr? Can you specify what needs to be done, please?

Or is the conclusion that this plugin is not presently compatible with the .exe Windows installer version of bzr?

The search facility on the bzr home page does not return any results for 'easy_setup' - can you say whether that mechanism would be Windows installer compatible?

I haven't actually installed loggerhead on Windows so I may be wrong,
but I think that until it's included in the bzr overall installer you
will have to install it manually, ie: install Python, install bzr,
paste, and loggerhead.

2009/6/22 David Roberts <email address hidden>:
> "I think you can fix this by separately installing the Python paste
> package."
>
> But since I don't actually have a 'standalone' installation of Python -
> only the underlying components supplied by the Windows binary (.exe)
> installer for Bazaar 1.16 - it isn't obvious to me how I would
> meaningfully install the Python paste package. I guess that relevant
> bits of it need to go into the bzrlib shipped with bzr? Can you specify
> what needs to be done, please?
>
> Or is the conclusion that this plugin is not presently compatible with
> the .exe Windows installer version of bzr?

It seems that plugins which depend on separately-installed libraries,
as loggerhead does for paste, can't be used with the all-in-one
installer.

--
Martin <http://launchpad.net/~mbp/>

I can see the problem, but don't know enough about how the bzr packaging works on windows to know how to fix it.

Including loggerhead and dependencies in the installer may make sense, they're all fairly small.

Filing against bzr because mwh says it could be included in the installer.

On Tue, 2009-06-30 at 01:29 +0000, Martin Pool wrote:
> Filing against bzr because mwh says it could be included in the
> installer.

What about just having a loggerhead installer, like xmloutput has?

-Rob

2009/6/30 Robert Collins <email address hidden>:
> On Tue, 2009-06-30 at 01:29 +0000, Martin Pool wrote:
>> Filing against bzr because mwh says it could be included in the
>> installer.
>
> What about just having a loggerhead installer, like xmloutput has?

If it works with both bzr installers that would be ok, but if it's
feasible to package it together that may be better.

--
Martin <http://launchpad.net/~mbp/>

...
 File "pkg_resources.pyo", line 524, in resolve
DistributionNotFound: Paste>=1.6

IIUC this error is a clear sign that some parts either of loggerhead or third-party library requires setuptools to work correctly. AFAIK, py2exed application (bzr.exe) can't work with setuptools and eggs properly. So this is dead end.

David, you'd better install python-based bzr version and then install all required dependencies.
See http://bazaar-vcs.org/WindowsInstall

Alexander Belchenko wrote:
> ...
> File "pkg_resources.pyo", line 524, in resolve
> DistributionNotFound: Paste>=1.6
>
> IIUC this error is a clear sign that some parts either of loggerhead or
> third-party library requires setuptools to work correctly. AFAIK,
> py2exed application (bzr.exe) can't work with setuptools and eggs
> properly. So this is dead end.

I don't know the details, but Loggerhead isn't compatible with old
versions of Paste and PasteDeploy, so it uses setuptools's pkg_resources
to make sure they're new enough. (Paste doesn't have many __version__
attributes, so that seems to be the best way to do it.)

It also uses pkg_resources for reporting the version numbers of its
dependencies and accessing some files included in the distribution.

Patches welcome. :-D I'd be happy to lose that dependency, but I don't
know how to do it.

As it is, it might be possible for the installer to use a patched
version of Loggerhead that removes the dependency. It would be easy to
do, as long as pkg_resources.resource_filename() can be replaced.