# Help with the \`spaces\` package documentation

**URL:** <https://discuss.huggingface.co/t/help-with-the-spaces-package-documentation/111845>\
**Category:** Spaces\
**Created:** [October 13, 2024, 10:47pm UTC](https://discuss.huggingface.co/t/help-with-the-spaces-package-documentation/111845 "2024-10-13T22:47:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Padarn](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/padarn/32/32874_2.png) [@Padarn](https://discuss.huggingface.co/u/Padarn)\
**Post date:** [October 13, 2024, 10:47pm UTC](https://discuss.huggingface.co/t/help-with-the-spaces-package-documentation/111845/1 "2024-10-13T22:47:37Z")

</div>

Sorry I recognize I’m probably missing something obvious, but I cannot find any documentation for the `spaces` package.

It is referenced here: [README - a Hugging Face Space by zero-gpu-explorers](https://huggingface.co/spaces/zero-gpu-explorers/README) and I originally came across it looking at this demo app from deepseek [DeepSeek-Coder/demo/app.py at main · deepseek-ai/DeepSeek-Coder · GitHub](https://github.com/deepseek-ai/DeepSeek-Coder/blob/main/demo/app.py)

Thanks

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](https://discuss.huggingface.co/u/John6666)\
**Post date:** [October 13, 2024, 11:16pm UTC](https://discuss.huggingface.co/t/help-with-the-spaces-package-documentation/111845/2 "2024-10-13T23:16:13Z")

</div>

I can’t find any **decent** documentation on the Zero GPU space and spaces library either. I routinely deal with errors by piecing together bits and pieces of information from the above community and the forum, other people’s Spaces, and Google searches.  
But this is not what one would call a **proper method**.  
Most of the HF documentation is of the auto-generated type based on comments in the code, **so when it comes to semi-private libraries and server-side stuff, documentation tends to suddenly disappear**.

I think the most reliable way is to **read the code in the spaces library in the Python folder**. I hope this was a joke or a slight…  
Unfortunately, it’s just a fact.😭

> **[@gtvracer on Hugging Face: "Hello Everyone,
I signed up as Pro and started a...](https://huggingface.co/posts/gtvracer/152623777236688)**
>
> We’re on a journey to advance and democratize artificial intelligence through open source and open science.

---

<div class="post-metadata">

**Author:** ![Padarn](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/padarn/32/32874_2.png) [@Padarn](https://discuss.huggingface.co/u/Padarn)\
**Post date:** [October 14, 2024, 12:13pm UTC](https://discuss.huggingface.co/t/help-with-the-spaces-package-documentation/111845/3 "2024-10-14T12:13:29Z")

</div>

I see haha… well thats unfortunate. I barely know what the package is meant to be doing if I’m honest.

Do we at least know who the author is?

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](https://discuss.huggingface.co/u/John6666)\
**Post date:** [October 14, 2024, 12:18pm UTC](https://discuss.huggingface.co/t/help-with-the-spaces-package-documentation/111845/4 "2024-10-14T12:18:44Z")

</div>

Well, it’s really a situation we can only laugh at…😇  
The pip says he is the maintainer, but I don’t know if he is the author or not…  
I guess libraries are usually maintained by more than one person.

> **[spaces](https://pypi.org/project/spaces/)**
>
> Utilities for Hugging Face Spaces

> **[Profile of cbensimon](https://pypi.org/user/cbensimon/)**
>
> The Python Package Index (PyPI) is a repository of software for the Python programming language.

Maybe.

> **[cbensimon (Charles Bensimon)](https://huggingface.co/cbensimon)**
>
> User profile of Charles Bensimon on Hugging Face