https://github.com/uibcdf/evidence

Scientific Python libraries or scripts often work with data coming from a database, a scientific communication, or any other external source. These data, or "evidences", are then supported by external references. Wouldn't be useful to work with "evidences" in your code?
https://github.com/uibcdf/evidence

Last synced: 2 months ago
JSON representation

Scientific Python libraries or scripts often work with data coming from a database, a scientific communication, or any other external source. These data, or "evidences", are then supported by external references. Wouldn't be useful to work with "evidences" in your code?

• Host: GitHub
• URL: https://github.com/uibcdf/evidence
• Owner: uibcdf
• License: mit
• Created: 2021-09-24T00:53:02.000Z (over 3 years ago)
• Default Branch: main
• Last Pushed: 2023-05-02T05:18:39.000Z (about 2 years ago)
• Last Synced: 2025-01-23T03:14:16.876Z (4 months ago)
• Language: Python
• Homepage: https://www.uibcdf.org/evidence
• Size: 2.74 MB
• Stars: 1
• Watchers: 2
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • Contributing: .github/CONTRIBUTING.md
  • License: LICENSE
  • Code of conduct: CODE_OF_CONDUCT.md

Awesome Lists containing this project

README

        
# Evidence

Scientific Python libraries or scripts often work with data coming from a database, a scientific communication, or any other external source.  These data, or "evidences", are then supported by external references. And these references should walk attached to the value of these evidences through your code. To this aim, this library provides a python object named `Evidence`. Have a look at xxx see how it works.