indygreg / indygreg/PyOxidizer

can't install missing modules behind company firewall which does not allow automated downloads

Open
#654 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
6.2k
Forks
256
PR merge metrics
No merged PRs in 30d

Description

### can't install missing modules behind company firewall which does not allow automated downloads

=> I suggest to advise a directory where to copy the missing module downloaded manually
=> --verbose does not expose a traceback in this case which would be helpful to locate the calling code and solve this issue by its own.

_copied from command window:_
"""
error[PYOXIDIZER_BUILD]: error sending request for url (https://github.com/indygreg/python-build-standalone/releases/download/20221106/cpython-3.10.8%2B20221106-x86_64-pc-windows-msvc-shared-pgo-full.tar.zst): error trying to connect: tcp connect error: No connection could be made because the target machine actively refused it. (os error 10061)

Caused by:
0: error trying to connect: tcp connect error: No connection could be made because the target machine actively refused it. (os error 10061)
1: tcp connect error: No connection could be made because the target machine actively refused it. (os error 10061)
2: No connection could be made because the target machine actively refused it. (os error 10061)
--> .\pyoxidizer.bzl:19:14
|
19 | policy = dist.make_python_packaging_policy()
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ resolve_distribution
"""

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with pyoxidizer.bzl:19 and the resolve_distribution call shown in the error, then trace the failed request for the CPython archive. Check how missing modules and downloads are handled when network access is unavailable. Done should cover a documented or supported manual-download path and provide the requested diagnostic traceback if both are in scope.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, rust
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.