Make namespace flat
See original GitHub issuePlan is to have a flat namespace for public functions:
plot_(plot_forest,plot_autocorrelation, etc)stat_(not wild about this naming convention - maybe just make sure these names are descriptive and exposed in the top-level namespace. thoughts?)- other functions (
convert_to_xarray,style.use) - Rename
load_arviz_datatoload_dataset - Make sure libraries like
matplotlib.pyplotorxarrayare not making it into thearviznamespace.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
How to use a "flat" namespace in whole C# project
Although all concerns mentioned in comments, there's simple way to achieve this. Just go to project properties and define default namespace:.
Read more >Introducing Hierarchical Namespaces - Kubernetes
Namespaces for tenancy Namespaces have two key properties that make them ideal for policy enforcement. Firstly, they can be used to represent ...
Read more >Understanding Object Storage Namespaces
Within a namespace, buckets and objects exist in flat hierarchy, but you can simulate a directory structure to help navigate a large set...
Read more >File scoped namespaces - C# 10.0 draft specifications
This feature specification describes file scoped namespaces, where the entire contents of a file are included in a namespace declared at the ...
Read more >Packaging namespace packages
Namespace packages allow you to split the sub-packages and modules within a single ... All that is required to create a native namespace...
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 Free
Top 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

My only hesitation with that is that there will be different return types (turning a numpy array into inference data is a ton of guessing about intentions). What about exposing
in the top level, and rename the directory to
convert, so you canaz.convert.dict_to_datasetoraz.convert.numpy_to_dataarrayif you need extra specificity.I know it is not consistent, but I sort of like that
from_pymc3accepts atraceargument, whilefrom_stanaccepts afitobject, which will be familiar to users of the library. Hopefullyfrom_pyroandfrom_tfpwill show up soon!Marking this as done, by the way.