Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Link Checker Report

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
jupyter-notebook
Domain
documentation

Research direction

The report names generated pages including about.html, ar1_processes.html, business_cycle.html, and cagan_adaptive.html; start by tracing these pages to their source content and checking whether the listed errors are real broken links or checker responses. Done means the actionable link-checker errors are resolved or appropriately accounted for across the reported pages.

Written by the indexing model from the issue text.

Description

automated linkchecker report

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
Dominant language
Jupyter Notebook
Stars
65
Forks
32
Avg merge
5d 11h
Merged PRs (30d)
5

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

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.

More from QuantEcon/lecture-python-intro

All issues in QuantEcon/lecture-python-intro

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.