Notebooks, VS Code and Customized Python libraries

Hi SergioTorrinha 
Thanks for using Fabric Community.

1. Customized Libraries and Wheel Files:

Building wheel files every time you make adjustments can be quite tedious. Here are some alternatives:

• Pip-installable Packages: If your library is simple enough, consider packaging it as a regular Python package and publishing it on a private PyPI repository within your organization. This allows easy installation with pip install and avoids rebuilding wheels.
• Local Imports: For quick testing and development, you can import your library directly from the source directory without building a wheel. This speeds up your workflow but is limited to the development environment.
• VS Code Integration: You can use VS Code extensions like "Python Project Manager" or "Kite" to manage dependencies and automatically install modules from source directories within your workspace. This provides a more IDE-integrated approach.

2. Notebook Resources:

Notebook resources are indeed a new feature in Microsoft Fabric. They allow you to reference external Python modules directly within your notebook without needing to install them through traditional methods like wheels or pip.

To use this functionality you need to install the Synapse Visual Studio Code extension. Please refer to this link and install all the prerequisites : Link1
The Synapse Visual Studio Code extension supports a pro-developer experience for exploring Microsoft Fabric lakehouses, and authoring Fabric notebooks and Spark job definitions.

3. Microsoft Fabric Roadmap:

Microsoft Fabric is continuously evolving, and the team is always working on improving functionalities like notebooks, python environments, and custom libraries. The specific roadmap for these areas isn't publicly available, but you can find general updates and announcements through the Microsoft Fabric blog and release plan documentation.

Hope this helps. Please let us know if you have any further questions.

Hi Anonymous !

Sorry for late response, but I was away for some Christmas time with family and friends. 🙂

Before anything, thanks for your input.
Based on it, I think that, for now, the most straightforward way of making use of custom libraries is really the notebook resource feature, because one only needs to publish the 'resource'/library into MS Fabric and that's it, which makes it easy and simple to use and to adjust whenever there is the need for it.

With this is mind, I have a couple more questions:

1. Is there any other documentation for it, excluding the one I pointed out initially? Is it planned to build some more documentation for this feature, eventually including one or multiple use case scenarios/examples?
2. Is there a way to see, in MS Fabric, where is the 'notebook resource'/custom library landing, after being exported from VS code? Will the 'notebook resource'/custom library be landing in the Files section of the data lake associated with the notebook, for instance, or is it somewhere else?
3. Related to VS Code and MS Fabric integration, and because I like to be an efficient programmer I find a bit clunky/not practical to keep pushing all those import/export buttons. Is it planned to enable some sort of automatic import/export of notebooks and their resources into or from MS Fabric ?

Again, thanks for the input.