Jeff wrote: > The only thing I'd hate to lose is the ability to point VS at a folder > full of Python code and have it open and allow me to start hacking on > it. For the foreseeable future, most Python projects are not going to > include .pyproj files to make it easy. > > It doesn't matter how that's accomplished, as long as that use case is > still supported. Simple creating a pyproj containing everything would > be easiest (maybe excluding .pyc/.pyo). Or, it might be interesting to > parse setup.cfg, if it exists.
Does File->New->Project from Existing code address this for you (if it worked?) Or do you want something lighter weight than that? _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
