search

pyupio / dparse

A parser for Python dependency files
MIT License
61 stars 23 forks source link

track the section of the pipfile from where the dependency originated #18

Closed paulortman closed 6 years ago

paulortman commented 6 years ago

For a project where I'd like to use dparse to work with Pipfiles and Pipfile.locks, I'd really like to track the section of the Pipfile from where the dependencies originate.

The use case is that I want to only really care about those dependencies which are "packages", not "dev-packages" I added a new dependencies attribute to track the data as I couldn't determine a better place to stuff it, thus my modifications below.

Thanks for the dparse library, it's saved me a fair bit of time already.

codecov[bot] commented 6 years ago

Codecov Report

Merging #18 into master will decrease coverage by 0.12%. The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master      #18      +/-   ##
==========================================
- Coverage   97.49%   97.36%   -0.13%     
==========================================
  Files          11       11              
  Lines         758      759       +1     
==========================================
  Hits          739      739              
- Misses         19       20       +1
Impacted Files Coverage Δ
dparse/parser.py 95.55% <100%> (+0.02%) :arrow_up:
dparse/updater.py 87.5% <0%> (-1.57%) :arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 8149c92...b38113d. Read the comment docs.

jayfk commented 6 years ago

Thanks, that's great!