Pipfile.lock
E428635
Pipfile.lock is a lockfile generated by Pipenv that records exact versions and hashes of Python package dependencies to ensure reproducible environments.
All labels observed (1)
| Label | Occurrences |
|---|---|
| Pipfile.lock canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T4278265 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
Target entity: Pipfile.lock Context triple: [Pipenv, usesFileFormat, Pipfile.lock]
-
A.
Pipfile
Pipfile is a configuration file used by Python’s Pipenv tool to declare a project’s package dependencies and related environment settings.
-
B.
Pipenv
Pipenv is a Python packaging and dependency management tool that combines virtual environment handling with a Pipfile-based workflow to simplify and standardize project setup.
-
C.
PEP 621 (project metadata in pyproject.toml, partially)
PEP 621 is a Python packaging standard that defines a standardized way to declare project metadata in the `pyproject.toml` file.
-
D.
PEP 517
PEP 517 is a Python packaging standard that defines a build-system independent interface for building Python project distributions.
-
E.
PEP 503
PEP 503 is a Python Enhancement Proposal that defines the simple repository API used by package installers like pip to discover and download Python packages.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: Pipfile.lock Target entity description: Pipfile.lock is a lockfile generated by Pipenv that records exact versions and hashes of Python package dependencies to ensure reproducible environments.
-
A.
Pipfile
Pipfile is a configuration file used by Python’s Pipenv tool to declare a project’s package dependencies and related environment settings.
-
B.
Pipenv
Pipenv is a Python packaging and dependency management tool that combines virtual environment handling with a Pipfile-based workflow to simplify and standardize project setup.
-
C.
PEP 621 (project metadata in pyproject.toml, partially)
PEP 621 is a Python packaging standard that defines a standardized way to declare project metadata in the `pyproject.toml` file.
-
D.
PEP 517
PEP 517 is a Python packaging standard that defines a build-system independent interface for building Python project distributions.
-
E.
PEP 503
PEP 503 is a Python Enhancement Proposal that defines the simple repository API used by package installers like pip to discover and download Python packages.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
configuration file
ⓘ
lockfile ⓘ |
| _metaSectionIncludes |
hash of Pipfile
ⓘ
pipenv version ⓘ requires information ⓘ |
| associatedWithFile | Pipfile ⓘ |
| belongsToEcosystem | Python packaging ⓘ |
| compatibleWith | pip ⓘ |
| containsSection |
_meta
ⓘ
default ⓘ develop ⓘ |
| controls | exact dependency resolution ⓘ |
| defaultSectionContains | runtime dependencies ⓘ |
| developSectionContains | development dependencies ⓘ |
| discourages | installing unpinned versions ⓘ |
| eachDependencyEntryIncludes |
hashes list
ⓘ
index information ⓘ markers ⓘ version specifier ⓘ |
| ecosystemRole | dependency lock specification for Pipenv ⓘ |
| ensures | same dependency tree across installations ⓘ |
| fileExtension | .lock ⓘ |
| generatedBy | pipenv lock ⓘ |
| hashesAre | cryptographic hashes of distributions ⓘ |
| introducedBy | Pipenv project ⓘ |
| livesIn | project root directory ⓘ |
| maintainedBy | project developers ⓘ |
| primaryPurpose | ensure reproducible Python environments ⓘ |
| readBy | Pipenv resolver NERFINISHED ⓘ |
| records |
Python package dependencies
ⓘ
dependency hashes ⓘ exact dependency versions ⓘ |
| regeneratedWhen | dependencies change in Pipfile ⓘ |
| similarTo |
Pipfile.lock in other languages’ ecosystems
ⓘ
package-lock.json ⓘ poetry.lock ⓘ |
| supports |
deterministic builds
ⓘ
environment reproducibility ⓘ |
| usedByCommand |
pipenv install
ⓘ
pipenv sync ⓘ pipenv update ⓘ |
| usedFor |
pinning transitive dependencies
ⓘ
sharing exact environments across machines ⓘ verifying package integrity ⓘ |
| usedInWorkflow |
CI environments
ⓘ
deployment of Python applications ⓘ |
| usedWith | Pipenv NERFINISHED ⓘ |
| writtenInFormat | JSON NERFINISHED ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Subject: Pipfile.lock Description of subject: Pipfile.lock is a lockfile generated by Pipenv that records exact versions and hashes of Python package dependencies to ensure reproducible environments.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.