Hi
On Fri, Dec 16, 2016 at 1:21 AM, Mark Murawski
<markm-lists@intellasoft.net> wrote:
> Ah thanks. It was just odd it didn't keep the settings from before i upped
> my local git.
It should - it stores that in your home directory by default. My only
guess is that it was working with the previous default search paths,
and we changed something in the code that caused that to no longer
work for you. I don't recall any changes in that area though.
> I searched my email history left and right trying to find where you had
> helped me previously, but I couldn't find anything and got stuck. A user
> not knowing anything beforehand, seeing 'Python Path' is a bit misleading
> without knowing the internals and how this parameter gets used.
True, but we don't expect most users to build their own copy. We
expect them to be using prebuilt/configured packages instead.
> I'll make some notes in my local README on this so I don't have to fight
> this next time.
>
> It would be really great if some sort of automatic virtualenv was set up and
> used as part of the startup. It's pretty easy to auto detect where the
> virtualenv tools are located on major distros, and worst-case, it can always
> fall back to spit out a note saying 'here's how you do it manually'.
Is the info in the existing README enough? If you can suggest
improvements I'd be happy to look at them.
Trying to handle auto-setup on a distro by distro basis is almost
certainly a non-starter. There are so many different ways things could
be setup, that vary even between different versions of distros that I
wouldn't be practical for us to deal with. That's why we try to leave
those details up to the packagers.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company