On top of that in Visual Studio 2013 and higher variations, by including get; established; you can easily see all references to that house. That will help solve this issue, often operate requirements.txt on only area packages. By community packages I imply packages which are only in your venture