• Documentation
    • Search documentation
    karat

    +

    K

    API Reference ↗
    5B. [Repositories] Publishing and Using Shared Libraries in Code Repositories4. Exercise Summary

    4 - Exercise Summary

    This content is also available at learn.palantir.com ↗ and is presented here for accessibility purposes.

    ✅ What you built

    A shared library repository in `.../Training Artifacts/yourName/Data Engineering Tutorials/Shared Python Libraries/.

    ✅ What you learned

    1. Most of the popular Python packages are already exposed in publicly available Conda channels such as conda-forge ↗ or bioconda ↗. Your organization either:

      • Proxies a mirror of one of these channels, which means the external channel must be available on the network.
      • Produces a local artifact repository from an asset bundle that contains a standard Conda channel.

    2. Your package name is the name of your shared library (spaces and underscore characters in your repository name will be replaced with hyphens when it appears as a package).

    3. You can change the name of your package by updating the condaPackageName variable in the hidden gradle.properties file.