It is not currently possible to use objects directly in Code Workspaces. User may import datasets that back objects using the Data menu within a workspace.
No. For performing large-scale data transformations, we recommend Foundry applications like Pipeline Builder and Code Repositories that leverage a Spark infrastructure.
Code Workspaces currently supports JupyterLab® and RStudio® Workbench.
Due to security reasons, the following Python packages are not supported:
Contact your Palantir representative if you have any concerns about the packages above.
Yes, you can make API calls in Code Workspaces after defining network policies in the Settings menu. Note that the external API must be registered as an approved Network Egress policy in Control Panel.
The Code Repositories application receives code from associated Code Workspaces in an IPython format, which renders the code at a cell-by-cell level in JSON format.
Yes; see the documentation on importing packages. If your package is hosted on an organizational Conda/PyPI/CRAN channel, it is possible for Foundry to proxy the channel and make it available to your projects. Contact your Palantir representative for more information.
To import libraries into your Code Workspace, use the Packages tab located in the left panel of your workspace.
Yes, you can edit code directly in Code Repositories when the code originates in Code Workspaces. Once committed, you can use the Sync or Reset changes functionality in the Code Workspace to pick up the remote changes in the Workspace.
Conceptually, you can think of Code Repositories as the version control manager for Code Workspaces, handling pull requests, conflict resolution, and administration, while code development can occur in Code Workspaces.
For security purposes, users are isolated when working in JupyterLab® or RStudio®. This means each user accessing the same Code Workspace will have their own environment. Collaboration happens through git workflows: if you wish to make your latest code available to colleagues, select Sync Changes to synchronize your changes with the backing code repository and the changes will become available to your colleagues when they select Sync or Reset changes. When multiple users work on the same workspace, we recommend they work on independent branches.
Note that we ignore some files by default using .gitignore
to ensure that no data is synchronized with the git repository, and to limit the size of the git repository. We also remove all outputs from JupyterLab® .ipynb
files.
RStudio® and Shiny® are trademarks of Posit™.
Jupyter®, JupyterLab®, and the Jupyter® logos are trademarks or registered trademarks of NumFOCUS.
All third-party trademarks (including logos and icons) referenced remain the property of their respective owners. No affiliation or endorsement is implied.