Skip to content

List PyThaiNLP 2.0 #118

Closed
Closed
@wannaphong

Description

@wannaphong

New evaluation corpus

New features

Bug fixes

Other improvements and optimizations

Name changes in API

  • Rearrangement of utility functions. Most of them, like rank, find_keyword, collate, and functions related to date and time, are now in pythainlp.util module. (Utility functions: rearrange package locations + add thai_strftime() date and time formatter #160)
  • Some class and function names are changed from 1.7 to make it aligned with PEP8 (Style Guide for Python Code), make it more explicit about what they are doing, or make it more consistent with other related classes/functions. For examples:
    • thainer and thai2rom classes are now ThaiNameTagger and ThaiTransliterator (CapWords for class name)
    • pythainlp.soundex.LK82, pythainlp.soundex.Udom83, and pythainlp.MetaSound functions are now pythainlp.soundex.lk82, pythainlp.soundex.udom83, and pythainlp.soundex.metasound (small caps for function name, also move metasound to soundex module)
    • collation, correction, and romanization functions are now collate, correct, and romanize -- in a verb (action) form, and in line with tokenize and summarize functions.
  • pythainlp.corpus.alphabets, pythainlp.corpus.tone, etc. constants are now pythainlp.thai_consonants, pythainlp.thai_tonemarks, etc.
    • They are also now str instead of set.
    • This is to follow the example of string.ascii_letters, etc. str also iterate a little bit faster in one character for one member use cases that these constants are usually used for.
  • These changes will resulted in breaking code if your code directly invoke those classes/functions. In general, the change should be only at the level of class or function name, there should be no change at the arguments passing to the class or the function. Please refer to the API doc.
  • Internally, there are also name changes of corpus files (Naming convention for consistency วิธีการตั้งชื่อไฟล์ #141) but this should not has any effect to the API.

Metadata

Metadata

Assignees

Labels

enhancementenhance functionalities

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions