pywin32 can't be installed automatically #142
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#142
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
(https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1799934&group_id=78018)
bumping this problem out to milestone 0.7.0
We need to choose a manageable subset of desired improvements for v0.7.1, scheduled for two week hence, so I'm bumping this one into v0.7.2, scheduled for mid-December.
Hooray! Philip J. Eby found a bug in setuptools that was causing this problem:
http://mail.python.org/pipermail/distutils-sig/2008-March/008867.html
setuptools 0.6c8 doesn't have the patch that makes it able to handle pywin32, but the current unreleased SVN of setuptools has.
Here is the ticket on the setuptools issue tracker:
http://bugs.python.org/setuptools/issue18
This has been fixed, but pywin32 isn't hosted on pypi so it isn't automatically downloaded by easy_install. However, we can host our own copies, e.g. http://testgrid.allmydata.org:3567/uri/URI%3ADIR2-RO%3Asnrfwfxatrci35zdgjnzxxx2ke%3Aunarxv347edtku3xzmefy4mcdmfngxzeb72iyqcadbjzjpczjx5a/
The ticket asking the pywin32 folks to post packages (or links) on pypi is https://sourceforge.net/tracker2/?func=detail&aid=1799934&group_id=78018&atid=551954
Closing this ticket.
Whoops, I don't think pywin32 and the latest setuptools/zetuptoolz work after all.
See also ticket #756 (if pywin32 has been manually installed, setuptools still doesn't detect it).
Setuptools is being eclipsed by a vigorously developed fork of setuptools named "distribute". There is one ticket open in their issue tracker which mentions pywin32. Perhaps the maintainers of distribute would like to make sure that pywin32 is installable with their tool.
(Distribute is backwards-compatible with setuptools so we could switch over to distribute without too much difficulty.)
Okay, I found a helpful person on #distutils IRC channel who tried to easy_install pywin32 using distribute 0.6.10. The results are:
There is also an independent problem that the pywin32 files are not linked from pypi.python.org so setuptools will not find them to auto-download them unless we add an entry to
find_links
in source:setup.cfg. (Possibly that entry should be<http://sourceforge.net/projects/pywin32/files/>
but I'm not sure if sourceforge's mirroring scheme will defeat setuptools's auto-downloading scheme.) Alternately we could host copies of the pywin32 packages on a Tahoe-LAFS grid and put the URL of that intofind_links
. :-)I'm pursuing http://bitbucket.org/tarek/distribute/issue/140/compile-from-source-of-pywin32-failed , which looks like it might be related to #756.
(@@http://www.mail-archive.com/python-win32@python.org/msg05269.html@@)
I work for a company called Enthought who also ships a Python Distribution(EPD) which includes an 'egg' version of pywin32 that someone could easy_install. The entire distribution is free, but unfortunately there is an annual fee to access the egg repository for individual packages. However, I would be more than willing to help you get started with using setuptools and creating an egg for pywin32 :). Even if the pywin32 project doesn't upload the egg to PyPi, there is still another way through setuptools to make a single install step for your users.
See also #1093 (win32 build hell).
See also #1274 (eliminate pywin32 dependency).
No longer required.
Reopening because of #2028 (Twisted endpoints introduce a dependency on pywin32).
#2247 was a duplicate of this.
This interacts with https://github.com/twisted/nevow/issues/43 (why does Nevow depend on Twisted >= 13.0?).
Here's a feature request that might help: http://sourceforge.net/p/pywin32/bugs/669/
Replying to zooko:
No, #2247 is to document the dependency on pywin32, which isn't the same proposed solution as this, so not a duplicate.
This has increased in urgency because the Magic Folder code depends on Twisted >= 15.2.0 even on Windows (see #2518), and Twisted depends on pywin32. The previous workaround we were using of depending only on Twisted >= 11.1.0, <= 12.1.0 for Windows (when pywin32 is not already installed) is no longer tenable.
pywin32 can't be installed with setuptoolsto pywin32 can't be installed automaticallyThis is dependent on the zetuptoolzectomy (#1582), so that we can use the binary wheels from pypiwin32.
Milestone renamed
We now depend upon
pypiwin32
, which is the PyPI-hosted pip-installable version ofpywin32
. Problem resolved.