Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Changes on namespace

See original GitHub issue

The idea is to create a new namespace lib containing the current context one. At the end, the namespace structure will be:

  • Lib
    • Context
      • Base context
      • Api context
      • (here will be the analysis framework context)


We want to send a message to the users: “this namespace is internal or private, you don’t need to think about it”.

it could be others like private or internals for example, but we have selected lib for being more generic.

cc @alasarr @alrocar @andy-esch

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:3
  • Comments:6 (6 by maintainers)

github_iconTop GitHub Comments

oleurudcommented, Sep 2, 2019

After a talk with @alasarr & @jgoizueta, we want to consider geocoding or isochrones part of data as services (or data services) and keep analysis namespace to big analysis as feature engineering.

Also, we want to add a deeper structure to data elements.

So, finally:

  • Auth

    • Credentials
    • set_default_credentials
  • Lib

    • Context
      • Api context
      • (Analysis framework context)
  • Data

    • Dataset
      • Dataset class
      • Registry
    • Do
      • enrich functions (enrich_points & enrich_polygon)
      • Catalog
      • Dataset
      • Country
      • Variable (supports variables group and variables)
      • Category
      • Geography
    • Services
      • Geocoding
      • Isochrones
  • Analysis

  • Viz

    • Map
    • Layers
    • Helpers
  • Utils

    • CARTO SQL client
    • Columns
    • Table (a helper class to get current Tables in a CARTO account)
  • Contrib (it could appear in the future)

Note: namespaces and classes in bold are public

oleurudcommented, Sep 10, 2019


Read more comments on GitHub >

github_iconTop Results From Across the Web

In Kubernetes, namespaces provides a mechanism for isolating groups of resources within a single cluster. Names of resources need to be unique ...
Read more >
How to switch namespace in kubernetes
It's a good practice to validate that the current namespace has changed by executing the following command kubectl config view | grep ......
Read more >
Chapter 4. Common kubectl Commands - Kubernetes
Kubernetes uses namespaces to organize objects in the cluster. ... If you want to change the default namespace more permanently, you can use...
Read more >
Kubernetes Namespaces: Everything you need to know
Kubernetes namespaces are a mechanism for isolating groups of resources within a single cluster. Resource names must be unique within a ...
Read more >
What is a Kubernetes Namespace? | VMware Glossary
Since this can get cumbersome, the default namespace can be changed by using the kubectl config command to set the namespace in the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found