Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Keep license file name from source distribution

See original GitHub issue

Issue Description

I noticed when creating a recipe that the upstream repo named the license file LICENSE.md and grayskull made a copy called LICENSE. It might be useful to match the naming convention in the upstream repo so that when the license file is eventually included in the upstream repo, there is no need to make changes to the meta.yaml in addition to deleting the manually packaged copy.

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:6 (4 by maintainers)

Top GitHub Comments

1reaction

synapticarborscommented, Apr 22, 2020

The pypi package is respx

0reactions

marcelotrevisanicommented, Apr 23, 2020

* Is there any way to get grayskull to pull the `dev_url` from pypi, or figure out a better `home` than the pypi url? For example, looking for the `url` in `setup` (https://github.com/lundberg/respx/blob/master/setup.py#L14)

I need to check it, but I think that grayskull tries to get it the dev_url first from the metadata, if it does not exist it uses the pypi. But I need to check it

* Is there an explanation of what `pip check` is doing in the context of a package built with `conda`? I've seen this coming up in a few places and I don't feel like I really understand what the caveats are of using this, if any.

pip check test if the whole dependencies of that package are installed, but sometimes it does not work well, but at least it is a second validation if it fails the user can just remove it. I think @ocefpaf can give you a better explanation about it

Top Results From Across the Web

setuptools doesn't install licenses · Issue #357

I've tried building a source distribution of my own package with a license_files option and installing it via pip install -U path\to\sdist.tar.gz and...

Does it matter what I name my open source license file?

If the license is one of the official open source licenses the official license name or its abbreviation may be explicated with the...

Do I really need to include a licence file for common ...

Of course, if you are distributing the source of a program that is licensed under one of these well-known licenses, then the license...

[Files] section

This parameter specifies a new name for the file when it is installed on the user's system. By default, Setup uses the name...

4. Creating a Source Distribution

Just like in the setup script, file and directory names in the manifest template should always be slash-separated; the Distutils will take care...