-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd client is not able to parse arguments correctly #46
Comments
Thanks for the detailed info. I really need to revise the interface. |
yeah, I am trying to incorporate your module into my own module. |
if you're building in python, it's probably easier to directly import the do_ofximport/do_csvimport functions instead of using the CLI interface I think. just pass it an object with email,password,budgetname attributes |
OK I think I found the problem, just pushed 3d3c305 , there was a missing sys.argv.pop to remove the command (ofximport or csvimport). |
No, not yet.
to get the error messages working on cmd. After that, i still get the following message:
|
Logging, logging.basicConfig() in main added in the latest changes This case |
Logging is indeed fixed, but the second error in #46 (comment) still exists with 1a58943. |
which python version ? |
2.7.13 and 3.6 |
how did you install pynynab and its entrypoint ? |
I uninstalled all pip version of pynynab, cloned the repo, created a virtual environment using Is something wrong with doing it that way? |
Here is the next issue:
pynynab ofximport --email bla --password bla --budgetname bla
(no ofx file given)seem to use
ofximport
as file name:pynynab ofximport --email bla --password bla --budgetname bla sample.ofx
fails with
My
ynab.conf
in the working directory is ignored.The text was updated successfully, but these errors were encountered: