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.

[BUG] Invalid string type when reading declarative `setup.cfg` under Python 2

See original GitHub issue

Hi,

I’m seeing the following error:

error: 'egg_base' must be a directory name (got `src`)

The config contains:

[options]
...
package_dir =
     = src

Contents of package_dir is

{u'': u'src'}

(I’ve worked around this by manually reading config and patching this applying str() to keys and vars)

Python: 2.7 OS: GNU/Linux

The issue appears to be the same as for:

ref #190
ref #597

Issue Analytics

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

Top GitHub Comments

1reaction

jaracocommented, Jan 27, 2019

Work in #1180 released as 40.7.0.

0reactions

aarchibacommented, Oct 16, 2019

We have users still reporting this with setuptools 41.4

Top Results From Across the Web

pyproject.toml won't find project name with setuptools python

At the time the question was asked, setuptools did not have support for writing its configuration in a pyproject.toml file (PEP 621). So...

Specifying package version in `setup.py` - Python Help

I'm trying to upload my first package to PyPI. I'm specifying version="0.1.0" in setup.py, and version = 0.1.0 in setup.cfg.

Configuring setuptools using setup.cfg files

Setuptools allows using configuration files (usually setup. cfg ) to define a package's metadata and other options that are normally supplied to the...

Frequently Asked Questions - PyScaffold 4.3.1 documentation

Can I use PyScaffold ≥ 3 to develop a Python package that is Python 2 & 3 ... the declarative configuration with setup.cfg...

Changelog — PyJWT 2.0.1 documentation

We no longer need to use mypy Python 2 compatibility mode (comments) ... Move setup information to declarative setup.cfg (#495) by @jdufresne ...