Skip to content
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

Modify Naming Conventions for CSV Output File and Excel Output File #558

Merged
merged 16 commits into from
Jul 14, 2017

Conversation

GoFroggyRun
Copy link
Contributor

@GoFroggyRun GoFroggyRun commented Jun 7, 2017

This PR tries to partially resolve concerns addressed in #534.

In particular, @MattHJensen suggested naming scheme for csv output files and excel output files in 534 comment. This PR mostly follows such scheme, expect substituting suggested keywords "payroll-income" and 'income" with "combined" and "individual" respectively so that the file name corresponds to the title of the table.

Based on local tests, the output file names read:

screen shot 2017-06-09 at 1 17 26 pm

Note that 127 is my run number, which will be changing according to the url. Please also note that the some buttons are not working for total liabilities tables, and currently the only output file for that table is in the format xxx_liabilities_change.

@MattHJensen Could you review? Any comments, concerns or remarks are welcomed.

@GoFroggyRun GoFroggyRun changed the title [WPI] Modify Naming Conventions for CSV output file and Excel output file [WPI] Modify Naming Conventions for CSV Output File and Excel Output File Jun 7, 2017
@GoFroggyRun GoFroggyRun changed the title [WPI] Modify Naming Conventions for CSV Output File and Excel Output File Modify Naming Conventions for CSV Output File and Excel Output File Jun 9, 2017
@MattHJensen
Copy link
Contributor

@GoFroggyRun, is this ready for review?

cc @brittainhard

@GoFroggyRun
Copy link
Contributor Author

GoFroggyRun commented Jun 14, 2017 via email

@@ -8,7 +8,6 @@ static3==0.5.1
wsgiref==0.1.2
-e git+https://github.com/funkybob/django-flatblocks.git#egg=django-flatblocks
sendgrid-django
psycopg2==2.5.4
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whats the reasoning behind removing this dependency?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@brittainhard:
When I was trying to set up everything locally with @PeterDSteinberg, some dependency error message regarding psycopg2 pops out. Removing this dependency seems to resolve such issue.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the dependency issue? Can you get a traceback?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm mainly concerned that this will cause issues on the heroku deployment, since it uses postgres as a database.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@brittainhard:
I wasn't able to locate the traceback since it was a while ago. Currently my conda list shows that psycopg2 is on 2.7.1. Would this be a problem for heroku deployment?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In other words, would it be a problem if I change the line

-psycopg2==2.5.4

to

-psycopg2

that removes the version requirement?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about this:

psycopg2>=2.5.4

Won't that satisfy everybody?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@GoFroggyRun if the main issue that you are having issues using postgres locally? If thats the case, there is the option of using SQLite for local development. It's what i use, since I have to alter the database frequently.

Is the problem that your psycopg2 version is causing problems, so you had to upgrade it? In that case @martinholmer that's a reasonable fix.

@talumbau
Copy link
Member

talumbau commented Jun 15, 2017 via email

@GoFroggyRun
Copy link
Contributor Author

Thanks @martinholmer and @brittainhard for your advices. It's the version of psycopg2 that bothers me, and I adopted @martinholmer's suggestion to fix that. Please take another look.

@brittainhard
Copy link
Contributor

Looks good to me. +1

@brittainhard brittainhard merged commit f274189 into ospc-org:master Jul 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants