Hi,
I've been using WAL-E for a few months for backups and recovery. It's
great!
WAL-E does, however, pull in 20 Python dependencies.* For an infrastructure
tool,
that's almost an unmanageably large number.
And thus it was a bit of a disappointment to see the new release
candidate (thanks for WALE_S3_ENDPOINT, btw!) introduce three more
dependencies through the use of python-daemon:
python-daemon>=1.5.2
setuptools (through python-daemon)
lockfile>=0.7 (through python-daemon)
The dependency on setuptools is particularly pernicious, since pretty
much all our virtualenvs are using distribute.
It seems like WAL-E only uses python-daemon in one place during
operator.backup.wal_restore(). Is there any chance that could be
refactored to use one of the various vendored daemon implementations?
Or, is there any chance you all could persuade the python-daemon
maintainer to update his install_requires so that it doesn't include
setuptools?
Thanks much,
HJB
* Although the readme says "It is possible to use WAL-E without the
dependencies of back-end storage one does not use installed: the imports
for those are only performed if the storage configuration demands their
use," I've never found an operationalizable way to install only the
packages I'd need. So I end up with half the OpenStack API libraries
and Azure, just in order to pull things from S3.
The list as of 0.7.2 was:
Babel==1.3
argparse==1.2.1
azure==0.8.2
boto==2.32.1
certifi==14.05.14
gevent==1.0.1
greenlet==0.4.3
iso8601==0.1.10
lxml==3.3.6
netaddr==0.7.12
oslo.config==1.3.0
pbr==0.10.0
prettytable==0.7.2
python-keystoneclient==0.10.1
python-swiftclient==2.2.0
pytz==2014.4
requests==2.4.0
simplejson==3.6.3
six==1.7.3
stevedore==0.14.1
wal-e==0.7.2
--
You received this message because you are subscribed to the Google Groups
"wal-e" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
