python 3.9-dev getting an error

[wumpus]

  reppy/robots.cpp: In function ‘int __Pyx_modinit_type_init_code()’:
  reppy/robots.cpp:7788:35: error: ‘PyTypeObject’ has no member named ‘tp_print’
     __pyx_type_5reppy_6robots_Agent.tp_print = 0;
                                     ^
  reppy/robots.cpp:7796:36: error: ‘PyTypeObject’ has no member named ‘tp_print’
     __pyx_type_5reppy_6robots_Robots.tp_print = 0;
                                      ^
  reppy/robots.cpp:7805:39: error: ‘PyTypeObject’ has no member named ‘tp_print’
     __pyx_type_5reppy_6robots_AllowNone.tp_print = 0;
                                         ^
  reppy/robots.cpp:7814:38: error: ‘PyTypeObject’ has no member named ‘tp_print’
     __pyx_type_5reppy_6robots_AllowAll.tp_print = 0;
                                        ^
  reppy/robots.cpp:7822:61: error: ‘PyTypeObject’ has no member named ‘tp_print’
     __pyx_type_5reppy_6robots___pyx_scope_struct__FetchMethod.tp_print = 0;
                                                               ^
  reppy/robots.cpp:7828:60: error: ‘PyTypeObject’ has no member named ‘tp_print’
     __pyx_scope_struct____Pyx_CFunc_object____object___to_py.tp_print = 0;
                                                              ^
  error: command 'gcc' failed with exit status 1
  ----------------------------------------
  ERROR: Failed building wheel for reppy

The precise version I saw this in is Python 3.9.0a2+

[wumpus]

In this example fix from another project, they limited using tp_print to python 2.

https://gitlab.gnome.org/GNOME/pygobject/merge_requests/119/diffs

My guess is that rebuilding reppy/robots.cpp in a newer Cython will fix the problem.

[wumpus]

Travis-CI made python3.9-dev available on their popular free continuous integration infrastructure, so you're going to see more and more reports of this bug.

[nishwalshetty]

i have the same issue, how do i fix this ?

[pensnarik]

Have the same issue while building reppy in Docker. The problem exists if I use latest Python image. If I specify FROM python:3.8 it builds successfully. So I guess the problem is with Python versions > 3.8. Docker file to reproduce the issue:

FROM python:3

RUN pip install reppy

The error I was getting is:

  reppy/robots.cpp:7788:35: error: ‘PyTypeObject’ {aka ‘struct _typeobject’} has no member named ‘tp_print’; did you mean ‘tp_dict’?
     __pyx_type_5reppy_6robots_Agent.tp_print = 0;
                                     ^~~~~~~~

[conraid]

Also in Slackware current with python-3.9

reppy/robots.cpp: In function 'int __Pyx_modinit_type_init_code()':
reppy/robots.cpp:7788:35: error: 'PyTypeObject' {aka 'struct _typeobject'} has no member named 'tp_print'
 7788 |   __pyx_type_5reppy_6robots_Agent.tp_print = 0;
      |                                   ^~~~~~~~
reppy/robots.cpp:7796:36: error: 'PyTypeObject' {aka 'struct _typeobject'} has no member named 'tp_print'
 7796 |   __pyx_type_5reppy_6robots_Robots.tp_print = 0;
      |                                    ^~~~~~~~
reppy/robots.cpp:7805:39: error: 'PyTypeObject' {aka 'struct _typeobject'} has no member named 'tp_print'
 7805 |   __pyx_type_5reppy_6robots_AllowNone.tp_print = 0;
      |                                       ^~~~~~~~
reppy/robots.cpp:7814:38: error: 'PyTypeObject' {aka 'struct _typeobject'} has no member named 'tp_print'
 7814 |   __pyx_type_5reppy_6robots_AllowAll.tp_print = 0;
      |                                      ^~~~~~~~
reppy/robots.cpp:7822:61: error: 'PyTypeObject' {aka 'struct _typeobject'} has no member named 'tp_print'
 7822 |   __pyx_type_5reppy_6robots___pyx_scope_struct__FetchMethod.tp_print = 0;
      |                                                             ^~~~~~~~
reppy/robots.cpp:7828:60: error: 'PyTypeObject' {aka 'struct _typeobject'} has no member named 'tp_print'
 7828 |   __pyx_scope_struct____Pyx_CFunc_object____object___to_py.tp_print = 0;

[virtadpt]

I'm getting it over here - Arch Linux updated as of 20200606, Python v3.9.2. Context: It's a dependency of Deadlinks.

[butuzov]

@virtadpt, yeah... looks like it needs to be replaced. go to deadlinks repo and open the issue. I stumble on it by accident.