profile
viewpoint

dulwich/dulwich 1522

Pure-Python Git implementation

jelmer/ansible-role-borgbackup 1

Borg backup role

jelmer/build-farm 1

The Samba Build-Farm

jelmer/bumpversion 1

Version-bump your software with a single command

jelmer/2048-qt_debian 0

mathematics based puzzle game

jelmer/3270font 0

A 3270 font in a modern format

jelmer/acpi-call 0

Temporary home for the acpi-call Debian package (upstream: https://github.com/mkottman/acpi_call)

jelmer/adv-17v35x 0

Advantech ACOM Series (EXAR chip) Linux Driver - Debian packaging

jelmer/aiohttp-wsgi 0

WSGI adapter for aiohttp.

created repositoryanthonywritescode/aoc2020

https://adventofcode.com/2020

created time in 9 hours

issue commentisomer/erbium

Request: Publish as crate

I thought I had? https://crates.io/crates/erbium

Is there something else I should be doing?

stappersg

comment created time in 9 hours

startedhanatos/vkdt

started time in 15 hours

issue openedisomer/erbium

Request: Publish as crate

More a wish than request

Publish erbium at https://crates.io

created time in 16 hours

issue commenttesting-cabal/mock

mock throws ValueError when spec_arg is an ndarray

Please can you try and reproduce the problem on the latest release of Python 3, including alphas, and replace any import from mock with ones from unittest.mock.

Cheers @cjw296 - we did just that, hence my posts above, mate! I will report upstream, cheers for your assistance - note however that the issue tracker for the package points here https://pypi.org/project/mock/ so you guys might want to add a descriptor note there saying that any issue should probably be first tested with unittest.mock and reported upstream - I find it a bit confusing if issues reported here get closed and bug reports need to be communicated upstream. Cheers, V :beers:

valeriupredoi

comment created time in 18 hours

startedfangfufu/Linux-Fake-Background-Webcam

started time in 19 hours

startedelastic/ansible-elasticsearch

started time in 20 hours

startedbruno-garcia/oxideoverflow

started time in a day

created repositoryaquatix/floatplane-fullwidth

Make the videoplayer of floatplane.com the full width of its container so it's not restricted to 1246px

created time in a day

startednejento/floatplane-dark

started time in a day

issue closedtesting-cabal/mock

mock throws ValueError when spec_arg is an ndarray

What versions are you using?

  • Python: 3.9
  • Mock: 3.3.1; installed from PyPi
  • Operating System: Linux
  • import: from unittest import mock

What happened?

Hey guys, not sure this is the right place to report this (I tried upstream in GitHub/unittest but they turned off their Issues). The latest version of mock.py has these at lines 411-412:

            if spec_arg and _is_async_obj(spec_arg):
                bases = (AsyncMockMixin, cls)

which throws an exception if spec_arg is an ndarray:

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
esmvalcore/preprocessor/_regrid_esmpy.py:88: in get_grid
    grid = ESMF.Grid(np.array(esmpy_lat.shape),
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

cls = <class 'tests.unit.preprocessor._regrid_esmpy.test_regrid_esmpy.MockGrid'>, args = (array([4, 4]),)
kw = {'num_peri_dims': 0, 'staggerloc': [sentinel.sl_center]}
bases = (<class 'tests.unit.preprocessor._regrid_esmpy.test_regrid_esmpy.MockGrid'>,)
bound_args = {'kwargs': {'num_peri_dims': 0, 'staggerloc': [sentinel.sl_center]}, 'self': <class 'tests.unit.preprocessor._regrid_esmpy.test_regrid_esmpy.MockGrid'>, 'spec': array([4, 4])}
spec_arg = array([4, 4])

    def __new__(cls, /, *args, **kw):
        # every instance has its own class
        # so we can create magic methods on the
        # class without stomping on other mocks
        bases = (cls,)
        if not issubclass(cls, AsyncMockMixin):
            # Check if spec is an async object or function
            bound_args = _MOCK_SIG.bind_partial(cls, *args, **kw).arguments
            spec_arg = bound_args.get('spec_set', bound_args.get('spec'))
>           if spec_arg and _is_async_obj(spec_arg):
E           ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()

in a previous older version, spec_arg was constructed as a list so things were going well. Is this a bug or an intended feature? Cheers muchly for your help :beer:

closed time in 2 days

valeriupredoi

issue commenttesting-cabal/mock

mock throws ValueError when spec_arg is an ndarray

This package is a rolling backport of unittest.mock. As such, any problems you encounter most likely need to be fixed upstream.

Please can you try and reproduce the problem on the latest release of Python 3, including alphas, and replace any import from mock with ones from unittest.mock.

If the issue still occurs, then please report upstream through https://bugs.python.org/ as it will need to be fixed there so that it can be backported here and released to you.

If not, reply with what you find out and we can re-open this issue.

valeriupredoi

comment created time in 2 days

startedloadimpact/k6

started time in 2 days

push eventbreezy-team/breezy

Jelmer Vernooij

commit sha c0d6a0272d4da9f5c4720a7bab5456c741327858

Drop test for exception that isn't raised on Python 3.9.

view details

Jelmer Vernooij

commit sha d1ef23eedcafbd140e87acd2e2901274b14c9dff

urlutils: Drop test for exception that isn't raised on Python 3.9. Merged from https://code.launchpad.net/~jelmer/brz/python3.9-test/+merge/394296

view details

push time in 2 days

pull request commentdulwich/dulwich

Update ignore, requirements.txt, workflows and lint python

We seem to be going in circles; I'm keen to merge changes that fix actual problems. A lot of these are just adding more cruft to the source for the sake of making changes.

Yes, I also feel that I am dealing with the same thing.

My direction is to write CI well or decide the architecture first, and my research direction is also this part, including automation, inspection, dependency, or specification. The current added content is based on the content of each developer.

So if it causes you trouble, I can do something else. I am also capable of development.

This is the case today, I will go to bed first.

timmy61109

comment created time in 2 days

Pull request review commentdulwich/dulwich

Update ignore, requirements.txt, workflows and lint python

+# Byte-compiled / optimized / DLL files

So what needs to be deleted?

timmy61109

comment created time in 2 days

Pull request review commentdulwich/dulwich

Update ignore, requirements.txt, workflows and lint python

 [flake8]-exclude = build,.git,build-pypy,.tox+exclude =+    .git,+    __pycache__,+    docs/source/conf.py,+    docs/conf.py,

我有更新。

timmy61109

comment created time in 2 days

Pull request review commentdulwich/dulwich

Update ignore, requirements.txt, workflows and lint python

 [flake8]-exclude = build,.git,build-pypy,.tox+exclude =+    .git,+    __pycache__,+    docs/source/conf.py,+    docs/conf.py,+    old,+    build,+    dist,

Because other developers who will use the virtual environment will use it, and if it is not ignored by the project, it will be checked.

And this is the way these packages are used, so these directories or files will be generated, just like __pycache__.

Although there will be no impact on GitHub Actions, developers can also set this function globally like Git, but it is relatively inconvenient to ~/.gitignores_global.

It is recommended to set it in the project, because the difference of each project is more complicated than that of .gitignore. You cannot set the common list as simple as .gitignore, and restricting the rules to projects is to generate the rules The interference is reduced and independent, so Git repositories and projects have .gitignore rules or flake8 exclude rules.

timmy61109

comment created time in 3 days

Pull request review commentdulwich/dulwich

Update ignore, requirements.txt, workflows and lint python

 [flake8]-exclude = build,.git,build-pypy,.tox+exclude =+    .git,+    __pycache__,+    docs/source/conf.py,+    docs/conf.py,+    old,

No problem, I am also studying, thank you for your feedback.

timmy61109

comment created time in 3 days

Pull request review commentdulwich/dulwich

Update ignore, requirements.txt, workflows and lint python

 [flake8]-exclude = build,.git,build-pypy,.tox+exclude =+    .git,+    __pycache__,+    docs/source/conf.py,+    docs/conf.py,

In addition, I refer to here, so if I have an error or describe the problem, you can give me feedback.

https://flake8.pycqa.org/en/latest/user/configuration.html#project-configuration

timmy61109

comment created time in 3 days

Pull request review commentdulwich/dulwich

Update ignore, requirements.txt, workflows and lint python

 [flake8]-exclude = build,.git,build-pypy,.tox+exclude =+    .git,+    __pycache__,+    docs/source/conf.py,+    docs/conf.py,

Yes, sorry, I remembered it wrong, it was Pylint.

timmy@timmy-Latitude-E5550:~/Git/dulwich$ python3 -m flake8 docs/conf.py 
timmy@timmy-Latitude-E5550:~/Git/dulwich$ python3 -m pylint docs/conf.py 
************* Module conf
docs/conf.py:52:0: W0622: Redefining built-in 'copyright' (redefined-builtin)
docs/conf.py:1:0: C0114: Missing module docstring (missing-module-docstring)
docs/conf.py:36:0: C0103: Constant name "autoclass_content" doesn't conform to UPPER_CASE naming style (invalid-name)
docs/conf.py:42:0: C0103: Constant name "source_suffix" doesn't conform to UPPER_CASE naming style (invalid-name)
docs/conf.py:48:0: C0103: Constant name "master_doc" doesn't conform to UPPER_CASE naming style (invalid-name)
docs/conf.py:51:0: C0103: Constant name "project" doesn't conform to UPPER_CASE naming style (invalid-name)
docs/conf.py:52:0: C0103: Constant name "copyright" doesn't conform to UPPER_CASE naming style (invalid-name)
docs/conf.py:59:0: C0103: Constant name "version" doesn't conform to UPPER_CASE naming style (invalid-name)
docs/conf.py:61:0: C0103: Constant name "release" doesn't conform to UPPER_CASE naming style (invalid-name)
docs/conf.py:96:0: C0103: Constant name "pygments_style" doesn't conform to UPPER_CASE naming style (invalid-name)
docs/conf.py:107:0: C0103: Constant name "html_theme" doesn't conform to UPPER_CASE naming style (invalid-name)
docs/conf.py:174:0: C0103: Constant name "htmlhelp_basename" doesn't conform to UPPER_CASE naming style (invalid-name)

-----------------------------------
Your code has been rated at 4.29/10

timmy@timmy-Latitude-E5550:~/Git/dulwich$ python3 -m flake8 docs/conf.py 
timmy@timmy-Latitude-E5550:~/Git/dulwich$ python3 -m pylint docs/conf.py 
************* Module conf
docs/conf.py:52:0: W0622: Redefining built-in 'copyright' (redefined-builtin)
docs/conf.py:1:0: C0114: Missing module docstring (missing-module-docstring)
docs/conf.py:36:0: C0103: Constant name "autoclass_content" doesn't conform to UPPER_CASE naming style (invalid-name)
docs/conf.py:42:0: C0103: Constant name "source_suffix" doesn't conform to UPPER_CASE naming style (invalid-name)
docs/conf.py:48:0: C0103: Constant name "master_doc" doesn't conform to UPPER_CASE naming style (invalid-name)
docs/conf.py:51:0: C0103: Constant name "project" doesn't conform to UPPER_CASE naming style (invalid-name)
docs/conf.py:52:0: C0103: Constant name "copyright" doesn't conform to UPPER_CASE naming style (invalid-name)
docs/conf.py:59:0: C0103: Constant name "version" doesn't conform to UPPER_CASE naming style (invalid-name)
docs/conf.py:61:0: C0103: Constant name "release" doesn't conform to UPPER_CASE naming style (invalid-name)
docs/conf.py:96:0: C0103: Constant name "pygments_style" doesn't conform to UPPER_CASE naming style (invalid-name)
docs/conf.py:107:0: C0103: Constant name "html_theme" doesn't conform to UPPER_CASE naming style (invalid-name)
docs/conf.py:174:0: C0103: Constant name "htmlhelp_basename" doesn't conform to UPPER_CASE naming style (invalid-name)

------------------------------------------------------------------
Your code has been rated at 4.29/10 (previous run: 4.29/10, +0.00)

timmy@timmy-Latitude-E5550:~/Git/dulwich$ 
timmy61109

comment created time in 3 days

Pull request review commentdulwich/dulwich

Update ignore, requirements.txt, workflows and lint python

 jobs:     - name: Upload coverage details       run: |         codecov+    - name: Style checks pylint+      run: |+        python -m pylint dulwich examples+    - name: Test unittest

Sorry I didn't see it, thank you for your reminder.

timmy61109

comment created time in 3 days

push eventbreezy-team/breezy

Jelmer Vernooij

commit sha 69f11e4c7e2cf0022541deb631edb387c2cd7b3a

Add RepositoryFormat.supports_multiple_authors.

view details

Jelmer Vernooij

commit sha fd2700c2783509efb130e722f702f2b160eefce2

Add RepositoryFormat.supports_multiple_authors. Merged from https://code.launchpad.net/~jelmer/brz/supports-multiple-authors/+merge/394354

view details

push time in 3 days

issue commentasottile/all-repos

How would I use this to clone/update/pull all starred repos?

Added to my todos :smile:

cocoonkid

comment created time in 3 days

pull request commentdulwich/dulwich

Update ignore, requirements.txt, workflows and lint python

Codecov Report

Merging #811 (ecaa289) into master (8e489f0) will decrease coverage by 0.69%. The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #811      +/-   ##
==========================================
- Coverage   85.27%   84.58%   -0.70%     
==========================================
  Files          86       86              
  Lines       21542    21566      +24     
  Branches     2297     2298       +1     
==========================================
- Hits        18370    18241     -129     
- Misses       2777     2890     +113     
- Partials      395      435      +40     
Impacted Files Coverage Δ
dulwich/tests/test_file.py 88.07% <0.00%> (-7.95%) :arrow_down:
dulwich/tests/test_hooks.py 94.04% <0.00%> (-5.96%) :arrow_down:
dulwich/tests/compat/utils.py 83.06% <0.00%> (-5.65%) :arrow_down:
dulwich/tests/__init__.py 79.48% <0.00%> (-3.85%) :arrow_down:
dulwich/index.py 77.57% <0.00%> (-2.91%) :arrow_down:
dulwich/tests/compat/test_client.py 88.80% <0.00%> (-2.62%) :arrow_down:
dulwich/tests/test_index.py 95.56% <0.00%> (-2.58%) :arrow_down:
dulwich/client.py 75.96% <0.00%> (-2.46%) :arrow_down:
dulwich/file.py 86.02% <0.00%> (-2.16%) :arrow_down:
dulwich/repo.py 90.38% <0.00%> (-1.73%) :arrow_down:
... and 15 more

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 8e489f0...ecaa289. Read the comment docs.

timmy61109

comment created time in 3 days

Pull request review commentdulwich/dulwich

Update ignore, requirements.txt, workflows and lint python

 jobs:       uses: actions/setup-python@v2       with:         python-version: ${{ matrix.python-version }}-    - name: Install dependencies+    - name: Install dependencies coverage, codecov, flake8, fastimport, mypy

Yes, there is nothing wrong, it is currently the case. Although I am not sure if I understand your thoughts.

timmy61109

comment created time in 3 days

Pull request review commentdulwich/dulwich

Update ignore, requirements.txt, workflows and lint python

+# Byte-compiled / optimized / DLL files+__pycache__/+*.py[cod]+*$py.class++# C extensions+*.so++# I don't konw. _trial_temp-build-build-pypy-MANIFEST-dist apidocs *,cover .testrepository-*.pyc-*.pyd-*.pyo-*.so *~-*.swp-*.swh-*.swn-*.swo+*.sw[phno] docs/tutorial/index.html dulwich.egg-info/+docs/api/*.txt+dulwich.dist-info++# Unit test / coverage reports+htmlcov/ .tox/+.coverage+.coverage.*+.cache+nosetests.xml+coverage.xml+*.cover+.hypothesis/+.pytest_cache/ .idea/ .coverage-htmlcov/-docs/api/*.txt++# Distribution / packaging+.Python+build+build/+develop-eggs/+dist+dist/+downloads/+eggs/+.eggs/+lib/+lib64/+parts/+sdist/+var/+wheels/+*.egg-info/+.installed.cfg+*.egg+MANIFEST++# PyInstaller+#  Usually these files are written by a python script from a template+#  before PyInstaller builds the exe, so as to inject date/other infos into it.+*.manifest+*.spec++# Installer logs+pip-log.txt+pip-delete-this-directory.txt++# Translations+*.mo+*.pot++# Scrapy stuff:+.scrapy++# Sphinx documentation+docs/_build/++# PyBuilder+target/++# Jupyter Notebook+.ipynb_checkpoints++# pyenv+.python-version++# celery beat schedule file+celerybeat-schedule++# SageMath parsed files+*.sage.py++# Environments+.env+.venv+env/+venv/+ENV/+env.bak/+venv.bak/++# Spyder project settings+.spyderproject+.spyproject++# Rope project settings+.ropeproject++# mkdocs documentation+/site++# mypy .mypy_cache/-.eggs-dulwich.dist-info+build-pypy

I will not delete the Jupyter-related ignore list here, because I think this is very useful.

In addition, this ignore list should actually be ignored, so according to the relevance of the programming language, a long ignore list is normal.

timmy61109

comment created time in 3 days

Pull request review commentdulwich/dulwich

Update ignore, requirements.txt, workflows and lint python

 [flake8]-exclude = build,.git,build-pypy,.tox+exclude =+    .git,+    __pycache__,+    docs/source/conf.py,+    docs/conf.py,

Because he will still check it, but the content of conf.py does not meet the EPE8 specification, so Flake8, Pylint, MyPy, etc. still check this directory.

In addition, I suggest that all non-Python directories and folders be added here, so that the CI part can be targeted at the specified directory, reducing the ignorance of some Python programs.

timmy61109

comment created time in 3 days

Pull request review commentdulwich/dulwich

Update ignore, requirements.txt, workflows and lint python

 [flake8]-exclude = build,.git,build-pypy,.tox+exclude =+    .git,+    __pycache__,+    docs/source/conf.py,

I think it is possible that some of the contents of this project are not structured according to the directory structure of most projects for technical manuals, but I am not sure about this, but most of the conf.py I found will be in docs/ Under the source/ directory.

So I want to ask why is it different?

timmy61109

comment created time in 3 days

Pull request review commentdulwich/dulwich

Update ignore, requirements.txt, workflows and lint python

 [flake8]-exclude = build,.git,build-pypy,.tox+exclude =+    .git,+    __pycache__,+    docs/source/conf.py,+    docs/conf.py,+    old,

I think it is possible that some of the contents of this project are not structured according to the directory structure of most projects for technical manuals, but I am not sure about this, but most of the conf.py I found will be in docs/ Under the source/ directory.

So I want to ask why is it different?

timmy61109

comment created time in 3 days

more