OK, if it makes a difference for tools (and security updates), let's
try to keep it. (*grumble*)

*But* given its too-generic name, can we add a big bold comment header
to the file explaining what it is?
Some quick searching suggests lines starting with # are ignored, so
hopefully this should be possible?

Best Regards,

Leif

On Tue, Oct 29, 2019 at 07:52:48PM -0700, Sean via Groups.Io wrote:
> It is a convention for projects using python.  It definitely isn't required 
> but there are some features that come for free when using that filename.
> 
> https://github.blog/2018-07-12-security-vulnerability-alerts-for-python/
> and
> https://help.github.com/en/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on
> 
> You can also get more insight from github into dependencies and dependents.
> example: 
> https://github.com/tianocore/edk2-pytool-extensions/network/dependencies
> 
> I did notice on the example from above that github picked up the 
> requirements.publisher.txt so i don't know what their pattern matching does 
> exactly.
> 
> 
> 

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#49622): https://edk2.groups.io/g/devel/message/49622
Mute This Topic: https://groups.io/mt/39614157/21656
Group Owner: devel+ow...@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to