Skip to content
This repository was archived by the owner on Apr 14, 2022. It is now read-only.

[WIP]: Split analysis into several assemblies #441

Closed
wants to merge 30 commits into from
Closed

[WIP]: Split analysis into several assemblies #441

wants to merge 30 commits into from

Conversation

MikhailArkhipov
Copy link

Fixes #257

Microsoft.Python.Core - common objects usable in many places
Microsoft.Python.Parsing - Python parser and AST
Microsoft.Python.Analysis.Engine - current DDG analysis
Microsoft.Python.Analysis.Ast - AST analysis

Reasoning: TDD development of the AST based analysis. Having separate assembly for AST analysis allows development of the DDG replacement without having to remove DDG first. DDG can continue to be used until we have sufficient test bed for the AST analysis to prove it is ready for the prime time.

Based on #439.

Still TODO: separate fluent classes for AST analysis since current one use definitions specific to DDG. Therefore tests for both AST and DDG analysis may have to stay in the same assembly for a while.

@AlexanderSher
Copy link
Contributor

Ok, I'll have a huge merge for this...

@MikhailArkhipov
Copy link
Author

No, if this go in, it will happen after earlier PR which is intended for after your imports.

@MikhailArkhipov MikhailArkhipov deleted the analysis3 branch December 28, 2018 17:14
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants