Luca

+1

@Warfront1 did you solve your issue? Would you mind pointing out the logical problems and your solution to them? Thanks

Same error on Windows 10, the script imports numpy and pandas. I updated the conda enviroment with latest pandas, numpy and scalene

When reading back into pandas DataFrame, for instance, the int64 columns has missing data with -9223372036854775808 instead of np.nan, resulting in a NON reproducible mapping.

In the debugger I saw that: ``` async def _rm(self, path, recursive=False, **kwargs): if recursive and isinstance(path, str): bucket, key, _ = self.split_path(path) if not key and await self._is_bucket_versioned(bucket): #...

If I try a direct call to the empy dir: ``` await self.fs._rmdir( path=f"{self.bucket_name}/{remote_path}", ) ``` There is the exception "FileExistsError". The path is empty though.

> It is > > ``` > await self.fs._rm_file( > path=f"{self.bucket_name}/{remote_path}/", > ) > ``` > > (with the "/" suffix) that you want. This is a **FILE**, which is...

Trying more I faced another problem that was: the cursor used on the write_dataframe function seems to overwrite the cursor params style and uses internally only position based formatting like...

Pinning `pandas < 2.0`, `numpy < 2.0` let me run the query. Are the updated docs where it is stated the supported versions of the libraries integrations?

> Thanks for the follow up. Does it mean the sentence: > > > By default BoundingBox is set to work with **denormalized** co-ordinates: x: (0, **docwidth**), y: (0, **docheight**)....