the function has been moved to Solver

fixes error

  AttributeError

  'Installer' object has no attribute 'remove_untracked'

  at ~/.asdf/installs/python/3.8.5/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/poetry_bundle_plugin/bundlers/venv_bundler.py:133 in bundle
      129│             poetry.locker,
      130│             poetry.pool,
      131│             poetry.config,
      132│         )
    → 133│         installer.remove_untracked()
      134│         installer.use_executor(poetry.config.get("experimental.new-installer", False))
      135│
      136│         return_code = installer.run()
      137│         if return_code:

By making BundleCommand inherit from poetry's GroupCommand, and passing the detected groups through to the venv bundler.

Fixes https://github.com/python-poetry/poetry-plugin-bundle/issues/8

Hi,

Thanks for putting together this useful tool. I don't seem to be able to install it though, and get the following error.

`$ poetry --version Poetry (version 1.2.0b1) $ poetry plugin add poetry-plugin-bundle

Could not find a matching version of package poetry-plugin-bundle `

Any ideas on how to resolve it?

Thanks,

Hi I've encountered an issue where when using the plugin it does work with internal packages (packages I import as: lib1 = {path = "../../../poetry/lib1", develop = true} for example).

The issue is that when lib1 himself is importing another internal package, for example: lib2 = {path = "../lib2", develop = true}

the output bundle doesn't contain lib2. So it seems the plugin only works on the first level of internal packages, is it possible to add the ability to bundle all the project packages?

Hey all.

After some strugle trying to find the correct versions that supports the commands needed to install poetry-plugin-bundle, I'm still finding some issues.

Using 1.1.14

curl -sSL https://install.python-poetry.org | python3 -
poetry --version
# Poetry version 1.1.14
poetry self add poetry-plugin-bundle

Using 1.2.0b3

curl -sSL https://install.python-poetry.org | python3 - --preview
# Poetry (version 1.2.0b3)
poetry self add poetry-plugin-bundle
#
# Could not find a matching version of package poetry-plugin-bundle

Using 1.2.0b3, accounting for #17

poetry self add poetry-bundle-plugin
# Using version ^0.1.0 for poetry-bundle-plugin
# 
# Updating dependencies
# Resolving dependencies... (1.1s)
# 
# Writing lock file
# 
# Package operations: 1 install, 0 updates, 0 removals
# 
#   • Installing poetry-bundle-plugin (0.1.0)
poetry bundle venv test_env
# cannot import name 'temporary_directory' from 'poetry.utils.helpers' (/home/<myuser>/.local/share/pypoetry/venv/lib/python3.8/site-packages/poetry/utils/helpers.py)

What is the correct poetry version to use with poetry-bundle?

Hi

I'm in a search for a way to build a package for my monorepo project including the internal packages. This plugin seems like it is exactly what I need but I'm encountering an issue when trying to use the build output.

Trying to run the activate script of poetry inside the dockerfile, running: . venv/bin/activate

It seems to activate the virtual environment but it doesn't find the python packages in projects. Running python -m site inside the virtual environment results in: (build) root@69ec21d33c0d:/app# python -m site sys.path = [ '/app', '/usr/local/lib/python38.zip', '/usr/local/lib/python3.8', '/usr/local/lib/python3.8/lib-dynload', '/usr/local/lib/python3.8/site-packages', ] USER_BASE: '/root/.local' (doesn't exist) USER_SITE: '/root/.local/lib/python3.8/site-packages' (doesn't exist) ENABLE_USER_SITE: True

Which isn't the correct site-packages path.

What is the correct way using this plugin out with docker container?

I tried bundeling my project with this plugin and got the following error:

Trashtalk:project$ poetry bundle venv ~/Programming/project/test

  • Bundling evm_backend (0.1.0) into /home/nathan/Programming/project/test: Installing dependencies

  AttributeError

  'Installer' object has no attribute 'remove_untracked'

  at ~/.local/share/pypoetry/venv/lib/python3.10/site-packages/poetry_bundle_plugin/bundlers/venv_bundler.py:133 in bundle
      129│             poetry.locker,
      130│             poetry.pool,
      131│             poetry.config,
      132│         )
    → 133│         installer.remove_untracked()
      134│         installer.use_executor(poetry.config.get("experimental.new-installer", False))
      135│ 
      136│         return_code = installer.run()
      137│         if return_code:

I don't know why this doesn't work, since I have a completely fresh install of both poetry and this plugin. I did some minor detective work and found out that remove_untracked doesn't exist in this file at least. Should I downgrade to an earlier 1.2 pre-release?

It's a bit weird that this is poetry-bundle-plugin, but export is poetry-plugin-export. I suspect it's best to pick one of the two naming formats and sticking to it.

updates:

• github.com/psf/black: 20.8b1 → 21.12b0
• https://gitlab.com/pycqa/flake8 → https://github.com/PyCQA/flake8
• github.com/PyCQA/flake8: 3.8.4 → 4.0.1
• https://github.com/timothycrosley/isort → https://github.com/PyCQA/isort
• github.com/PyCQA/isort: 5.7.0 → 5.10.1
• github.com/pre-commit/pre-commit-hooks: v3.4.0 → v4.0.1

updates:

• github.com/psf/black: 20.8b1 → 21.11b1
• https://gitlab.com/pycqa/flake8 → https://github.com/PyCQA/flake8
• github.com/PyCQA/flake8: 3.8.4 → 4.0.1
• https://github.com/timothycrosley/isort → https://github.com/PyCQA/isort
• github.com/PyCQA/isort: 5.7.0 → 5.10.1
• github.com/pre-commit/pre-commit-hooks: v3.4.0 → v4.0.1

updates:

• github.com/psf/black: 20.8b1 → 21.10b0
• https://gitlab.com/pycqa/flake8 → https://github.com/PyCQA/flake8
• github.com/PyCQA/flake8: 3.8.4 → 4.0.1
• https://github.com/timothycrosley/isort → https://github.com/PyCQA/isort
• github.com/PyCQA/isort: 5.7.0 → 5.10.1
• github.com/pre-commit/pre-commit-hooks: v3.4.0 → v4.0.1

I know that poetry install can detect conda environment automatically and install dependencies to the current activate environment. But the problem if poetry install is there is no way to make it ignore the editable dependencies. I don't know if bundle plugin support this. It would be good to have some doc about it, thank you.

Hi,

I would like to ask if this is a good idea to add an option to save bundled venv to .zip or tar.gz file. The usecase is for providing pyspark code and dependencies, it supports venv-pack tar.gz file which basically works the same as this bundle plugin, except it creates tar.gz file. See: https://spark.apache.org/docs/latest/api/python/user_guide/python_packaging.html#using-virtualenv

updates:

• github.com/pre-commit/pre-commit-hooks: v4.3.0 → v4.4.0
• github.com/asottile/pyupgrade: v3.2.2 → v3.3.1
• github.com/pycqa/isort: 5.10.1 → 5.11.4
• github.com/psf/black: 22.10.0 → 22.12.0
• github.com/pycqa/flake8: 5.0.4 → 6.0.0

For dependencies marked as editable, this plugin will create .pth files including the local location of the path-based dependency. In that sense, the dependency is not bundled.

Is there a reason for a bundled install to observe the "develop = true" flag? If so, can we have an option to install these packages as non-editable instead? According to my reading of https://github.com/python-poetry/poetry/issues/1382#issuecomment-1266291854, this bundler is supposed to handle that installation case.

poetry 1.2.1
poetry-core 1.2.0 poetry-plugin-bundle 1.1.0

Using windows WSL2 with debian and python3.7, I just migrated to poetry 1.2.2 and wanted to try the new bundle plugin that would allow me to build faster in my CI.

I innocently typed

poetry bundle venv .

as I wanted the bundle to be in the current folder. The command started and showed

Bundling xxx_gateway (1.1.1) into .: Removing existing virtual environment

and then

[Errno 22] Invalid argument: '.'

In the meantime my folder had been emptied (no consequence git was here)

I think other people could try to bundle in there local folder so I suggest adding an exception for the dot path. Maybe using ./bundle as a default could be interesting in some automation process as well.