Add 18 upcoming conferences, five with open CfPs

[JesperDramsch]

Stacked on JesperDramsch/python-deadlines#494. Merge that first; GitHub then retargets this PR to main.

These conferences were found by surveying pretalx, Sessionize, the PSF events calendar, the PyCon trademark list and pycon.org, Bluesky, and developers.events and dev.events. Aggregators only served as leads. Every value below comes from the conference's own site or CfP platform, checked on 2026-10-13, and a second, independent pass tried to refute each field.

Time-sensitive

Open CfPs: PyDay Hurlingham and PyDay La Plata (both 18 Oct), PyCon Slovakia 2027 (30 Oct), PyDay Lima (15 Nov), PyTexas 2027 (11 Dec).

Needs your call

• PyDay Hurlingham: the page says "Límite de recepción: Domingo 20 de Octubre", but 20 October 2026 is a Tuesday. I listed the earlier date, Sunday the 18th, so nobody misses the deadline.
• PyTexas 2027: pretalx closes at 17:00 America/Chicago, while the website says 11:59pm CST. I used pretalx, because it is what actually closes submissions.
• PyDay Santo Domingo: the date (5 Dec) comes from the official site. developers.events says 20–21 Nov. PaperCall was unreachable, so there is no cfp_link and the cfp is TBA.
• PyCon Davao: the CfP link is the Google Form from the official FAQ, but the form needs a sign-in, so I couldn't view it.
• FOSDEM 2027: start/end span the whole conference. Python devrooms are announced on 20 October; narrow the dates once the devroom day is known.
• Naming: the data spells the series "Pytorch Day", so the new entries are "Pytorch Day Japan" and "Pytorch Day China". Plain "Pytorch Day 2026" is already the Bengaluru event, and keeping these separate stops the sort from merging them into it. Jupyter Day uses DATA,DAY, like Pytorch Day.
• Held, not added: PyTN 2026 and PyConf 2026.
  • pytn.org was registered in July 2026, names no organiser, and had no public schedule a week before the event.
  • pyconf.org was registered on 8 October 2026, yet claims a CfP that "closed 31 August" and says "sold out" while still selling early-bird tickets.

Entries

Conference	Dates	CfP	Source
PyCon Davao 2026	2026-10-17 to 2026-10-18	None	pycon-davao.durianpy.org: "17-18 October, 2026"
Jupyter Day 2026	2026-10-19	2026-09-13 23:59 PDT	events.linuxfoundation.org: "will take place on October 19, 2026"
PyDay La Plata 2026	2026-11-07	2026-10-18 23:59 AoE	eventos.python.org.ar: "Sábado 7 de Noviembre de 2026"
PyCon Chile 2026	2026-11-14 to 2026-11-15	2026-10-02 23:59 America/Santiago	sessionize.com: "event starts 14 Nov 2026 event ends 15 Nov 2026 location Santiago, Chile"
PyDay Hurlingham 2026	2026-11-14	2026-10-18 23:59 AoE	eventos.python.org.ar: "Sábado 14 de noviembre de 2026, de 9 a 17 hs."
PyDay Santo Domingo 2026	2026-12-05	TBA	pyday.do: site data "DECEMBER_5_2026", status "CONFIRMED"
Pytorch Day Japan 2026	2026-12-10	2026-09-27 23:59 JST	sessionize.com: "event date 10 Dec 2026"
PyDay Lima 2026	2026-12-11	2026-11-15 23:59 America/Lima	pylimaperu.org: "Fecha Viernes 11 de Diciembre 2026"
PyCon mini Tokyo 2026	2026-12-12	None	pyconjp.connpass.com: "開催日時：2026年12月12日（土）10:00〜19:00"
Pytorch Day China 2026	2026-12-12	TBA	lfopensource.cn: "Scheduled for 12 December in China"
FOSDEM 2027	2027-01-30 to 2027-01-31	TBA	fosdem.org: "will take place on Saturday 30th and Sunday 31st of January"
PyCon Slovakia 2027	2027-03-12 to 2027-03-13	2026-10-30 23:59 AoE	pycon.sk: "See you on 12–13 March 2027 at FIIT STU in Bratislava."
PyCon Czechia 2027	2027-04-16 to 2027-04-18	TBA	cz.pycon.org: "PyCon CZ 27, 16–18 April 2027, Pilsen"
PyTexas 2027	2027-04-16 to 2027-04-18	2026-12-11 17:00 America/Chicago	pretalx.com and pytexas.org
PyCon Italy 2027	2027-06-02 to 2027-06-05	TBA	2026.pycon.it: "PyCon Italia 2027, from June 2 to June 5, 2027, at the Savoia Regency Hotel."
PyCon Russia 2027	2027-07-24	2027-05-15 23:59 AoE	pycon.ru: "24 июля 2027 Москва"; pycon.ru/cfp
PyCon Japan 2027	2027-09-24 to 2027-09-26	TBA	2027.pycon.jp: "日程: 2027年09月24日-2027年09月26日"
PyTorch Conference 2027	2027-10-06 to 2027-10-07	TBA	events.linuxfoundation.org: event data 2027-10-06 to 2027-10-07

Checks

• python utils/sort_yaml.py --skip_links completed. It validates every entry against the schema, and its geocoding step added the locations.
• pre-commit passed on the changed file.
• pytest tests/: no new failures. The same 10 tests fail on an untouched checkout because the local environment has pandas 3.0.5 (the project pins <2.3); CI uses the pinned versions.

🤖 Generated with Claude Code

https://claude.ai/code/session_01QzyF2ciB5jhvcTVpj4ErMr

---

Generated by Claude Code

[JesperDramsch]

Routine review

1. Request

No linked issue; the request is the PR description: add 18 upcoming conferences to _data/conferences.yml, each value taken from the conference's own site or CfP platform. The 18 are PyCon Davao, Jupyter Day, PyDay La Plata, PyCon Chile, PyDay Hurlingham, PyDay Santo Domingo, Pytorch Day Japan, PyDay Lima, PyCon mini Tokyo, Pytorch Day China, FOSDEM, PyCon Slovakia, PyCon Czechia, PyTexas, PyCon Italy, PyCon Russia, PyCon Japan and PyTorch Conference. The diff adds exactly these 18 entries and touches only _data/conferences.yml.

2. Checked against

Date: Wed Oct 14 00:04 UTC 2026.

• I fetched no external URLs. The sandbox proxy answered 403 for https://2027.pycon.it/en and https://2026.pycon.it/en.
• unverified: every conference date, CfP deadline and link in the PR table. I compared the diff to the PR's own table but not to the conference sites.
• unverified: "20 October 2026 is a Tuesday". I did not check the calendar, but I checked the claim against date arithmetic from today (Wed 14 Oct), which gives Tuesday.

3. Needs your decision

1. PyCon Italy link. The entry uses https://2027.pycon.it/en, but the PR's cited source is https://2026.pycon.it/en. I could not tell whether the 2027 site is live. Recommendation: confirm it resolves; if not, use the 2026 URL until the 2027 site exists.
2. PyCon Russia 2027. This is a Moscow-hosted event. Whether the calendar should list it is your editorial call. Recommendation: keep it only if you list events regardless of host country; I have no repository rule on this.
3. Stacked base. The base is ai-agent/exciting-tesla-g7fn0r (PR Repair lost and wrong conference data; stop the new-year job deleting entries #494), not main. This review is of the delta against that branch. Recommendation: merge Repair lost and wrong conference data; stop the new-year job deleting entries #494 first, as the PR says.
4. Held-back entries. The description says PyTN 2026 and PyConf 2026 were held back. I agree with holding them, but it is your call whether they belong in a follow-up.
5. Date-dependent items, judged on 2026-10-14.
   • PyCon Chile's CfP (2026-10-02) and Jupyter Day's CfP (2026-09-13) are already past. They are correct as history but are not open CfPs.
   • PyDay Hurlingham uses the earlier date (the 18th) because the site's "20 de Octubre" is a Sunday/Tuesday mismatch. Keeping the 18th is the safe choice.
   • PyDay Hurlingham and PyDay La Plata both close 2026-10-18, four days from today.
6. Time zones. PyDay La Plata, PyDay Hurlingham, PyCon Slovakia and PyCon Russia have no timezone, so they default to AoE (per CONTRIBUTING.md: "defaults to AoE if omitted"). The PR table says AoE for these, which matches.

4. Findings

Important: None.

Nits:

1. Possible inconsistency: PyCon Davao has cfp: None but also a cfp_link (_data/conferences.yml, PyCon Davao entry). The PR says the form needs a sign-in. This is a judgement call; keeping the link is reasonable.
2. Possible naming inconsistency: "Pytorch Day Japan" and "PyTorch Conference" use different capitalisation of PyTorch. The PR explains this is deliberate to avoid the sort merging Pytorch Day entries (see decision 4 area); no action needed beyond awareness.

5. Tests

No test checks the request's invariant (every new entry has a valid date range, a reachable link and a deadline that matches its source). The existing suite does not read the new entries against their sources. Output of what I ran:

• npm ci then npm test (jest): Test Suites: 15 passed, 15 total / Tests: 423 passed, 423 total.
• A YAML load of _data/conferences.yml succeeded with 70 entries and no duplicate (conference, year) pair.
• python3 -m pytest: No module named pytest. I could not run the Python suite (environment gap, see Bounds).
• ruff check: Found 92 errors. [*] 79 fixable with the --fix option. The PR changes no Python files, so these come from existing code.

6. Bounds

• Read in full: the whole diff, CONTRIBUTING.md from the base branch (first 150 lines), and the review contract.
• Did not read: REVIEW.md and AGENTS.md; neither exists on the base branch.
• Could not run: the Python tests (pytest not installed in the sandbox; the PR also says the local pandas pin makes 10 tests fail anyway). I did not re-run utils/sort_yaml.py, so geocoding and schema validation are as reported by the author.
• Could not fetch any conference site (proxy 403), so no source facts were independently confirmed.
• Pre-existing: ruff check reports 92 errors in code this PR does not touch.

---

Generated by Claude Code

[JesperDramsch]

Replies to the routine review:

• PyCon Italy link (decision 1): https://2027.pycon.it/en returned HTTP 200 when I verified it on 2026-10-13 and shows the same 2027 announcement ("PyCon Italia 2027, from June 2 to June 5, 2027, at the Savoia Regency Hotel"). The page still runs on the 2026 build, so the link stays as it is.
• Stacked base (decision 3): done. Repair lost and wrong conference data; stop the new-year job deleting entries #494 is merged, this PR now targets main, and 0dc901a merges main in so the diff is only the 18 new entries in _data/conferences.yml. sort_yaml.py --skip_links makes no changes. I also ran the two REVIEW.md checks: every new entry's year matches the year of its start, and every timezone is a valid IANA name.
• Nits: both stay as they are. PyCon Davao's cfp_link is the official CfP form, which is worth keeping even though the deadline is unknown. "Pytorch Day" keeps the existing series spelling so the sort keeps these entries separate.

---

Generated by Claude Code