[bug fix]remove paddle.nn.Sequential to fix dygraph to static error #48477
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR types
Bug fixes
PR changes
APIs
Describe
In the previous work of cleaning
Sequential
under fluid, due to the problem of circular dependency, I copied a copy ofSequential
and put it under paddle.nn, and kept the originalSequential
under fluid.In dygraph to static,
paddle.fluid.dygraph.dygraph_to_static.convert_call_func.py
importspaddle.fluid.dygraph.container.Sequential
under fluid on line 27, and performs type judgment on lines 48 and 131, which will lead to an obscure problem. Usepaddle.nn.Sequential
models will not be able to perform dygraph and static conversions correctly.So we remove the Sequential under paddle.nn, and will migrate it back after the dygraph to static migration is completed.