Hypothesis: PyCon Australia 2018 Sprints!

Created on 27 Aug 2018  Â·  34Comments  Â·  Source: HypothesisWorks/hypothesis

Hello to everyone at the sprints! This issue is the place to get started, comment to claim an issue (please talk to me first), and so on. Thanks for helping out!

The "what is Hypothesis" pack: my talk if you like videos, the docs as a general overview, and these quick excercises to try it out.

All of the following are valued contributions: reading docs or trying to use hypothesis and telling me what you found confusing; adding Hypothesis tests to other open-source projects (e.g. Pandas, dateutil, Xarray, etc - ask me!); new documentation or blog posts or artwork; and of course traditional code whether bugfixes or new features!

General checklist:

  1. Talk to Zac about what you want to do - I can help you find the right issue (start here) or other way to contribute :smile:
  2. (optional): read CONTRIBUTING.rst and check what's in the guides/ directory for tips.
  3. Comment below so people don't work on the same issue by accident!
  4. Do the thing :snake:
  5. Open a PR :tada:
meta

Most helpful comment

Thanks so much everyone for working on Hypothesis at the sprints - I had a great time and hope you did too. It's also been fantastic for the project - nine releases so far, another five expected in the near future, and other important contributions from better testing to gorgeous artwork.

From here on, we're back in normal development mode - so while this issue will be closed, you can @-mention me and I'll help out if I can.

:tada: :snake: :heart_eyes:

All 34 comments

It turns out that our install instructions are out of date - issue for old or confusing docs incoming, but first:

  • Fork and clone this repo
  • On OSX and Linux you can use the build.sh described in CONTRIBUTING.rst;
    alternatively or on Windows:
  • pip install -e hypothesis-python/ in the cloned repo
  • pip install -r requirements/tools.in
  • pip install -r requirements/test.in
  • (optional) pytest hypothesis-python/tests/cover -n auto warning: ~20 CPU-minutes

And now you're ready to go! I generally recommend developing with a Python3 environment, as some of our tools (e.g. mypy) don't work on Python 2 even though Hypothesis does.

adding here as @Zac-HD advised...
i'll be helping on the following issue one my machine is setup:
https://github.com/HypothesisWorks/hypothesis/issues/1317

I am working on "replace pickle with json" issue

1512

I'll be helping on #1115 – "Consider adding a simple subsets / subsequences strategy".

I'm having a look at #1238 :)

I will have a look at #356 (capture logging)

Having a look at #1486

Gonna take a geez at #848.

I'm going to look at #1410 - "note should print when verbosity is set to at least verbose"

Going to look at #1383

any quick patch that can be done in around 1.5hrs?
image

Is this still a problem?
https://github.com/HypothesisWorks/hypothesis/issues/1493

I'm able to setup and debug in Visual Studio 2017.
I can try check VS Code if it's still an issue there.

I think it's still a problem, but I don't use VS Code - if you can't reproduce it I'd be happy to close the issue, or if you can confirm and provide more detail that would also be great :smile:

Working on #1311

Regarding #1493

Please don't close the issue.
I'm able to reproduce it in Visual Studio 2017.
I'm able to confirm the following:

  • Debugging using custom decorator works
  • Debugging using @given doesn't work. It runs, but doesn't stop on breakpoint.

I'll try to investigate further.

I've claimed #840.

I've claimed #847

Looking at #1223

Also, working on #1520

@Zac-HD I've got a branch ready to make a PR. I created the RELEASE file and updated CONTRIBUTING.rst. If you wanted to check out the branch it's https://github.com/00willo/hypothesis/tree/improve-setup.py . If that looks all good, am I good to make a PR?

@00willo - looks great! I'd use the following patch note, but with that it's time to open a PR :tada:

This patch improves the packaging of the Python package by adding
``LICENSE.txt`` to the sdist (:issue:`1311`), clarifying the minimum
supported versions of :pypi:`pytz` and :pypi:`dateutil <python-dateutil>`
(:issue:`1383`), and adds keywords to the metadate (:issue:`1520`).

Thanks to ...

Sweet, I'll update and submit the PR in the next few mins

@Zac-HD Ah, sorry, I just realised that my branch is behind upstream master, do your merge checks handle that automagically in the PR process?

Yep, should all be fine - it tests the result of merging your branch into master.

Looking at #1223

Looking at #1085

I'm looking at #1337

PR #1522 up for review

I worked out how to run invoke the various tests locally. I'll drop a comment in the documentation issue.

PR #1522 up for review

Approved! I'll start merging stuff after 6pm ish, to avoid CI conflicts for those still pushing changes :smile:

I'm not claiming #847 anymore. It's most likely a maintainer level issue

Thanks so much everyone for working on Hypothesis at the sprints - I had a great time and hope you did too. It's also been fantastic for the project - nine releases so far, another five expected in the near future, and other important contributions from better testing to gorgeous artwork.

From here on, we're back in normal development mode - so while this issue will be closed, you can @-mention me and I'll help out if I can.

:tada: :snake: :heart_eyes:

Was this page helpful?
0 / 5 - 0 ratings