Sounds like pywincffi should fix that issue....I'm planning on distributing binary wheels which pip and setuptools should be able to install like any other dependency. I can make sure to build other formats (exe, msi, egg, etc) if it helps though the binary wheels should be enough to avoid the same installation issues pywin32 has in most cases. Is Tahoe's packaging going to require anything special that I should account for or will Twisted depending on pywincffi work for Tahoe?
On Tue, Jan 12, 2016 at 8:44 PM, Zooko Wilcox-O'Hearn <zoo...@gmail.com> wrote: > FYI, this would, if it were compatible with Tahoe's packaging, fix > these outstanding issues for Tahoe: > > * https://tahoe-lafs.org/trac/tahoe-lafs/ticket/142# pywin32 can't be > installed automatically > > * https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2028# Twisted > endpoints introduce a dependency on pywin32 > > Sincerely, > > Zooko > > _______________________________________________ > Twisted-Python mailing list > Twisted-Python@twistedmatrix.com > http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python >
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python