<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: where saving the wheel package? in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/where-saving-the-wheel-package/m-p/114176#M44735</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/133094"&gt;@jeremy98&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can upload the wheel to a shared workspace location and configure it for cluster-level installation by attaching it as a library.&lt;/P&gt;&lt;P&gt;Or you can also automate the process by adding the wheel to the libraries section of your databricks.yml task configuration.&lt;/P&gt;</description>
    <pubDate>Tue, 01 Apr 2025 13:14:10 GMT</pubDate>
    <dc:creator>Renu_</dc:creator>
    <dc:date>2025-04-01T13:14:10Z</dc:date>
    <item>
      <title>where saving the wheel package?</title>
      <link>https://community.databricks.com/t5/data-engineering/where-saving-the-wheel-package/m-p/111549#M43933</link>
      <description>&lt;P&gt;Hi community,&lt;/P&gt;&lt;P&gt;We have deployed the wheel package internally in our bundle repository:&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;artifacts:
  rnc_lib:
    type: whl
    build: poetry build
    path: .

# For passing wheel package to workspace
sync:
  include:
    - ./dist/*.whl&lt;/LI-CODE&gt;&lt;P&gt;The problem is that if we want to install packages in each notebook scope file, for now, we do it one by one:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;%pip install sentry-sdk=2.19.0&lt;/LI-CODE&gt;&lt;P&gt;but, this is not feasible, so which is the best practice in this case? Deploying the wheel in a Workspace/Shared location? Or?&lt;/P&gt;</description>
      <pubDate>Mon, 03 Mar 2025 09:14:22 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/where-saving-the-wheel-package/m-p/111549#M43933</guid>
      <dc:creator>jeremy98</dc:creator>
      <dc:date>2025-03-03T09:14:22Z</dc:date>
    </item>
    <item>
      <title>Re: where saving the wheel package?</title>
      <link>https://community.databricks.com/t5/data-engineering/where-saving-the-wheel-package/m-p/114176#M44735</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/133094"&gt;@jeremy98&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can upload the wheel to a shared workspace location and configure it for cluster-level installation by attaching it as a library.&lt;/P&gt;&lt;P&gt;Or you can also automate the process by adding the wheel to the libraries section of your databricks.yml task configuration.&lt;/P&gt;</description>
      <pubDate>Tue, 01 Apr 2025 13:14:10 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/where-saving-the-wheel-package/m-p/114176#M44735</guid>
      <dc:creator>Renu_</dc:creator>
      <dc:date>2025-04-01T13:14:10Z</dc:date>
    </item>
  </channel>
</rss>

