License clarification

Open
#21 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

Inspect the package metadata shown in the issue and compare its MIT declaration with mit.LICENSE and the Apache-2.0 license file in the repository. Confirm the intended licensing with a maintainer; the issue is done when the metadata and license files consistently document the approved license.

Written by the indexing model from the issue text.

Description

Hi,

The metadata says MIT:

[metadata]
name = pip-requirements-parser
license = MIT

# description must be on ONE line https://github.com/pypa/setuptools/issues/1390
description = pip requirements parser - a mostly correct pip requirements parsing library because it uses pip's own code.
long_description = file:README.rst
long_description_content_type = text/x-rst
url = https://github.com/nexB/pip-requirements-parser

author = The pip authors, nexB. Inc. and others
author_email = [email protected]

classifiers =
    Development Status :: 5 - Production/Stable
    Intended Audience :: Developers
    Programming Language :: Python :: 3
    Programming Language :: Python :: 3 :: Only
    Topic :: Software Development
    Topic :: Utilities

keywords =
    utilities pip requirements parser dependencies pypi

license_files =
    mit.LICENSE
    AUTHORS.rst
    CHANGELOG.rst
    README.rst

but you also carry Apache-2.0 license file in the repo. Is this an error?

Thanks.

Dominant language
Python
Stars
20
Forks
17
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from aboutcode-org/pip-requirements-parser

All issues in aboutcode-org/pip-requirements-parser

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.