pypa / pypa/setuptools

Can't find dependency_links.txt

Open
#365 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug major
Dominant language
Python
Stars
2.9k
Forks
1.4k
Avg merge
1d 1h
Merged PRs (30d)
1

Description

Originally reported by: ishakir (Bitbucket: ishakir, GitHub: ishakir)


I'm calling setup.py from ant:

<exec executable="python" failonerror="true">
    <arg value="setup.py"/>
    <arg value="sdist"/>
    <arg value="--format=gztar"/>
</exec>

setup.py contains (among other things)

from distutils.core import setup
from setuptools import find_packages

setup(
    name=name,
    version="0.1.07",

    description="Some description",
    author="Some author",
    author_email="someone@company.com",

    packages=find_packages(source_directory),
    package_dir={"": source_directory},

    install_requires=[]
)

I'll post the most relevant part of the logs below to demonstrate what the problem is:

 [exec] C:\Python27\Lib\site-packages\setuptools\dist.py:282: UserWarning: Normalizing '0.1.07' to '0.1.7'
 [exec] running sdist
 [exec] running egg_info
 [exec] writing dependency_links to python\project_name_branch.egg-info\dependency_links.txt
 [exec] running check
 [exec] copying python\project_name_branch.egg-info\dependency_links.txt -> project_name@branch-version\python\project_name_branch.egg-info
 [exec] error: [Errno 2] No such file or directory: 'project_name@branch-verison\\python\\project_name_branch.egg-info\\dependency_links.txt'

And then the python process bombs out. This seems very strange to me as it should create the file, copy it and then find it later on! The dependency_link.txt file is empty as you might expect! This is causing my deployments to fail - surely the dependency_links.txt file should be there when it bombs out!

I'm on Windows 64-bit and am running 64-bit versions of the libraries where appropriate, am happy to provide more info, just not sure what would be helpful at this stage!


Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the Windows failure by running the shown setup.py sdist --format=gztar command, then inspect the egg_info and sdist steps around dependency_links.txt. Compare the generated path with the destination path in the log; done means the source distribution completes without the missing-file error.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.