> I too am a pydev user. OK, the auto_completion issues isn't a problem > when using wildcard imports, but this effectively forces us to use > wildcard imports which is ... unpythonic!
True. Can't argue against that. >> Doing the namespaces differently is non trivial, > > I'm not proposing to change the name-spaces, but to rename classes to > remove the prefix (on the grounds that it is redundant information, > given that all classes live in their appropriate package name- > space). If > I am unable to provide a straightforward patch for this, I'll withdraw > the idea! That's a good idea. I've thought of the issue too, but haven't yet figured out simple & effective solution for it. So, if you can be of help, all the better Bryan. If you can think of something without touching __import__ magic, well, then wonderful. It could be cool if the SVN version could be build like: python setup.py build --noprefix That way we can delay enforcing this renaming until 0.3 ( Thomas, what do you think, is that reasonable? ) > Does this mean your against the proposal? I'd appreciate it if you can > give a clear statement of your views (e.g. -1,0,+1 etc.). +1 You guys are right: the cleaner the better. Though it impacts existing code, so this decision needs to be final. The slightly embarrassing thing would be that 0.1 ( import OCC ) 0.2 ( from OCC.BRep import * ) and 0.3 ( from OCC import BRep ) are all different... This renaming decision therefore *has* to be final ;') Of course 0.2 -> 0.3 renaming would be especially trivial, still it can be a nuisance. > I'll accept the overall consensus. I just want to be sure this topic > is > debated now, because as the number of pythonOCC users increases it > will > soon become impossible to change. You're absolutely spot on. Though Thomas view on this outweighs mine; he'll have to do the hard work ;') Cheers, -jelle _______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
