#premature need to update libraries to reflect `latest` docs
edgy raptor
starting a thread
we could consider backporting the displayio refactor to 8.x.x, but that probably isn't worth it
upper quest
it might be possible to use the mock module list in order to get the docs to build without making the change in code yet so that we could still defer it if we wanted to go that route.
edgy raptor
also note that the doc problem only provoked fourwire changes, but there are other non-fourwire display libraries whose examples will need to be updated later, e.g. https://github.com/adafruit/Adafruit_CircuitPython_displayio_sh1107 which uses I2CDisplay; its use of displayio.I2CDisplay will need to change, but not until 10
real nacelle
I did consider not warning until we release 9.0.0 stable
I thought the docs would build ok because I do have import lines in the stubs that should use the old names
native night
I don't understand the build/doc issues but could a try/except block be used on the imports and bus creation calls during the transition
edgy raptor
I *thought* the docs would build ok because I do have import lines in the stubs ...
I thought this was be due to intersphinx not finding references to, say, displayio.fourwire. But I see you added these to displayio
//| from busdisplay import BusDisplay as Display
//| from epaperdisplay import EPaperDisplay
//| from fourwire import FourWire
//| from i2cdisplaybus import I2CDisplayBus as I2CDisplay
that doesn't mean it works with intersphinx though. I'm not sure why it is having an issue
native night
I submitted this https://github.com/adafruit/Adafruit_CircuitPython_DisplayIO_SSD1305/pull/18 wondering if it would be a workable approach for the displayio changes during the transtion to the new displayio structure.
