Update pyproject for maturin 1.8.0

[dylanwhawk]

Fixes #44

[Bennoo]

small up, I am waiting for this. Can this being merged? Thanks a lot

[jason-huh]

@daxpryce @nicaurvi , could you please take a look?
We've got a problem in another repo: microsoft/graphrag#1559

[daxpryce]

hey @darthtrevino can you take a look at this? I remember running into this ages ago and something in maturin made it so I didn't have to set version as a dynamic property, but it's been so long I'm not confident I will be able to ensure this is working the way in time. I figured since you've done some stuff on this more recently than me you might be a better point of contact.

I'll look at it no matter what, I just don't know how soon I'll have it done :)

nevermind all of that, you haven't had to do anything in this repo. I'll try to take a look tomorrow.

Sorry this hasn't been kept up to date with maturin folks, I haven't had any time to work on this in years 😅

[jason-huh]

@daxpryce Thank you so much for your help. Would it be possible to get an estimated timeline for when this might be resolved? If it takes longer than anticipated, we may need to explore a workaround.

Just to clarify, we understand that you owe us nothing, and we truly appreciate your prompt response and kindness.

[jason-huh]

Also, I'd be happy to contribute, if you could offer the necessary guidance.

[daxpryce]

This is likely such an easy fix - indeed we have a great example of how it could work submitted by @dylanwhawk - I just need to read through exactly what is going on, why it is happening, and what the proper way to fix it is (like, it very likely could be their exact method, but I want to make sure I'm not raising any weird issues where if version is dynamic [something] malicious could be slipstreamed into it or something. it's exceedingly unlikely, but I still don't want to be hasty :) )

timeline: I would expect tomorrow or Wednesday (pacific timezone). If it's taking longer I'll be sure to let everyone know :)

[daxpryce]

Just to clarify, we understand that you owe us nothing, and we truly appreciate your prompt response and kindness.

No worries, I'm just glad someone is finding some use for it! If I had my way I'd revisit the whole thing again, knowing what I know now about... so many things 😄

[daxpryce]

Thank you so much for this @dylanwhawk !

[dylanwhawk]

Thank you so much for this @dylanwhawk !

Of course! Happy that this got resolved for everyone waiting for it.

[Bennoo]

Many thanks to all of you!!

[daxpryce]

Because it pained me to leave us so many versions behind on so many things in this, I took the day and ... kinda got target fixation and tried to do way too much stuff at once. But anyway, there's a PR out now as a prep for 1.2.2 - #46 . If any of you fine folks wouldn't mind doing a PR of all my changes - in specific noting that we are dropping support for python 3.6 an 3.7 (now that they're not available in the most up-to-date pyo3) . I would not mind community feedback on this well before I make the change, especially since it's somehow still a patch release.

[daxpryce]

I didn't merge the dang thing after I approved it. I am an absolute genius.

[daxpryce]

https://pypi.org/project/graspologic-native/1.2.2.dev2025010812680358310/ was released as a prerelease today. @darthtrevino, if you could test this with graphrag to make sure it works for everyone here that would be great. Once I know I'm not breaking things for everyone I'll create the final 1.2.2 release.

The unit testing scenario around this project is absolutely dire