You are not logged in.
- Topics: Active | Unanswered
#1 2019-07-09 09:08:45
- linux-mate
- Banned
- Registered: 2018-06-28
- Posts: 78
[SELF-SOLVED] Pycharm mercurial problem
"Message" is a required field in this form.
Last edited by linux-mate (2020-01-05 21:57:32)
Offline
#2 2019-07-09 16:08:47
- jasonwryan
- Anarchist
- From: .nz
- Registered: 2009-05-09
- Posts: 30,424
- Website
Re: [SELF-SOLVED] Pycharm mercurial problem
Include version numbers and the actual name of the pycharm package. for a start.
Moving to NC...
Offline
#3 2019-07-09 16:32:05
- linux-mate
- Banned
- Registered: 2018-06-28
- Posts: 78
Re: [SELF-SOLVED] Pycharm mercurial problem
"Message" is a required field in this form.
Last edited by linux-mate (2020-01-05 21:57:25)
Offline
#4 2019-07-09 18:01:25
- jasonwryan
- Anarchist
- From: .nz
- Registered: 2009-05-09
- Posts: 30,424
- Website
Re: [SELF-SOLVED] Pycharm mercurial problem
So the package is pycharm-professional?
Moving to AUR Issues...
Offline
#5 2019-07-10 08:07:22
- linux-mate
- Banned
- Registered: 2018-06-28
- Posts: 78
Re: [SELF-SOLVED] Pycharm mercurial problem
"Message" is a required field in this form.
Last edited by linux-mate (2020-01-05 21:57:20)
Offline
#6 2019-07-10 08:19:17
- bulletmark
- Member
- From: Brisbane, Australia
- Registered: 2013-10-22
- Posts: 653
Re: [SELF-SOLVED] Pycharm mercurial problem
self solved like always ..
Well it had to be "self solved" because you never answered any of the questions that were asked!
Offline
#7 2019-07-12 22:43:57
- chrisjbillington
- Member
- Registered: 2018-11-26
- Posts: 15
Re: [SELF-SOLVED] Pycharm mercurial problem
For what it's worth, most Python programs on Arch will be confused by finding themselves being run whilst you're in a virtualenv. In contrast to other distros, it's normal practice on Arch for shebangs to be `#! python` instead of specifying a full path to a python interpreter, which means they use whichever python interpreter is first in the path. This was the preference of one of the core developers (Allan, I think), as it makes testing a program with different python versions easier, but I personally hope this advice gets revisited - it means that ordinary pacman-installed tools written in Python but presenting as ordinary executables in /usr/bin often will not work whilst in a conda env or virtualenv.
Last edited by chrisjbillington (2019-07-13 02:05:18)
Offline