Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Currently some packages can't be analyzed. #48

Closed
Masara opened this issue Dec 7, 2023 · 1 comment · Fixed by #51
Closed

Currently some packages can't be analyzed. #48

Masara opened this issue Dec 7, 2023 · 1 comment · Fixed by #51
Assignees
@Masara
Labels
bug 🪲 Something isn't working released Included in a release

Comments

@Masara
Copy link
Contributor

Masara commented Dec 7, 2023

Describe the bug

Some packages can't be analyzed because currently the mypy data can't be extracted correctly. The function _get_mypy_ast() creates dictionary keys to get the data from mypy for our package, but these keys are currently not created correctly.

To Reproduce

Try to analyze the Library package. A bug will appear in the _get_api.py file for the _get_mypy_ast function.

Expected behavior

No bugs should appear and stubs should be created.

Screenshots (optional)

No response

Additional Context (optional)

No response
@Masara Masara added the bug 🪲 Something isn't working label Dec 7, 2023
@Masara Masara self-assigned this Dec 7, 2023
@Masara Masara moved this from Backlog to In Progress in Library Analysis Dec 10, 2023
@Masara Masara mentioned this issue Dec 10, 2023
Merged
@Masara Masara linked a pull request Dec 10, 2023 that will close this issue
fix: Some packages couldn't be analyzed #51
Merged
lars-reimann pushed a commit that referenced this issue Feb 21, 2024
@Masara @megalinter-bot
fix: Some packages couldn't be analyzed (#51)
fa3d020 
Closes #48

### Summary of Changes
* Fixed the bug where some packages couldn't be analyzed because the
Mypy build result could not be parsed from our side.
* Added TypeVarType as a _types.py class for type variables.
* Some bug fixes and refactoring

---------

Co-authored-by: megalinter-bot <129584137+megalinter-bot@users.noreply.github.com>
@github-project-automation github-project-automation bot moved this from In Progress to ✔️ Done in Library Analysis Feb 21, 2024
lars-reimann pushed a commit that referenced this issue Mar 29, 2024
@semantic-release-bot
chore(release): 0.2.0 [skip ci]
81b9b1d 
## [0.2.0](v0.1.0...v0.2.0) (2024-03-29)

### Features

* Added generation for Safe-DS stubs files ([#33](#33)) ([ab45b45](ab45b45))
* Correct stubs for TypeVars ([#67](#67)) ([df8c5c9](df8c5c9)), closes [#63](#63)
* Create stubs for public methods of inherited internal classes ([#69](#69)) ([71b38d7](71b38d7)), closes [#64](#64)
* Rework import generation for stubs. ([#50](#50)) ([216e179](216e179)), closes [#38](#38) [#24](#24) [#38](#38) [#24](#24)
* Safe-DS stubs also contain docstring information. ([#78](#78)) ([bdb43bd](bdb43bd))
* Stubs are created for referenced declarations in other packages ([#70](#70)) ([522f38d](522f38d)), closes [#66](#66)

### Bug Fixes

* Some packages couldn't be analyzed ([#51](#51)) ([fa3d020](fa3d020)), closes [#48](#48)
* Stub generation testing and fixing of miscellaneous bugs ([#76](#76)) ([97b0ab3](97b0ab3))
@lars-reimann
Copy link
Member

🎉 This issue has been resolved in version 0.2.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@lars-reimann lars-reimann added the released Included in a release label Mar 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Masara Masara

Labels
bug 🪲 Something isn't working released Included in a release
Projects
Library Analysis
Status: ✔️ Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: Some packages couldn't be analyzed Safe-DS/Stub-Generator
2 participants
@Masara @lars-reimann