# Workaround for importing folder by compiling wheel

**URL:** <https://forum.anaconda.com/t/workaround-for-importing-folder-by-compiling-wheel/23103>\
**Category:** PyScript\
**Created:** [May 27, 2022, 2:31am UTC](https://forum.anaconda.com/t/workaround-for-importing-folder-by-compiling-wheel/23103 "2022-05-27T02:31:43Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mudream4869](https://dub1.discourse-cdn.com/anaconda/user_avatar/forum.anaconda.com/mudream4869/32/1401_2.png) [@mudream4869](https://forum.anaconda.com/u/mudream4869)\
**Post date:** [May 27, 2022, 2:31am UTC](https://forum.anaconda.com/t/workaround-for-importing-folder-by-compiling-wheel/23103/1 "2022-05-27T02:31:43Z")

</div>

Just a workaround 😛

> **[GitHub - mudream4869/pyscript-local-package: Just a workaround for pyscript...](https://github.com/mudream4869/pyscript-local-package)**
>
> Just a workaround for pyscript importing local package. - GitHub - mudream4869/pyscript-local-package: Just a workaround for pyscript importing local package.

---

<div class="post-metadata">

**Author:** ![john.hanley](https://dub1.discourse-cdn.com/anaconda/user_avatar/forum.anaconda.com/john.hanley/32/1294_2.png) [@john.hanley](https://forum.anaconda.com/u/john.hanley)\
**Post date:** [May 27, 2022, 6:56am UTC](https://forum.anaconda.com/t/workaround-for-importing-folder-by-compiling-wheel/23103/2 "2022-05-27T06:56:53Z")

</div>

Very interesting. That has potential for applications with many files.

My only suggestion is to improve the readme to explain what you have written so that others can understand without studying the repository.

---

<div class="post-metadata">

**Author:** ![MARTIN\_DURANT](https://dub1.discourse-cdn.com/anaconda/user_avatar/forum.anaconda.com/martin_durant/32/67_2.png) [@MARTIN\_DURANT](https://forum.anaconda.com/u/MARTIN_DURANT)\
**Post date:** [June 1, 2022, 3:50pm UTC](https://forum.anaconda.com/t/workaround-for-importing-folder-by-compiling-wheel/23103/3 "2022-06-01T15:50:30Z")

</div>

Even better would be to auto-generate the setup,py for any python package (dir with ` __init__.py`).!

---

<div class="post-metadata">

**Author:** ![pauleveritt](https://dub1.discourse-cdn.com/anaconda/user_avatar/forum.anaconda.com/pauleveritt/32/1649_2.png) [@pauleveritt](https://forum.anaconda.com/u/pauleveritt)\
**Post date:** [June 2, 2022, 1:25pm UTC](https://forum.anaconda.com/t/workaround-for-importing-folder-by-compiling-wheel/23103/4 "2022-06-02T13:25:49Z")

</div>

That’s a smart idea, reminds me of the build process for frontend JS. Of course, PyScript wants to eliminate that.

But I could imagine a smart dev server which made this process worth doing.

---

<div class="post-metadata">

**Author:** ![JeffGlass](https://dub1.discourse-cdn.com/anaconda/user_avatar/forum.anaconda.com/jeffglass/32/1301_2.png) [@JeffGlass](https://forum.anaconda.com/u/JeffGlass)\
**Post date:** [July 12, 2022, 1:25pm UTC](https://forum.anaconda.com/t/workaround-for-importing-folder-by-compiling-wheel/23103/5 "2022-07-12T13:25:16Z")

</div>

As you say @pauleveritt, automating the build step is a huge help - I’ve found that using VS Code’s [Run on Save Extension](https://code.visualstudio.com/updates/v1_23#_run-code-actions-on-save) to build a wheel automatically whenever a change is saved to in the module code speeds up iteration time considerably. I believe PyCharm’s [File Watcher](https://www.jetbrains.com/help/pycharm/using-file-watchers.html) feature could achieve the same thing.