Deprecating include_defs.
See original GitHub issueinclude_defs function leads to namespace pollution, makes it hard to remove unused imports and as such has been superseded by load.
Its documentation has already been suggesting usage of load
, but its status will be changed to deprecated and it will be completely removed in a month.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:5
- Comments:7 (7 by maintainers)
Top Results From Across the Web
What is deprecated in IT? - TechTarget
In information technology (IT), deprecation means that although something is available or allowed, it is not recommended or that -- in the case...
Read more >definition of deprecating by The Free Dictionary
1. To express disapproval of; deplore. 2. To belittle; depreciate. 3. Computers To mark (a component of a software standard) as obsolete to...
Read more >Deprecation - Wikipedia
In several fields, especially computing, deprecation is the discouragement of use of some terminology, feature, design, or practice, typically because it ...
Read more >DEPRECATE | definition in the Cambridge English Dictionary
deprecate verb (NOT VALUE) to say that you think something is of little value or importance: He always deprecates my achievements.
Read more >What is Deprecated? - Definition from Techopedia
Deprecated refers to a software or programming language feature that is tolerated or supported but not recommended. A deprecated attribute or ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@kageiit,
buildfile.includes
continues to work for Python DSL and since Python DSL is in a maintenance-only mode there are no plans to change this.I understand about skylark. But if a project is still using polyglot parsing and is in the process of migration, its important that the functionality of
buildfile.includes
still works