As a note, what I said should work in any remote machine (including a
container/docker/etc.), although it's just the first step (after a remote
interpreter is configured -- which should be configured to have the
settings from the remote computer, we'd still need some mechanism to
synchronize the code you have locally and remotely).
I think that PyDev should work mostly locally for development and on launch
(or during development), the code should be kept in sync with the remote
and launching should occur only in the remote -- path translation should
all be automatic as the project should also have the concept of having a
remote copy (so, we'd know where's the remote and where's the local).
Related to syntax checking it's done with in memory contents (so, it
doesn't need anything from remote), although for code-analysis it may need
to load many modules when validating something (so, a remote interpreter
should be able to cache the information needed from the remote locally and
contents for the project should be local and kept in sync).
Best Regards,
Fabio
On Mon, Aug 21, 2017 at 4:49 PM, Kelson Zawack <k...@cornell.edu> wrote:
> Actually if I am going to write some code I would like to aim for a use
> case that is more general in two ways. I would like to be able to have
> pydev running on my machine but run python in a container. Also the remote
> machine I want to run the code on is part of a cluster which means starting
> up the interpreter involves sshing to the cluster, and then asking the
> scheduler for a node.
>
> I can’t decide how to deal with the code being executed. In some sense
> the most obvious thing to do is to have it on the same machine/container as
> the interpeter and have the user tell pydev how to do any necessary path
> translation.
>
> How does pydev’s syntax checking work? Is it making use of the specified
> interpreter, so that if you specified a remote interpreter the syntax
> checking would be happening on the remote machine?
>
> Do these questions make sense, or am I on the wrong track?
>
> Thanks for your patience
>
> Kelson
>
>
> On Aug 19, 2017, at 7:30 AM, Fabio Zadrozny <fabi...@gmail.com> wrote:
>
> The first step would be being able to configure the interpreter for a
> remote machine...
>
> The main problem this doesn't work currently the way I said is that PyDev
> will call:
>
> ssh python -u 'local/path/to/interpreterInfo.py'
>
> So, the first step would be making that work (i.e.: run python on ssh but
> making the contents of the local file available remotely).
>
> This happens at org.python.pydev.ui.interpreters.PythonInterpreterManager.
> doCreateInterpreterInfo(String, IProgressMonitor, boolean)
>
> I believe Eclipse already has integration with jsch for doing the ssh
> connection -- the pub/private keys are configured at preferences > general
> > network connections > ssh2, so, we'd need to configure the connection
> host/port, but we can use the keys from there already (not sure how to
> consume that API though, needs some research)... or alternatively, we could
> just start with something as plink/ssh and ask the user to have that
> pre-configured already.
>
> Cheers,
>
> Fabio
>
> On Fri, Aug 18, 2017 at 4:53 PM, Kelson Zawack <k...@cornell.edu> wrote:
>
>> Sounds good. I would be happy to help develop some of these features. I
>> don’t have a ton of time either, but if we could split it up into some
>> small pieces I could make some incremental improvements over the next few
>> months. Do you have suggestions on where to start?
>>
>> Kelson
>>
>> On Aug 18, 2017, at 3:34 PM, Fabio Zadrozny <fabi...@gmail.com> wrote:
>>
>> Humm, I just checked it here and the issue is that it'll pass things from
>> the local eclipse install expecting they'll be in the remote install....
>>
>> I think that for having a remote interpreter I'll have to actually change
>> the implementation to support the use-case better (you'll need too many
>> workarounds to work as is now). So, my suggestion is running from the shell
>> currently (you can still edit in PyDev with something as RSE (Remote System
>> Explorer) -- you can use the following update site to install it:
>> http://download.eclipse.org/tm/updates/3.5/).
>>
>> As I said, I already have plans on improving the scenario, but I still
>> couldn't find enough time to actually implement/document it better.
>>
>> Best Regards,
>>
>> Fabio
>>
>> On Wed, Aug 16, 2017 at 6:00 PM, Kelson Zawack <k...@cornell.edu> wrote:
>>
>>> Hi Fabio -
>>>
>>> Thanks for the suggestion. I tried what you suggested, but when I try
>>> to add my shell script as an interpreter in the preferences dialogue pydev
>>> complains ‘Unable to get info on the interpreter … common reasons include
>>> specifying an invalid interpreter (usually a link to the actual interpreter
>>> on Mac or Linux)’. It seems it needs to access the actual interpreter
>>> files and not just run the interpreter.
>>>
>>> Thoughts?
>>>
>>> Kelson
>>>
>>> On Aug 14, 2017, at 7:35 AM, Fabio Zadrozny <fabi...@gmail.com> wrote:
>>>
>>> Hi Kelson,
>>>
>>> I must say that I haven't really tested this... in theory you could
>>> create a python interpreter which is a shell script which would then run a
>>> python over ssh and with a partition created with sshfs, things should work
>>> (just make sure that the partition locally maps to the same path remotely)
>>> -- although I must say I haven't really tested this setup myself -- so, if
>>> you do go that route, it'd be nice to hear your experience later on ;)
>>>
>>> There are plans to actually improve the remote development scenario on
>>> PyDev (with a remote interpreter supported by default), but I haven't been
>>> able to make time for it so far... maybe I'll create a crowdfunding for
>>> that so that users can help me get the needed time ;)
>>>
>>> Cheers,
>>>
>>> Fabio
>>>
>>> On Fri, Aug 11, 2017 at 10:39 AM, Kelson Zawack <k...@cornell.edu>
>>> wrote:
>>>
>>>> I use Pydev for scientific computing and really like it. One problem I
>>>> have is I would like to use it to run analyses on a server. My plan was to
>>>> use ipython’s ability to run shell commands to ssh to the server and then
>>>> launch an ipython session there. It seems that while the interactive
>>>> interpreter can run the ssh just fine it isn’t able to pick up the remote
>>>> terminal session that gets started. Any suggestions?
>>>>
>>>> Thanks
>>>> ------------------------------------------------------------
>>>> ------------------
>>>> Check out the vibrant tech community on one of the world's most
>>>> engaging tech sites, Slashdot.org <http://slashdot.org/>!
>>>> http://sdm.link/slashdot
>>>> _______________________________________________
>>>> pydev-code mailing list
>>>> pydev-code@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/pydev-code
>>>>
>>>
>>> ------------------------------------------------------------
>>> ------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org <http://slashdot.org/>!
>>> http://sdm.link/slashdot_______________________________________________
>>> pydev-code mailing list
>>> pydev-code@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/pydev-code
>>>
>>>
>>>
>>> ------------------------------------------------------------
>>> ------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org <http://slashdot.org/>!
>>> http://sdm.link/slashdot
>>> _______________________________________________
>>> pydev-code mailing list
>>> pydev-code@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/pydev-code
>>>
>>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org <http://slashdot.org/>!
>> http://sdm.link/slashdot_______________________________________________
>> pydev-code mailing list
>> pydev-code@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/pydev-code
>>
>>
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> pydev-code mailing list
>> pydev-code@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/pydev-code
>>
>>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot______
> _________________________________________
> pydev-code mailing list
> pydev-code@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/pydev-code
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> pydev-code mailing list
> pydev-code@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/pydev-code
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
pydev-code mailing list
pydev-code@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pydev-code
