-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is this project still maintained? #23
Comments
I do not have the answer to your question, but I do have an active fork in which I have merged almost all contributions of other forks that I could find on Github. If you find pypi to be outdated, you could always just clone a repository to your computer and then make a symbolic link of that repository in your python site-packages folder. |
Hi! I'm not using it myself. Someone at my institute (MAX IV) wanted to use it. So yes, right now they just cloned the repo locally and installed from there but it's not great for reproducibility. If the original author doesn't answer, and if you are interested you could open an issue on pypi: https://peps.python.org/pep-0541/#how-to-request-a-name-transfer |
I was looking for the functionality of reading files created by the process control. That was not supported by the repo here, but by your one, so thanks a lot @luukvandervelden! It would be correct to say that this repository is not active, while your one is clearly more advanced (for everyone having the same problems as I had). |
Thanks @beenje, I will take a look at your suggestion |
Has somebody yet contacted qed.ai by mail (Wiliam Wu is the co-founder)? |
I will contact them this afternoon @philipp-baumann, will let you know |
@luukvandervelden do you have any updates from qed.ai ? |
Nothing yet, I’ve just forwarded the mail to William. Hopefully he’ll respond 🙏🏻
… Op 19 mrt. 2023 om 12:00 heeft Philipp Baumann ***@***.***> het volgende geschreven:
@luukvandervelden do you have any updates from qed.ai ?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
|
thanks. I'm sure they will. |
Willam @willywutang, @tdyczek Tomasz? |
Hi, we're looking at options internally and will let you know soon. Sorry for the wait! |
As the first step we're tweaking licensing, see #25 In the meantime, @fernandezc – would @spectrochempy be interested in taking over maintenance, including the pypi package? We're potentially open to that, as long as our credit is preserved (AFAIK the license enforces that either way). |
Hi, @spectrochempy is not a big organization (only two maintainers at the moment) |
Hi all, So, now, which fork should I be using ? Thank you. |
Hi, |
I have recently published a python package that can both read binary OPUS files and communicate/control OPUS software. I believe it uses a more sophisticated algorithm for extracting data from OPUS files and should read most, if not all, files. Take a look here: |
Hello,
I'd like to know the status of the project. Last version on pypi is 1.3.4 (from 2019).
There is a fork https://github.com/spectrochempy/brukeropusreader with several tags. There is a 1.3.9 version available.
Are you willing to take the changes from this fork?
Or would you consider transferring the pypi project to @spectrochempy? I have no link with this organisation, so I actually don't know if they are interested.
As a user it would be nice to have a maintained version on pypi.
The text was updated successfully, but these errors were encountered: