Comments (1)
The signals import was removed because it wasn't used. I don't want it to be removed though, as the import has intentional side effects.
Removing unused import is an intentional behavior. rope can't know that you intend to use an import just for its side effect. Once we've implemented __all__
(#8) you can add the imported lines there to prevent it from being removed. It would also be reasonable if user can add a special comment markers (e.g. # rope: keep-unused-import
) on imports lines to prevent rope from removing them during reorganization. I've separated that to a separate ticket (#368).
The User import was removed even though the User module is used in the code.
There is not enough info to reproduce this issue. Please open a new ticket if you find specific scenarios where rope removed imports that it shouldn't have.
from rope.
Related Issues (20)
- Inline method refactoring changes variables names after applying the transformation
- Inline method refactoring passes the wrong parameter to the inlined function body
- Rename Field refactoring allows you to rename a field with the same name used in a global method HOT 1
- Rename Field refactoring allows you to use the name of special methods as a new name HOT 1
- Rename Field refactoring allows the use of declared method names as new field names HOT 1
- Rename Field refactoring allows the use of a name that can not be iterable HOT 1
- Rename Field refactoring allows you to rename a class field with class method names HOT 1
- Rename Field refactoring allows you to rename a local field with the method name HOT 1
- Rename Field refactoring allows you to change the method parameter, causing inconsistent override
- Rename Method refactoring allows the use of previously declared field name HOT 1
- Rename Method refactoring allows you to rename a method to a name with an 'internal use' indicator HOT 1
- Rename Method refactoring does not change the name of the super method in the classes that override it
- Rename Method refactoring is allowed in methods of the descriptor protocol
- Rename Method refactoring does not change the calls of the renamed method.
- Rename Method refactoring allowed for methods designed for numeric type emulation
- Rename Method refactoring does not rename all implementations of an abstract method
- Rename Method refactoring allowed for methods defined to implement container objects
- Rename Method refactoring allows you to rename a nested method with a parameter name HOT 1
- Rename refactoring should check whether the target variable exists
- Tests that uses external_fixturepkg shoud run in their own venv
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rope.