deps: update python-telegram-bot requirement from <22,>=21.0 to >=21.0,<23#8
Closed
dependabot[bot] wants to merge 1 commit intomasterfrom
Closed
Conversation
Updates the requirements on [python-telegram-bot](https://github.com/python-telegram-bot/python-telegram-bot) to permit the latest version. - [Release notes](https://github.com/python-telegram-bot/python-telegram-bot/releases) - [Commits](python-telegram-bot/python-telegram-bot@v21.0...v22.7) --- updated-dependencies: - dependency-name: python-telegram-bot dependency-version: '22.7' dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Owner
|
의존성 범위 변경은 수동 검증 후 적용 |
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
eddmpython
added a commit
that referenced
this pull request
Apr 7, 2026
Plan v5 후 SK하이닉스 review 1막~6막 line by line 읽기. 3막 (현금전환) - ✅ 영업CF 53.4조, FCF 24.8조, OCF/NI 124% 정상 - ❌ #5: 재무CF 2025 결손 (`-`) — snakeId 매핑 또는 분기 데이터 부족 4막 (안정성) - ✅ 부채비율 46%, Z-Score 5.55 안전, 차입금 fallback 정확 (Plan v5 P5) - ❌ #6: notes.borrowings 시계열 4년만 (2022 이전 `-`) - ❌ #7: parser 가 sub-row 헤더 ("OAT Nego, Banker's Usance" 등) 를 데이터 row 로 추출 - ❌ #8: notes.lease 표 분기/연간 혼합 가능 5막 (자본배분) - ✅ 배당 5221억, CAPEX 28.6조, FCF 사용처 정확 - ❌ #9: 배당성장률 +8600.8% (2021 47억 → 2022 4126억 base effect) 6막 (가치평가) - ✅ DCF/DDM/RIM/상대가치 4 모델 + 확률가중 목표가 5 시나리오 - ❌ #10: 종합 적정가 19.7만원 vs 확률가중 목표가 129.7만원 (6배 차이) — 사용자 혼란 - ❌ #11: RIM/DCF 단위 표시 불명확 (원/주당) ops/reviewAudit.md 갱신 — Plan v4/v5 root fix 후 단위/Q4 함정 섹션 정정.
eddmpython
added a commit
that referenced
this pull request
Apr 21, 2026
독자 평가(설명글 이해도 기준) 결과 약한 막 2곳 보강: (1) §Pyodide 섹션에 WebAssembly 한 문단 + "브라우저가 .wasm으로 인터프리터 통째로 받는다" 인과 + Pyodide→xlwings Lite 다리 명시, (2) §제약 도입부 '세→네' 정정 + CORS를 "허락 도장" 비유로 풀이 + scan 271MB는 "일반 웹페이지의 100배" 감각. 본문·정리 숫자 불일치 1건(제약 셋→넷) 정합. 상단 OneDrive 링크는 dl-primary CTA 버튼으로 승격.
eddmpython
added a commit
that referenced
this pull request
Apr 21, 2026
Pyodide 미경험자에게 가장 걸리는 추상 3지점을 시각화: (1) pyodide-vs-python — 런타임 위치·설치·파일시스템 등 8항목 2열 카드 비교, (2) install-flow-compare — 일반 Python 5단계 vs Pyodide 1단계 타임라인, (3) cors-permission — 허락 도장 있음 vs 없음 2장면 비유. 각 SVG는 텍스트 문단 직후에 배치해 추상→시각→구체 예시 순서로 흐름이 이어지게 함. 독자 에이전트 재평가 95→97, 제약 섹션 복선까지 SVG1이 미리 깔아주는 구조.
eddmpython
added a commit
that referenced
this pull request
Apr 21, 2026
매출 5조·영업이익률 8.6%에 주가 3배 — HD현대일렉트릭(#8) 24% 대비 1/3 마진으로도 AI·IRA·재생에너지 3대 테마 수혜를 받은 다품종 B2B 구조. 주요 내용: - 2016 매출 3.77조 → 2019 2.35조 (-38%, 사업 재편) → 2025 4.97조 (+111%) - 영업이익률 5.6% → 8.6% (+3%p): 고마진 제품 비중 + 텍사스 IRA + 자동화 확대 - 2024 순이익 2,422억 사상 최대 → 2025 2,170억 -10% (금융·법인세 악화) - HD현대일렉트릭(단일제품 Boutique) vs LS(다품종 Conglomerate) 대조 - 주가 4.5배 상승의 정체 = PER 7→32배 멀티플 확대 (순이익은 불변) - 부채비율 131%지만 선수금+매입채무 73% · 실질 차입금은 자본의 24% - 10막에서 #8·#63·#64·#65 4사 AI 공급망 매핑 완성 에셋: - SVG 7장 (opm-vs-hdelec/segments/opm-decomposition/debt-structure/global-peers/quarterly-opm/checkpoints) - FLUX 3장 (데이터센터 스위치기어 룸 · 텍사스 공장 · 썸네일) - 썸네일 + AUTO 영역 sync_financials 검증: SEO 96% 🟢 22,921자 · 검증표 24개 항목 · dCR-A-
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates the requirements on python-telegram-bot to permit the latest version.
Release notes
Sourced from python-telegram-bot's releases.
Commits
5a41d2bBump Version to v22.7 (#5176)108bfafDocumentation Improvements (#5119)3fd6932Lock file maintenance (#5175)22c31b1Update sigstore/gh-action-sigstore-python action to v3.2.0 (#5172)dd8c60fUpdate stefanzweifel/git-auto-commit-action action to v7.1.0 (#5173)5bc0f4fUpdate actions/checkout action to v6 (#5174)80f3ccdUpdate GitHub Artifact Actions (major) (#5171)537693fUpdate dependency astral-sh/uv to v0.10.10 (#5169)72e8dedUpdate astral-sh/setup-uv action to v7.5.0 (#5170)a48b08fBump Sphinx Related Dependencies, Fixuvand Docs Build (#5168)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)