if pywin32 has been manually installed, setuptools still doesn't detect it #756
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
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#756
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?
If I add
pywin32
to source:_auto_deps.py and install the "pywin32-214.win32-py2.5.exe" file from http://sourceforge.net/projects/pywin32/ , then the following weirdness occurs:...
So, pkg_resources says it is there, but setuptools doesn't consider the requirement to be already satisfied.
Is this another instance of http://bugs.python.org/setuptools/issue17 (easy_install will install a package that is already there)?
I made a minimal version of this. Put the following into a file named
setup.py
in a new empty directory:Then run the following command:
It will say something like:
...
I updated http://bugs.python.org/setuptools/issue17 (easy_install will install a package that is already there) with the minimal test case from #comment:72001.
Note that once #668 is resolved, switching to Distribute, this issue may or may not be resolved as a result.
(http://bugs.python.org/setuptools/issue17) claims that this issue was fixed in setuptools-0.6c10. We currently have a version (variant) of setuptools which is newer than and derived from 0.6c10 in our build system so if it is true that this was fixed (and if the distribute tool that we intend to switch to soon also has the fix) then we can close this ticket.
See also #1274 (eliminate pywin32 dependency).
This is invalid given that we're about to eliminate the pywin32 dependency completely (in http://tahoe-lafs.org/trac/tahoe-lafs/attachment/ticket/1435/dependency-updates.darcs.patch).