Bug 155583 - Implement includes/excludes (Mercurial)
Implement includes/excludes (Mercurial)
Status: CLOSED INVALID
Product: python
Classification: Unclassified
Component: Projects
6.x
All All
: P3 (vote)
: TBD
Assigned To: Lou Dasaro
nbpythonqa
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-12-16 17:12 UTC by Jesse Glick
Modified: 2017-06-23 08:06 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2008-12-16 17:12:57 UTC
If I try to set up Mercurial sources as a NB project, my first instinct is to add the root folder as a source folder.
Unfortunately this then means that the build dir is scanned and offered in e.g. Find Usages, which I definitely do not
want. There is no way to exclude it.

I can instead add mercurial/ and hgext/ folders as source folders. This works tolerably well, but it gets the import
path wrong: $PYTHONPATH when running the app should be the root folder. For example, if I Go to Type and enter
"localrepository", it offers "localrepo.localrepository", whereas it should be showing
"mercurial.localrepo.localrepository". Of course, with Python doing such dynamic name lookups, it is not clear whether
the root module namespace is very meaningful.
Comment 1 Jenselme 2017-06-22 21:31:20 UTC
Not sure it is still relevant with the current version. Closing this as old bug. If this is still a thing, please reopen and accept my apologies.
Comment 2 Jiri Kovalsky 2017-06-23 08:06:05 UTC
Thanks for your evaluation Julien. Reporter, if you think your issue is still valid and needs to be addressed, don't hesitate to reopen it with additional information. Closing for now.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo