Fix authentication error when postgres is password protected

[jonathan-s]

Fixes #282

[jonathan-s]

@NoahRR Hey there, I saw that you had issues with #282, would you mind trying out this branch and see if it works for you?

[jonathan-s]

Should add a testcase for this too -> https://dba.stackexchange.com/a/243220/132631

[ZuluPro]

👍🏾

[NoahRR]

@NoahRR Hey there, I saw that you had issues with #282, would you mind trying out this branch and see if it works for you?

@jonathan-s Hey, yeah I'd love to. Sorry, I'm new to the programming world, how would I actually download this new branch to test if it works? I KNOW REALLY NOOB QUESTION xD

[NoahRR]

@NoahRR Hey there, I saw that you had issues with #282, would you mind trying out this branch and see if it works for you?

@jonathan-s Hey, yeah I'd love to. Sorry, I'm new to the programming world, how would I actually download this new branch to test if it works? I KNOW REALLY NOOB QUESTION xD

scratch that... I see the branch now xD. Let me test it

[NoahRR]

nope, I'm still a dumbass :). I cloned repo and checked out password branch, but how do I actually "install" it so I can test the new functionality. @jonathan-s I know you probably have more important things to do but I'd love to test this branch if I could >.<

[jonathan-s]

@NoahRR Nothing wrong with being a noob, we all were at some point.

So you've cloned the repo and also changed the branch to password. Great! Half-way there. If you go to the folder where the cloned repo is (ie you see setup.py when you type ls -l in the command line). You should be able to type pip install -e . that would install the package in editable mode (which is excellent way of developing python packages :) ). It's pip installed and is now available everywhere you can access all the other packages that were installed the same way.

[NoahRR]

@jonathan-s I really appreciate the help (now i understand how that works)!

The new branch seems to have solved the password problem!

... I'm still running into errors, but I believe those are due to Postgres permissions (error: permission denied for schema topology). Anyways, I don't think that is relevant and shouldn't be too hard to fix on my part. The --no-password errors are gone!

[jonathan-s]

Great to hear @NoahRR, and thanks for verifying that it works as expected.