🚚 Upgrade to lamindb 1.0

[falexwolf]

No description provided.

[github-actions]

🚀 Deployed on https://677fd5a5d0acd699d0850090--lamindb-setup-htry.netlify.app

[Koncopd]

django 5 is not compatible with python 3.9

[falexwolf]

Yes, I studied this for the past 15 min 😅

Scientific Python is already beyond 3.10

EOL of Python 3.9 is in a few months

Hence my sense is that >3.10 should be OK, don't you think?

Reason is using Django's db_default without which we have problems in the hub backend.

[Koncopd]

But what are the problems? This sounds very suspicious to me.

[Koncopd]

I would prefer not to drop before EOL. This can definitely frustrate some users, we need to check first.

[falexwolf]

This can definitely frustrate some users, we need to check first.

I know that a few users might not be happy about it. But I fear that without it, there is no lamindb 1.0 (I mean it'd be super hacky and ugly not to us db_default).

And without lamindb 1.0 we're practically dead-locked.

So, I'd accept that small nuisance given that we'll then be in a position of operating disruption free.

Do you see any other solution?

[Koncopd]

Why is db_default needed?

[falexwolf]

Here is an important approval:

• https://github.com/laminlabs/pfizer-lamin-usage/issues/107#issuecomment-2578344798

Why is db_default needed?

To declare defaults on the database level in a meaningful way. Several new fields error otherwise on the hub. And it should be declared on the database level anyway. So if we don't do it now, we have to do it in a year or so with the next migration.