Migrating to 2.0
tacular 2.0 is a breaking API cleanup. The data is the same as 1.2. Renamed names have no aliases, so an import or attribute error tells you exactly what to change. The tables below list every removed or renamed public name.
Renamed
1.x |
2.0 |
|---|---|
|
|
|
read-only now ( |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Removed or made private
1.x |
Use instead |
|---|---|
|
|
|
|
|
|
|
|
|
a list comprehension over |
|
|
|
inherited |
Changed behaviour
1.x |
2.0 |
|---|---|
|
|
|
|
|
keyword-only: |
|
frozen, slotted dataclasses (no |
|
also include |
|
sorted, so |
|
|
Only long accession prefixes ( |
short prefixes too ( |
|
raise |
|
returns the raw accession ids ( |
|
|
|
raises |
|
raises |
|
always downloads the current release; |
New
tacular.constants:PROTON_MASS,ELECTRON_MASS,NEUTRON_MASS(CODATA 2018),HYDROGEN_MASSandC13_C12_MASS_DIFF(AME2016, matching the bundled isotope table).items()on every lookup;query_nameonMONOSACCHARIDE_LOOKUP.tacular.ElementKey: the type of every keyELEMENT_LOOKUPaccepts.tacular.tolerance:ppm_error,da_to_ppm,ppm_to_da,tolerance_windowandwithin_tolerance;query_masstakestolerance_unit="da"|"ppm"(the keyword every tacular-omics package uses).tacular.types:ToleranceUnitandPolarity, the shared vocabulary the other packages import instead of defining their own.