QuantEcon / QuantEcon/lecture-python-intro

Link Checker Report

Open
#718 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

automated linkchecker report
Dominant language
Jupyter Notebook
Stars
65
Forks
32
Avg merge
4d 14h
Merged PRs (30d)
6

Description

Summary

Status Count
πŸ” Total 7365
βœ… Successful 6152
⏳ Timeouts 0
πŸ”€ Redirected 1
πŸ‘» Excluded 1
❓ Unknown 0
🚫 Errors 1211
β›” Unsupported 0

Errors per input

Errors in about.html
Errors in ar1_processes.html
Errors in business_cycle.html
Errors in cagan_adaptive.html
Errors in cagan_ree.html
Errors in cobweb.html
Errors in commod_price.html
Errors in complex_and_trig.html
Errors in cons_smooth.html
Errors in eigen_I.html
Errors in eigen_II.html
Errors in equalizing_difference.html
Errors in french_rev.html
Errors in genindex.html
Errors in geom_series.html
Errors in greek_square.html
Errors in heavy_tails.html
Errors in inequality.html
Errors in inflation_history.html
Errors in input_output.html
Errors in intro.html
Errors in intro_supply_demand.html
  • [ERROR] error: | Error building URL for "/_notebooks/intro_supply_demand.ipynb" (Attribute: Some("href")): Cannot convert path '/_notebooks/intro_supply_demand.ipynb' to a URI: To resolve root-relative links in local files, provide a root dir
  • [ERROR] error: | Error building URL for "/_pdf/quantecon-python-intro.pdf" (Attribute: Some("href")): Cannot convert path '/_pdf/qu...[Issue body truncated]

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up β€” it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the link-checker errors listed for about.html, ar1_processes.html, and business_cycle.html, then inspect the referenced root-relative notebook and PDF paths alongside the external FRED links. Done means the affected links are resolved or appropriately handled and a rerun no longer reports these errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
jupyter-notebook
Domain
documentation
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.