2

Closed

"File/New/Project From Existing Code..." improvements

description

When using File/New/Project From Existing Code... to move an older Python project into PTVS the menu command includes all *.pyc files found in the target folder. They don't need to be (and probably shouldn't be) part of the solution. The Project From Existing Code command should ignore those files.

List:
should ignore *.pyc files
Should support multiple project types (e.g. new Django project)
Closed Oct 19, 2012 at 11:14 PM by Ptools

comments

dinov wrote Dec 12, 2011 at 9:09 PM

Fixed for the next release - http://pytools.codeplex.com/SourceControl/changeset/changes/3b108df3126a
We were doing the right thing for subdirs, but VS was controllilng the addition of files in the top-level folder. I've added a small hack which prevents VS from adding non-.py/.pyw files.

joxn wrote Jan 4, 2012 at 8:41 PM

I'm reopening this bug because the fix caused issue http://pytools.codeplex.com/workitem/628 -- we have to revert the current fix and try something else, or decide we can't fix it.

apeters wrote Feb 14, 2012 at 6:30 PM

I would also add that it should ignore .svn folders and related files

Zooba wrote Sep 11, 2012 at 5:10 PM

Changed this significantly - http://pytools.codeplex.com/SourceControl/changeset/a8d12570c484

I've assigned this to myself to add support for:
  • folder filtering (though I think .svn and .hg folders will be fine, since their contents will very rarely match the extension filter)
  • flavored project selection