From: R0b0t1 <r030t1@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] pycharm-community vs pycharm-professional
Date: Mon, 17 Sep 2018 11:19:28 +0200 [thread overview]
Message-ID: <CAAD4mYhSRT3D_mDi95n8hMaUFEh6s4rdpvhQCd0aLBSPGFqLUQ@mail.gmail.com> (raw)
In-Reply-To: <0c14cbd4-4a28-f5ef-ebfd-1d3d494ca68c@st.com>
On Mon, Sep 17, 2018 at 10:54 AM, Raffaele Belardi
<raffaele.belardi@st.com> wrote:
> András Csányi wrote:
>> Hi,
>>
>> Check this page:
>> https://www.jetbrains.com/pycharm/features/editions_comparison_matrix.html
>
> I'm not the OP but am interested in the topic and currently just a noob in Python.
>
> I'd use Python to develop programs for fun on an ARM-linux embedded board, with the host
> PC running Gentoo. I suppose that for debugging on the target I'd need this feature:
> "Remote run/debug" which is available only in the Pro edition, right?
>
Yes. For all interested there is a .jar going around that has been
modified to avoid the license check that is as far as I can tell safe;
it does not require a network connection.
There is also PyDev, based on Eclipse. Remote debug (which entails
running) can be found documented at
http://www.pydev.org/manual_adv_remote_debugger.html.
Usually what I see is either sftp or rsync (over ssh) to the remote
computer, then ssh to run the updated files. Alternatively you can ssh
to the remote host and run vim within that session.
Cheers,
R0b0t1
next prev parent reply other threads:[~2018-09-17 9:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-15 22:31 [gentoo-user] pycharm-community vs pycharm-professional gevisz
2018-09-15 22:40 ` Andrew Udvare
2018-09-15 22:42 ` András Csányi
2018-09-16 7:13 ` gevisz
2018-09-16 7:56 ` Arve Barsnes
2018-09-16 11:34 ` gevisz
2018-09-17 8:54 ` Raffaele Belardi
2018-09-17 9:19 ` R0b0t1 [this message]
2018-09-17 9:53 ` [gentoo-user] remote debugging python on embedded platform Raffaele Belardi
2018-09-17 10:36 ` R0b0t1
2018-09-17 11:38 ` R0b0t1
2018-09-18 5:24 ` Raffaele Belardi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAD4mYhSRT3D_mDi95n8hMaUFEh6s4rdpvhQCd0aLBSPGFqLUQ@mail.gmail.com \
--to=r030t1@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox