Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add section to docs about empty packages for specific python versions

See original GitHub issue

I read the conda-forge documentation and could not find the solution for my problem there.

Issue:

There are some packages in python that include features added to later python versions like dataclasses and typing_extensions.

Originally, they could only be installed under specific python versions which meant that packages that depend on those cannot be noarch: python. This has been solved by creating empty packages for specific python versions like in dataclasses and typing.

If this is something that will become more widespread, it might be good to have his mentioned in the docs as new maintainers are normally not aware of this (One example is here and another one was me 😄).

Issue Analytics

State:
Created 3 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

BastianZimcommented, Mar 19, 2021

Ok no worries, then I’ll just add something to the docs.

0reactions

beckermrcommented, Mar 19, 2021

Sorry I missed these messages! Yes, those sections above are fine. We do not have a database.

Top Results From Across the Web

Packaging Python Projects

This tutorial walks you through how to package a simple Python project. It will show you how to add the necessary files and...

2. Writing the Setup Script — Python 3.11.1 documentation

As we saw in section A Simple Example above, the setup script consists mainly ... The keys to this dictionary are package names,...

6. Modules — Python 3.11.1 documentation

To speed up loading modules, Python caches the compiled version of each module in the __pycache__ directory under the name module.version.pyc , where...

Installing Python Modules (Legacy version)

The most convenient way is to add a path configuration file to a directory that's already on Python's path, usually to the .../site-packages/...

__main__ — Top-level code environment — ...

“Top-level code” is the first user-specified Python module that starts running. It's “top-level” because it imports all other modules that the program needs ......