Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=6442316 By: fabioz
Ok, I was thinking a bit about it, and I think that the way to handle that is adding it somewhere outside of the pydev project and just reference it as an external source folder. For that, you can either create a separate project to be added to the svn only with those files and don't mark it as a Pydev project, and in the project you're referencing, add it as an external source folder or simply add it to your site-packages (and add that to svn). The point is, it should be treated as something totally external to Pydev, as it's not really source code and not meant to be edited and managed internally by Pydev (anything in your project pythonpath is treated as if it was part of something you're developing, not something external -- and when you're developing, I don't think you ever want to keep your .pyc files floating around unless you actually have its source -- that can lead to some subtle and unexpected bugs) Cheers, Fabio ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=293649 ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Pydev-users mailing list Pydev-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pydev-users
