Inspect4py 0.0.8: FIxing dataflow in macOS

This release produces a compatible .so version for macOS machines. The dataflow should now work correctly.

Thanks to @OEG-Clark, now the README includes instructions into generating a specific .so file.

What's Changed

• Data Flow Fix by @OEG-Clark in #422
• Dev by @dgarijo in #423

Full Changelog: v0.0.7...v0.0.8

Inspect4py 0.0.7: Adding dataflow functionalities

This release adds a new small feature: obtaining a dataflow for a function.
See the documentation (readme) to see its functionality.

Inspect4py 0.0.6: Bug fix in requirement extraction

This version fixes a small bug when extracting requirements of a repository if there is no access to the internet.

Inspect4py 0.0.5: Bug fix on output readme paths

This release fixes a small bug related to the accessibility of README files in the output generated by inspect4py.

Full Changelog: v0.0.4.1...v0.0.5

Inspect4py 0.0.4.1: Release bug fix

Same as https://github.com/SoftwareUnderstanding/inspect4py/releases/tag/v0.0.4 but fixing pypi pipeline

Inspect4py 0.0.4: Minor improvement to license retrieval

Small release to fix issues when retrieving a license. Also added contribution guidelines for the project.

New Contributors

• @WilliamsCJ made their first contribution in #396

Full Changelog: v0.0.3...v0.0.4

Inspect4py 0.0.3: Minor bug fixes

This version fixes minor bug fixes and prevents errors from cmdcfparser in Python 3.10 (the dependency has been removed)

Full Changelog: v0.0.2...v0.0.3

Inspect4py 0.0.2: Bug fixes and new features

This version of inspect4py:

• Automates package deployment.
• Adds multiple tests.
• Improves service description and classification
• Fixes installation errors
• Improves the detection and validation of tests.
• Function call improvements

Inspect4py 0.0.1: First release

First official release of inspect4py, which includes:

• Extraction of module dependencies
• Extraction of all functions in the code, including their documentation, parameters, accepted values, and call list.
• Extraction of all classes in the code, with all their methods and respective documentation
• Extraction of the control flow of each file.
• Extraction of the hierarchy of directories and files.
• Extraction the requirements used in the software project.
• Classification of which files are tests
• Classification of the main type of software project (script, package, library or service).
• Return a ranking of the different ways in which a a software component can be run, ordered by relevance.