Skip to content
This repository has been archived by the owner on Apr 14, 2019. It is now read-only.

ENH: add fixture for San Diego reporting periods, 2015 & 2016. #249

Merged
merged 1 commit into from
Jul 14, 2016

Conversation

bcipolli
Copy link
Collaborator

@bcipolli bcipolli commented Jul 6, 2016

Here are updated fixtures for getting SD data to run. Similar data should be added for SF/OAK.

This enables:
python manage.py xformnetfilerawdata --agencies CSD --years 2015,2016

@adborden adborden self-assigned this Jul 6, 2016
@adborden
Copy link
Member

adborden commented Jul 6, 2016

This is still missing fixtures for reporting periods. I'm creating them locally now. There's usually 2-4 per year depending on jurisdiction and they need to be created for each form, too.

@adborden
Copy link
Member

adborden commented Jul 7, 2016

Related #221

@tdooner
Copy link
Member

tdooner commented Jul 14, 2016

I'm going to merge this so we get closer to a backend that works.

In the future, @bcipolli, please pretty-print JSON so it is more readable and easier to diff. My favorite tool for this purpose is jq, which you may already know, could help you out like so:

cat foo.json | jq . | sponge foo.json

(using sponge from the coreutils package)

@tdooner tdooner merged commit e91e941 into develop Jul 14, 2016
@KyleW
Copy link

KyleW commented Jul 14, 2016

@monkeyhippies - this may be helpful for the issue you're looking at. I believe the fix is to add those missing fixtures @bcipolli mentions.

@mikeubell
Copy link
Contributor

python manage.py xformnetfilerawdata --agencies CSD --years 2015,2016
Still fails for me with this merge. I pulled the develop branch, recreated the db's. ran makemigrations and then setupserver. The above command fails with:
Exception: You must add a reporting period for form 'Form 460 Schedule A', locality 'San Diego, CA', containing date 2015-01-15 00:00:00-08:00

@tdooner
Copy link
Member

tdooner commented Jul 15, 2016

@mikeubell you may need to load the fixtures, according to this the command is python manage.py loaddata

@mikeubell
Copy link
Contributor

That should be documented, particularly what fixture name we are using:
manage.py loaddata: error: No database fixture specified. Please provide the path of at least one fixture in the command line.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants