Skip to content
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

python3-bibtexparser: update to 1.2.0. #34299

Closed
wants to merge 1 commit into from

Conversation

jgarte
Copy link
Contributor

@jgarte jgarte commented Nov 29, 2021

Testing the changes

  • I tested the changes in this PR: briefly

Local build testing

  • I built this PR locally for my native architecture, (x86_64)

@jgarte
Copy link
Contributor Author

jgarte commented Nov 29, 2021

@ericonr

This built locally on my machine and I was able to import the library in a repl.

Not sure what's going on with ci...

@paper42
Copy link
Member

paper42 commented Nov 29, 2021

let's also add the changelog

changelog="https://raw.githubusercontent.com/sciunto-org/python-bibtexparser/master/CHANGELOG"

cc @xaltsc

@jgarte
Copy link
Contributor Author

jgarte commented Nov 29, 2021

@jgarte
Copy link
Contributor Author

jgarte commented Nov 30, 2021

Hmm, the github UI allows me to add suggestions made by others so they can get there name added to the commit, which is really cool but it doesn't squash those commits together. What do void devs prefer? Are you able to squash the final commit on your end from the web ui?

@jgarte
Copy link
Contributor Author

jgarte commented Nov 30, 2021

subject does not follow CONTRIBUTING.md guildelines

I'm not entirely sure what the above lint warning from github CI means. It happened after I accepted @paper42 suggestion above to add pytest to the template.

Copy link
Contributor Author

@jgarte jgarte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like github web ui duplicated python3-future when I accepted your patch/diff.

@jgarte
Copy link
Contributor Author

jgarte commented Nov 30, 2021

@paper42

I applied your co-authorship manually from my terminal and force pushed. I think all should be good now.

Co-authored-by: paper <michal@vasilek.cz>
@jgarte
Copy link
Contributor Author

jgarte commented Nov 30, 2021

@paper42 @dotnetfox @ericonr

Tests currently fail for this package because PyPi does not include the test repo.

I can add them if I pull the sources in from the project's github repo.

Would you prefer for me to do that?

@paper42

It looks like tests are run with nose instead of pytest:

https://github.com/NixOS/nixpkgs/blob/nixos-unstable/pkgs/development/python-modules/bibtexparser/default.nix#L24

@paper42
Copy link
Member

paper42 commented Nov 30, 2021

@jgarte
Copy link
Contributor Author

jgarte commented Nov 30, 2021

@paper42

Does pytest wrap unittest or nosetests? I haven't looked that far at the code.

Answer to self:

https://docs.pytest.org/en/6.2.x/unittest.html

pytest supports running Python unittest-based tests out of the box. It’s meant for leveraging existing unittest-based test suites to use pytest as a test runner and also allow to incrementally adapt the test suite to take full advantage of pytest’s features.

checksum=0f9ab94e3fc36ee2ee6a3713c5dd7320d4b6ee52bd66ecbab03c6b06675ae410

do_check() {
LC_ALL="en_US.UTF-8" nosetests
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should use nosetests3 directly, but it also requires that python3-nose be in checkdepends.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can run all the tests with pytest if we just remove do_check and add pytest to checkdepends.

@jgarte
Copy link
Contributor Author

jgarte commented Jan 12, 2022

Not sure, when I'll be able to spend time on this one again. If anyone else would like to take it over feel free to.

@github-actions
Copy link

Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.

@github-actions github-actions bot added the Stale label Jun 16, 2022
@github-actions github-actions bot closed this Jul 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants