Menu

when will pydev support symbolic links?

Dan Keefe
2009-03-17
2013-03-15
  • Dan Keefe

    Dan Keefe - 2009-03-17

    I read in a forum message (somewhere) in 2007 that pyDev support for symbolic links would be available in the next release.  Doesn't seem to work in the version I just downloaded though.  (The most recent).  I mean, I can create projects with modules that are symbolic links, but building doesn't catch any errors, I have to actually run.  (This might be a pydev Extentions problem, I'm not sure where pyDev stops and pyDev extensions picks up...)

    So ... am I missing something or is this still a work in progress?

    Thanks!
    Dan

     
    • Fabio Zadrozny

      Fabio Zadrozny - 2009-03-17

      What exactly is not working?

      Symbolic links should be supported (note that this is related to links created from your filesystem, not the links created from the eclipse linking system -- for the eclipse linking, only source folders or folders higher in the structure are supported, not inside your source folders).

      If there actually is a problem, it's probably in Pydev (Pydev Extensions makes use of the type inference provided by Pydev, so, code-completion would also not work if it doesn't work in Pydev Extensions).

      Cheers,

      Fabio

       
    • Dan Keefe

      Dan Keefe - 2009-03-17

      Well, here is my scenario.  I create a symbolic link in my workspace folder (on the filesystem -- Redat Linux) to a python module.  Inside eclipse, pyDev handles the file just fine; I can view it, modify it, save it and so forth.   However, what does not work is the build errors.  It's like building doesn't do anything at all.  I'm not sure how this works under the hood, whether the python interpreter is run line by line and errors are spit out or if it is some other magical process, but I never get errors in the symbolically linked file.

      For instance, lets say I have a file that is symbolically linked called whatever.py and it's contents are:

      print "Hello World"
      blabla

      I never get a build error on the line blabla.  However, when I run, I do get the expected error. (NameError: blabla is not defined)

      Now, ff the file is not symbolically linked, I get a build error; namely, Undefined Variable: blabla.

      So, I've never run without Pydev Extensions, so I'm not sure if PyDev alone would give me the build error.  And code completion is working so I guess PyDev extensions isn't the problem?

      Finally, let me admit that I lied a little in the above post.  I actually can get some errors to come out of a symbolically linked file (I've played around a little) but they are all of the form "Encountered \n at line<>" which happens whenever I place a python keyword without the expected follow on text.  For example:

      import

      -- This gives that error.  So, I do get some errors but never the 'undefined variable' type.

      Thanks,
      Dan

       
      • Fabio Zadrozny

        Fabio Zadrozny - 2009-03-17

        Ok, so, you're getting the syntax errors (which is from Pydev), and not the analysis errors (which are from the extensions)...

        I know links should be working when configuring the interpreter, but I haven't actually got to the point of configuring links to work inside of the source folder... (it's not really common to use them there as it is in other places). I think that what is probably happening is that it's resolving the link to the 'real' location and as the real location is not in the pythonpath it doesn't analyze that file.

        Can you report that as a bug? I have to take a better look at what's actually happening there.

        Cheers,

        Fabio