poetry: Python 3.8 - "TypeError: expected string or bytes-like object" with poetry install

This will also happen if you somehow end up with an .egg-info file (presumably malformatted) in your project directory. I think I created one unintentionally while experimenting with dephell, but regardless of the source this is what you can expect to see:

myproject % touch myproject.egg-info
myproject % poetry check
All set!
myproject % poetry show

[TypeError]
expected string or bytes-like object
myproject % rm myproject.egg-info
myproject % poetry show
aiohttp                        3.6.2     Async http client/server framework (asyncio)
....

What is the solution to this? This ticket is closed, but I am still getting the issue. I have read every comment here and did not see what allowed this to be closed. If this is fixed in some version of poetry, can someone please be explicit about which specific version of poetry this is fixed in? Thank you.

For me it was also due to activated conda environment. So it was fixed by conda deactivate

This issue still exists in the latest 1.1.7

I solved this problem by deleting the virtual environment. First you can get ENV_NAME by typing poetry env list, and then typing poetry env remove ENV_NAME to delete this virtual environment.

Seeing the exact same issue, but on Python 3.7.2 and poetry 1.0.3. Downgrading to poetry 1.0.2 made no difference.

I met this bug again in poetry==1.1.0 on windows.

Hi, I experience the same issue, and eventually traced it to this:

class InstalledRepository(Repository):
    @classmethod
    def load(cls, env):  # type: (Env) -> InstalledRepository
        """
        Load installed packages.

        For now, it uses the pip "freeze" command.
        """
        repo = cls()
        seen = set()

        print(env.sys_path)
        for entry in env.sys_path:
            if not entry:
                continue
            print('entry', repr(entry))

e.g. at this point env.sys_path contains an empty string as the first item, which somehow eventually leads to ‘name’ passed to canonicalize_name being None skipping the empty entry as i did here seems to fix it for now

@repnop It would be more helpful for you if you communicated meaningful information, such as the pyproject.toml, the name of the git dependency that causes the issue, the full console output showing the error message.

Hitting this on a fresh project, with 1.1.4 latest release installed via pip

edit: I commented out a git dep and now it let me poetry install, not sure if that’s related or useful info

@abn OK, I’ll create a repo with github actions to reproduce it.

In my case, I moved pyproject.toml to the root directory of the git repository and that fixed the problem. But the error occurred if pyproject.toml was placed in the sub directory.

OK

git repository root/ 　├ pyproject.toml 　├ src/

NG

git repository root/ 　├ src/ 　 　└ pyproject.toml

(repository = GitHub repository of poetry package)

My idea is that this error will occur allways if the name of installed package is missing for poetry.

I want install some package shared between my projects on the development machine (something like -e mode of pip). I create empty mypackage/ and inside mypackage/mypackage/ with code.

Now: Both poetry add mypackage/ and poetry add mypackage/mypackage/ will fail with the error above.

Then I create mypackage/setup.py with setup(name='mypackage', .....). And now: poetry add mypackage/` will install the editable package without problems.

Minimum setup.py content for this goal is:

from setuptools import setup
setup(name='mypackage')

Maybe this will help to identify the reasons more exactly?

Same here. I can’t get to workaround this with a git dependency.

@sinoroc its an internal work project so the git dependency is not public, but its a simple

dep = { git = "git://a.url/dep" }

the full error is exactly the same as above, and I did hit it when trying to install aiomysql or sanic before that (but it hasn’t happened with them since I fixed? whatever the problem was there). I tried deleting the venv multiple times and reinstalling the dependencies.