lists/dicts in vocabulary in separate json files for easier merging of changes to vocabulary.py
See original GitHub issueAs it stands, many refactors to vocabulary.py
result in merge conflicts due to custom vocabulary defined. If these were instead read from json files, this would no longer be a problem.
Issue Analytics
- State:
- Created 3 years ago
- Comments:15 (7 by maintainers)
Top Results From Across the Web
The purpose of files merges.txt, special_tokens_map.json, ...
Good evening! After I have my RoBERTa model pre-trained, I get the list of the following files: merges.txt, special_tokens_map.json, ...
Read more >separate dictionary in multiple json files - python
I have multiple json files. I merge the files in a unique dictionary. What I want, is to save this dictionary back to...
Read more >jsonmerge
This Python module allows you to merge a series of JSON documents into a single ... We call the document we are merging...
Read more >Working With JSON Data in Python
In this tutorial you'll learn how to read and write JSON-encoded data using Python ... A Little Vocabulary; Serializing JSON; A Simple Serialization...
Read more >How to Best Work with JSON in Python | by Julia Kho
In this article, you will learn how to read, parse, and write JSON files in Python. I will talk about how to best...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah, CSV works and has precedent 👍 I think jcaw might have some work in this direction as well
sounds like everyone’s on the same page, but FWIW I’d vote to keeping it simple & clean-
(1) Use CSV; probably stick with vanilla CSV stuff since this is (presumably) a temporary solution until .talon has support for lists. Just document when/what we can. (2) 4 files is probably the most intuitive for newbies, particularly with the differences between Dragon and w2l re: capitalization.