Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cookiecutter vs cruft #28

Closed
turbomam opened this issue Nov 28, 2022 · 3 comments
Closed

cookiecutter vs cruft #28

turbomam opened this issue Nov 28, 2022 · 3 comments

Comments

@turbomam
Copy link

TL;DR:

Because no versions of cruft match >2.11.1,<3.0.0
 and cruft (2.11.1) depends on cookiecutter (>=1.7), cruft (>=2.11.1,<3.0.0) requires cookiecutter (>=1.7).
So, because cookiecutter depends on cruft (^2.11.1)
 and cookiecutter is 0.1.0, version solving failed.

Full log

MAM@MAM-M74 gitrepos % mkdir cookiecutter
MAM@MAM-M74 gitrepos % cd cookiecutter 
MAM@MAM-M74 cookiecutter % poetry init

This command will guide you through creating your pyproject.toml config.

Package name [cookiecutter]:  
Version [0.1.0]:  
Description []:  
Author [Mark A. Miller <[email protected]>, n to skip]:  
License []:  
Compatible Python versions [^3.9]:  

Would you like to define your main dependencies interactively? (yes/no) [yes] 
You can specify a package in the following forms:
  - A single name (requests): this will search for matches on PyPI
  - A name and a constraint (requests@^2.23.0)
  - A git url (git+https://github.com/python-poetry/poetry.git)
  - A git url with a revision (git+https://github.com/python-poetry/poetry.git#develop)
  - A file path (../my-package/my-package.whl)
  - A directory (../my-package/)
  - A url (https://example.com/packages/my-package-0.1.0.tar.gz)

Package to add or search for (leave blank to skip): 

Would you like to define your development dependencies interactively? (yes/no) [yes] 
Package to add or search for (leave blank to skip): 

Generated file

[tool.poetry]
name = "cookiecutter"
version = "0.1.0"
description = ""
authors = ["Mark A. Miller <[email protected]>"]
readme = "README.md"

[tool.poetry.dependencies]
python = "^3.9"


[build-system]
requires = ["poetry-core"]
build-backend = "poetry.core.masonry.api"


Do you confirm generation? (yes/no) [yes] 
MAM@MAM-M74 cookiecutter % 
MAM@MAM-M74 cookiecutter % poetry add click==8.0.4
Creating virtualenv cookiecutter-Q1nVBc__-py3.9 in /Users/MAM/Library/Caches/pypoetry/virtualenvs

Updating dependencies
Resolving dependencies... (0.1s)

Writing lock file

Package operations: 1 install, 0 updates, 0 removals

  • Installing click (8.0.4)
MAM@MAM-M74 cookiecutter % poetry install
Installing dependencies from lock file

No dependencies to install or update
MAM@MAM-M74 cookiecutter % poetry add cruft
Using version ^2.11.1 for cruft

Updating dependencies
Resolving dependencies... (0.0s)

Because no versions of cruft match >2.11.1,<3.0.0
 and cruft (2.11.1) depends on cookiecutter (>=1.7), cruft (>=2.11.1,<3.0.0) requires cookiecutter (>=1.7).
So, because cookiecutter depends on cruft (^2.11.1)
 and cookiecutter is 0.1.0, version solving failed.

@turbomam
Copy link
Author

Maybe I fouled things up by calling my initial directory cookiecutter?

I started over with an initial directory of eq-expr-sandbox. poetry install and make setup seem to have run to completion.

@turbomam
Copy link
Author

@pkalita-lbl
Copy link
Contributor

This appears to be based on the old setup instructions. With #84 the instructions have been rewritten to advise using pipx. I don't think you'll come across the same issue as described here using those instructions, but if you do feel free to reopen this issue. If you run into a different issue, please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants