Releases: merwanroudane/econenv
Release list
v1.0.9: EconEnv 1.0.9
1.0.9 — 2026-09-05
A documentation release. No code changed; its purpose is a PyPI page whose links work.
Fixed
Every link in the README returned 404 on PyPI. The README is also the PyPI long description, and PyPI resolves a relative link like docs/guide/econenv-guide.pdf against pypi.org/project/econenv// rather than against the repository. All twenty were therefore correct on GitHub and broken for anyone arriving from PyPI — including the User Guide, Examples and Changelog links in the header row.
All twenty are now absolute https://github.com/... URLs, and two tests keep them that way: no relative links may appear in the README, and every repository link must point at a file that exists. The check matches on the link target alone, because a text pattern cannot see — which is how the licence badge survived the first pass of the fix.
The released version is now linked from the site hero, both example notebooks and the guide's title page, each deriving the number from the package rather than repeating it.
Published to PyPI: https://pypi.org/project/econenv/1.0.9/
EconEnv 0.1.7
0.1.7 — 2026-09-04
Google Colab support, and a correction to what I had claimed about it.
Added
Colab detection. discovery.is_colab() reads COLAB_RELEASE_TAG, COLAB_GPU or the google.colab module, and doctor reports the environment by name with what can and cannot run there.
examples/11_colab_quickstart.ipynb with an Open in Colab badge: one %pip install econenv, then a Python + R workflow on the same real macro data as the four-engine notebook.
All four engines in Colab, via a local runtime. Colab already runs in a browser on your own PC, so it can be pointed at a Jupyter server on that same PC: the interface stays Colab while the kernel — and therefore Python, R, Stata and EViews — is your Windows machine. Nothing is exposed to the internet, so this is not the prohibited "web server access to EViews via COM".
It needs the classic Jupyter stack, and that was measured rather than assumed. jupyter_http_over_ws was last released in March 2020 and is a notebook 5/6 server extension: on notebook 7.5.5 and 6.5.7 — both on jupyter_server 2 — enabling it fails and /http_over_websocket returns 404. Pinned to notebook==6.4.12 it validates and the probe returns HTTP 400, the endpoint waiting for Colab's websocket upgrade.
A Colab chapter in the printed guide, and a Colab section on the documentation site and in docs/installation.md.