Marc Garcia

> @datapythonista can you clarify the statement "not the ones I'm currently a member"? Do you still want to be on the core library team? If you're not on any...

I can confirm this happens to me, only for 3.9 and pandas installed via pip (installed via conda-forge has the right version)

I'm personally happy to add this, but it's kind of a big change in terms of the code users can write. @pandas-dev/pandas-core, thoughts here? If this moves forward, you'll want...

> Hard to understand without documentation that illustrates a use case. We allow creating pandas accessors with `register_dataframe_accessor`. For cyberpandas for example, when you do `import cyberpandas` they'd call that,...

> What if there were conflicts in naming? I think by default, the last package found for the entry point with that name will overwrite the previous. As Tom says,...

I don't think we should raise an exception. Imagine a case where someone workimg with dna has two packages installed that provide a dna accessor. The user doesn't even care...

We already use entrypoints in pandas for the plotting backends. Besides what Tom said, if I'm not wrong many projects using commands (e.g. `jupyter `, `black `, `flake8 `) are...

Tom commented about 2. The entry points are a registry. I think the cost is just a lookup of the entry point name in a hash table. It shouldn't depend...

> FWIW I recall the team being negative in the past about supporting reading directories of files Do you remember the reason? This seems like a useful thing, as I...

Note that you've got the image from Will's book in this PR, this happened when we had to hard revert it from git history.