An alternative that would work is if I can query the diff publicly. Taking a look at the internal code, it uses private variables, so there's no easy way to get the diff in a "safe" way.

Obviously this is not something I would do intentionally, but in a large script is it very possible for one section of code to add a property and another section of code to remove that property, and then the diff becomes empty.

In T355981#9492165, @Xqt wrote:

@RPI2026F1 Cannot follow this task, could you please explain a bit more. What is meant with diff is empty? What would be the reason not to make a request call if we have a site? I guess you mean the editEntity() call without any parameters?

I was using DataSite to enhance type information, since pywikibot.Site() only returns methods shared by all types of sites, and I needed some Wikidata-specific methods.

I mean it partially isn’t a bug as the precision is set to millennium. If you want a more specific date value then the precision should be updated to be more precise. 2000 and 1500 are in the same millennium, the 2nd millennium.

There are alternative ways to only import ForwardRef types for type checkers. A common usage I've seen is:

Ahh my bad, I didn't notice this difference.

Seems to be working as of the latest version.

In T330716#8669002, @Xqt wrote:

I've no glue how this can be done. DataSite is a subclass from BaseSite but how can an overload be done for all site objects which are no DataSite objects? If the site parameter is None the Site type is determined during runtime and can be either DataSite, APISite, DrySite, DryDataSite or any other defined e.g. by Family.interface() method.

Sorry I misread the notification, my bad. The Needs Triage color is too similar to the “Resolved” color

Why was this task closed? I still cannot visit the original link without the error.

I suspect it might have to do with the data file being 11 MB in size

A logout seems to have fixed the issue. I'm not sure why this happens though.

This is severely slowing down any Pywikibot bots from fetching information.

I have observed this happening for a few weeks, did not know it was a bug.

Maybe a solution can be to display a REPR of <Incomplete Claim P31 site=pywikibot.Site(...)> or something along those lines.

@Xqt alright, sorry I missed that somehow

I think the only way to deal with this is to do from imports only, ie no accessing modules from the parent pywikibot module.

Are you trying to load this through nodeJS? You need to compile it down to JS and load it through mw.loader.load(url) on a website of a Wikipedia.

It actually seems that something closer to the API layer took over type validation and I don't think it's possible to get to this internal position anymore, so my patch is most likely invalid.

This patch was intending to clarify an API error, which is what I was running into. That type mismatch is more of a fundamental error, where I was supplying a "wikibase-entityid" value to a property expecting a "string" and so on.

Hmm this issue seems to be gone, but I'm not sure why. I should have captured a web archive.

Seems to be tracked in https://github.com/magnusmanske/quickstatements/issues/38

So my mistake was putting in an object when an array was expected. I'm not sure why that didn't return a validation error.

Can you please provide references for this statement? Thanks!

I guess that makes sense. My intro to Python programming was the discord.py library, which runs exclusively on asyncio, and so I had thought that async made the library use coroutines.