gluonts: Cannot use R models in version 0.11.x--follow up
Description
This is a follow-up bug report to #2414.
Problem: Some *.R files are missing when installing gluonts 0.11.x via poetry.
To Reproduce
I reproduced like this:
- fresh poetry projects for both gluonts 0.9.x (the version we’re using right now) and gluonts 0.11.x (the one we want to use)
- both use python 3.8.x and poetry 1.2.x (i’m using a poetry beta, a team mate has the same issue with the most recent poetry version 1.2.2)
Result:
- *.R files are there for 0.9.x and none is there for 0.11.x
- both versions have a folder of *.R files, see here for 11 and here for 9
I provide two code blocks (of one shell sessions) how to reproduce.
/tmp> python --version
Python 3.8.10
/tmp> poetry --version
Poetry (version 1.2.0b1)
/tmp> mkdir gluonts11
/tmp> mkdir gluonts9
/tmp> cd gluonts11
/tmp/gluonts11> echo "[virtualenvs]\nin-project = true" >> poetry.toml
/tmp/gluonts11> cat poetry.toml
[virtualenvs]
in-project = true
/tmp/gluonts11> poetry init
This command will guide you through creating your pyproject.toml config.
Package name [gluonts11]:
Version [0.1.0]:
Description []:
Author [Bert Besser <...>, n to skip]:
License []:
Compatible Python versions [^3.8]:
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)
- 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)
Search for package to add (or leave blank to continue): gluonts@^0.11.2
Adding gluonts@^0.11.2
Add a package:
Would you like to define your development dependencies interactively? (yes/no) [yes] no
Generated file
[tool.poetry]
name = "gluonts11"
version = "0.1.0"
description = ""
authors = ["Bert Besser <...>"]
readme = "README.md"
[tool.poetry.dependencies]
python = "^3.8"
gluonts = "^0.11.2"
[build-system]
requires = ["poetry-core"]
build-backend = "poetry.core.masonry.api"
Do you confirm generation? (yes/no) [yes]
/tmp/gluonts11> poetry install
Creating virtualenv gluonts11 in /tmp/gluonts11/.venv
Updating dependencies
Resolving dependencies... (0.6s)
Writing lock file
Package operations: 10 installs, 0 updates, 0 removals
• Installing six (1.16.0)
• Installing numpy (1.23.5)
• Installing python-dateutil (2.8.2)
• Installing pytz (2022.6)
• Installing typing-extensions (4.4.0)
• Installing pandas (1.5.2)
• Installing pydantic (1.10.2)
• Installing toolz (0.12.0)
• Installing tqdm (4.64.1)
• Installing gluonts (0.11.2)
/tmp/gluonts11> find .venv | grep "\.R"
exit 1
/tmp/gluonts11> # no R files here for 0.11.x
So there are no *.R files for 0.11.x.
… continuing in the same shell session …
/tmp/gluonts11> cd ../gluonts9
/tmp/gluonts9> echo "[virtualenvs]\nin-project = true" >> poetry.toml
/tmp/gluonts9> poetry init
This command will guide you through creating your pyproject.toml config.
Package name [gluonts9]:
Version [0.1.0]:
Description []:
Author [Bert Besser <...>, n to skip]:
License []:
Compatible Python versions [^3.8]:
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)
- 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)
Search for package to add (or leave blank to continue): gluonts@^0.9.4
Adding gluonts@^0.9.4
Add a package:
Would you like to define your development dependencies interactively? (yes/no) [yes] no
Generated file
[tool.poetry]
name = "gluonts9"
version = "0.1.0"
description = ""
authors = ["Bert Besser <...>"]
readme = "README.md"
[tool.poetry.dependencies]
python = "^3.8"
gluonts = "^0.9.4"
[build-system]
requires = ["poetry-core"]
build-backend = "poetry.core.masonry.api"
Do you confirm generation? (yes/no) [yes]
/tmp/gluonts9> poetry install
Creating virtualenv gluonts9 in /tmp/gluonts9/.venv
Updating dependencies
Resolving dependencies... (1.3s)
Writing lock file
Package operations: 25 installs, 1 update, 0 removals
• Installing pyparsing (3.0.9)
• Installing numpy (1.23.5)
• Installing packaging (21.3)
• Installing pymeeus (0.5.11)
• Updating setuptools (65.3.0 -> 65.6.0)
• Installing six (1.16.0)
• Installing tomli (2.0.1)
• Installing typing-extensions (4.4.0)
• Installing contourpy (1.0.6): Installing...
• Installing contourpy (1.0.6)
• Installing convertdate (2.4.0)
• Installing cycler (0.11.0)
• Installing fonttools (4.38.0)
• Installing hijri-converter (2.2.4)
• Installing kiwisolver (1.4.4)
• Installing korean-lunar-calendar (0.3.1)
• Installing pillow (9.3.0)
• Installing python-dateutil (2.8.2)
• Installing pytz (2022.6)
• Installing setuptools-scm (7.0.5)
• Installing holidays (0.17)
• Installing matplotlib (3.6.2)
• Installing pandas (1.5.2)
• Installing pydantic (1.10.2)
• Installing toolz (0.12.0)
• Installing tqdm (4.64.1)
• Installing gluonts (0.9.9)
/tmp/gluonts9> find .venv | grep "\.R"
.venv/lib/python3.8/site-packages/gluonts/model/r_forecast/R/forecast_methods.R
tmp/gluonts9> # for 0.9.x there is an R file
So there is an *.R file for 0.9.x.
Error message or code output
I will ask my colleague to paste some error message in the following comments.
Environment
- Operating system: linux
- Python version: 3.8.x
- GluonTS version: 0.11.x resp. 0.9.x
- MXNet version: ?
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 15 (8 by maintainers)
Hi I tested via
poetry add "git+https://github.com/lostella/gluon-ts.git#5d08ce"from your fork @lostella and the .R files were there. I see you have already merged it! 🙏This was quick! Do you already have an idea when this will be available in the 0.11.x branch, or even published to pypi? (Asking to arrange our time/prios in the project.)