@@ -12,19 +12,47 @@ Should you require help, there are a :ref:`variety of options available
12
12
usage then please check the rest of this guide first as it should answer your
13
13
question.
14
14
15
+ Discourse
16
+ ---------
17
+
18
+ Python has a hosted `Discourse `_ instance. Be sure to visit the related Core
19
+ categories, such as
20
+ `Core Development <https://discuss.python.org/c/core-dev/23 >`_ and
21
+ `Core Workflow <https://discuss.python.org/c/core-workflow/8 >`_.
22
+
23
+ .. _Discourse : https://discuss.python.org/
24
+
25
+ Mailing Lists
26
+ -------------
27
+
28
+ Further options for seeking assistance include the `python-ideas `_ and
29
+ `python-dev `_ mailing lists. Python-ideas contains discussion of speculative
30
+ Python language ideas for possible inclusion into the language. If an idea
31
+ gains traction it can then be discussed and honed to the point of becoming a
32
+ solid proposal and presented on python-dev. Python-dev contains discussion
33
+ of current Python design issues, release mechanics, and maintenance of
34
+ existing releases. These mailing lists are for questions involving the
35
+ development *of * Python, **not ** for development *with * Python.
36
+
37
+ .. _python-ideas : https://mail.python.org/mailman/listinfo/python-ideas
38
+ .. _python-dev : https://mail.python.org/mailman/listinfo/python-dev
15
39
16
40
Ask #python-dev
17
41
---------------
18
42
19
43
If you are comfortable with IRC you can try asking on ``#python-dev `` (on
20
44
the `freenode `_ network). Typically there are a number of experienced
21
45
developers, ranging from triagers to core developers, who can answer
22
- questions about developing for Python. Just remember that `` #python-dev ``
23
- is for questions involving the development *of * Python whereas `` #python ``
24
- is for questions concerning development *with * Python.
46
+ questions about developing for Python. As with the mailing lists,
47
+ `` #python-dev `` is for questions involving the development *of * Python
48
+ whereas `` #python `` is for questions concerning development *with * Python.
25
49
26
- .. _freenode : https://freenode.net/
50
+ .. note ::
51
+
52
+ You may not be able to access the history of this channel, so it cannot
53
+ be used as a "knowledge base" of sorts.
27
54
55
+ .. _freenode : https://freenode.net/
28
56
29
57
Zulip
30
58
-----
@@ -34,6 +62,11 @@ for asking help with core development, as well as core developers' office
34
62
hour stream. It is preferred that you ask questions here first or schedule
35
63
an office hour, before posting to python-dev mailing list or filing bugs.
36
64
65
+ .. warning ::
66
+
67
+ This is no longer actively monitored by core devs. Consider asking your questions
68
+ on Discourse or on the `python-dev `_ mailing list.
69
+
37
70
.. _Zulip : https://python.zulipchat.com
38
71
39
72
@@ -78,23 +111,6 @@ during office hours.
78
111
.. _Mariatta's twitter : https://twitter.com/mariatta
79
112
80
113
81
- Mailing Lists
82
- -------------
83
-
84
- Further options for seeking assistance include the `python-ideas `_ and
85
- `python-dev `_ mailing lists. Python-ideas contains discussion of speculative
86
- Python language ideas for possible inclusion into the language. If an idea
87
- gains traction it can then be discussed and honed to the point of becoming a
88
- solid proposal and presented on python-dev. Python-dev contains discussion
89
- of current Python design issues, release mechanics, and maintenance of
90
- existing releases. As with ``#python-dev ``, these mailing lists are for
91
- questions involving the development *of * Python, **not ** for development
92
- *with * Python.
93
-
94
- .. _python-ideas : https://mail.python.org/mailman/listinfo/python-ideas
95
- .. _python-dev : https://mail.python.org/mailman/listinfo/python-dev
96
-
97
-
98
114
File a Bug
99
115
----------
100
116
0 commit comments