Skip to content
This repository has been archived by the owner on Feb 23, 2020. It is now read-only.

parse_stalbeton.py:128-131: Save parsed stalbeton to a... #764

Open
0pdd opened this issue Jul 16, 2019 · 1 comment
Open

parse_stalbeton.py:128-131: Save parsed stalbeton to a... #764

0pdd opened this issue Jul 16, 2019 · 1 comment
Labels
1 hour typical issue size. It's one pdd hour. Performer should spend about one astronomical hour for this i 1 burning issue take it any teammate can take this issue and start working with it

Comments

@0pdd
Copy link
Collaborator

0pdd commented Jul 16, 2019

The puzzle 741-c3a9fcaf from #741 has to be resolved:

# @todo #741:60m Save parsed stalbeton to a DB.
# DB isn't required to be high performance.
# It can be sqlite or postgres or pickle lib or whatever else.
# DB is required to analyze data without loading stalbeton site every time.

The puzzle was created by duker33 on 16-Jul-19.

Estimate: 60 minutes, role: DEV.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@0pdd
Copy link
Collaborator Author

0pdd commented Jul 16, 2019

@artemiyds2 @duker33 please pay attention to this new issue.

0pdd referenced this issue Jul 16, 2019
* #741  Parse roots

* #741  Cleanup categories parsing code

* #741  Parse category text

* #741  Review#1 fixes. Subtask arch improvements
@duker33 duker33 self-assigned this Jul 16, 2019
@duker33 duker33 added 1 burning issue 1 hour typical issue size. It's one pdd hour. Performer should spend about one astronomical hour for this i labels Jul 16, 2019
@duker33 duker33 removed their assignment Jul 16, 2019
@duker33 duker33 added the take it any teammate can take this issue and start working with it label Jul 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
1 hour typical issue size. It's one pdd hour. Performer should spend about one astronomical hour for this i 1 burning issue take it any teammate can take this issue and start working with it
Projects
None yet
Development

No branches or pull requests

2 participants