reworking wright-tools entry points #1152
Conversation
|
for the record, I would lean towards conversions and loading being separate commands, personally, though I don't necessarily have a problem with extending |
yeah, I totally agree it's not right to call everything under wt-tree. I really wish I use I will definitely rework the namespace to make it fit better with the tools. |
interact with crawl after table is made
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
fix typo
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
using multiple entry points
incorporate attrs filter in glob methods
try to use pathlib over os
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
directory is optional argument for most methods
for more information, see https://pre-commit.ci
ddkohler
changed the title
ddkohler
requested review from
untzag,
ksunden,
darienmorrow and
kameyer226
as code owners
| number = int(number) | ||
| sig_figs = len(str(number)) | ||
| sig_figs -= 1 if "." in str(number) else 0 | ||
|
|
There was a problem hiding this comment.
Guess we are presuming no Europeans who use commas instead of decimal points...
There was a problem hiding this comment.
Europeans have to use . when working with python anyways (unless they change default formatting). In any case, I don't see our notation as a meaningful hindrance. I am fine with the syntax as is until someone raises an issue.
|
|
||
|
|
||
| if __name__ == "__main__": | ||
| cli() |
There was a problem hiding this comment.
This was a feature request (issue #653). A quick entry point to check how units convert (according to wright tools)
Changes
wt-treeremovedwt-convertfor cli access to our unit conversions (resolves wt-convert entry point #653)wt5with commands tree, load, glob, explorewt5entry point for such utilitiesChecklist