diff --git a/.gitignore b/.gitignore index 8321f55..4d3c4ac 100644 --- a/.gitignore +++ b/.gitignore @@ -7,3 +7,4 @@ /mypy-lang-0.3.1.tar.gz /mypy-lang-0.4.1.tar.gz /mypy-lang-0.4.2.tar.gz +/mypy-lang-0.4.3.tar.gz diff --git a/0001-Look-for-typeshed-in-usr-share.patch b/0001-Look-for-typeshed-in-usr-share.patch index 488dc18..ef409c0 100644 --- a/0001-Look-for-typeshed-in-usr-share.patch +++ b/0001-Look-for-typeshed-in-usr-share.patch @@ -1,4 +1,4 @@ -From 8a7f0e201878777c9513928f2fc232b245efe681 Mon Sep 17 00:00:00 2001 +From acb21f10d34135171035cdde696fa28c9b81336d Mon Sep 17 00:00:00 2001 From: David Shea Date: Tue, 15 Dec 2015 14:01:55 -0500 Subject: [PATCH 1/2] Look for typeshed in /usr/share @@ -10,10 +10,10 @@ Skip installing the bundled typeshed 2 files changed, 1 insertion(+), 3 deletions(-) diff --git a/mypy/build.py b/mypy/build.py -index d37dc78..327c441 100644 +index c4b9459..6195b7d 100644 --- a/mypy/build.py +++ b/mypy/build.py -@@ -257,7 +257,7 @@ def default_data_dir(bin_dir: str) -> str: +@@ -225,7 +225,7 @@ def default_data_dir(bin_dir: Optional[str]) -> str: return dir elif base == 'bin': # Installed to somewhere (can be under /usr/local or anywhere). @@ -23,7 +23,7 @@ index d37dc78..327c441 100644 # Assume we installed python3 with brew on os x return os.path.join(os.path.dirname(dir), 'lib', 'mypy') diff --git a/setup.py b/setup.py -index 69cbfb2..570830a 100644 +index 10da829..a35837c 100644 --- a/setup.py +++ b/setup.py @@ -53,8 +53,6 @@ def find_data_files(base, globs): @@ -36,5 +36,5 @@ index 69cbfb2..570830a 100644 classifiers = [ -- -2.8.2 +2.9.2 diff --git a/0002-Canonicalize-bin_dir-when-looking-for-data_dir.patch b/0002-Canonicalize-bin_dir-when-looking-for-data_dir.patch index 8a898bd..d050d26 100644 --- a/0002-Canonicalize-bin_dir-when-looking-for-data_dir.patch +++ b/0002-Canonicalize-bin_dir-when-looking-for-data_dir.patch @@ -1,4 +1,4 @@ -From bf379518a15c340a0989f7e00eac99d64e94a428 Mon Sep 17 00:00:00 2001 +From 90222ce2272cda680a71671e82177d752e2ae547 Mon Sep 17 00:00:00 2001 From: David Shea Date: Thu, 7 Jan 2016 10:02:27 -0500 Subject: [PATCH 2/2] Canonicalize bin_dir when looking for data_dir. @@ -10,10 +10,10 @@ in /usr instead of /. 1 file changed, 4 insertions(+) diff --git a/mypy/build.py b/mypy/build.py -index 327c441..320a363 100644 +index 6195b7d..0e139bb 100644 --- a/mypy/build.py +++ b/mypy/build.py -@@ -246,6 +246,10 @@ def default_data_dir(bin_dir: str) -> str: +@@ -214,6 +214,10 @@ def default_data_dir(bin_dir: Optional[str]) -> str: return subdir # Default to directory containing this file's parent. return parent @@ -25,5 +25,5 @@ index 327c441..320a363 100644 dir = os.path.dirname(bin_dir) if (sys.platform == 'win32' and base.lower() == 'scripts' -- -2.8.2 +2.9.2 diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..a6a3cce --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,156 @@ +Contributing to Mypy +==================== + +Welcome! Mypy is a community project that aims to work for a wide +range of Python users and Python codebases. If you're trying Mypy on +your Python code, your experience and what you can contribute are +important to the project's success. + + +Getting started, building, and testing +-------------------------------------- + +If you haven't already, take a look at the project's +[README.md file](README.md) +and the [Mypy documentation](http://mypy.readthedocs.io/en/latest/), +and try adding type annotations to your file and type-checking it with Mypy. + + +Discussion +---------- + +If you've run into behavior in Mypy you don't understand, or you're +having trouble working out a good way to apply it to your code, or +you've found a bug or would like a feature it doesn't have, we want to +hear from you! + +Our main forum for discussion is the project's [GitHub issue +tracker](https://github.com/python/mypy/issues). This is the right +place to start a discussion of any of the above or most any other +topic concerning the project. + +We have an IRC channel, `#python-mypy` on irc.freenode.net. This is +lightly used, but some Mypy core developers are almost always present; +feel free to find us there and we're happy to chat. Substantive +technical discussion will be directed to the issue tracker. + +#### Code of Conduct + +Everyone participating in the Mypy community, and in particular in our +issue tracker, pull requests, and IRC channel, is expected to treat +other people with respect and more generally to follow the guidelines +articulated in the [Python Community Code of +Conduct](https://www.python.org/psf/codeofconduct/). + + +Submitting Changes +------------------ + +Even more excellent than a good bug report is a fix for a bug, or the +implementation of a much-needed new feature. (*) We'd love to have +your contributions. + +(*) If your new feature will be a lot of work, we recommend talking to + us early -- see below. + +We use the usual GitHub pull-request flow, which may be familiar to +you if you've contributed to other projects on GitHub. For the mechanics, +see [our git and GitHub workflow help page](https://github.com/python/mypy/wiki/Using-Git-And-GitHub), +or [GitHub's own documentation](https://help.github.com/articles/using-pull-requests/). + +Anyone interested in Mypy may review your code. One of the Mypy core +developers will merge your pull request when they think it's ready. +For every pull request, we aim to promptly either merge it or say why +it's not yet ready; if you go a few days without a reply, please feel +free to ping the thread by adding a new comment. + +At present the core developers are (alphabetically): +* David Fisher (@ddfisher) +* Jukka Lehtosalo (@JukkaL) +* Greg Price (@gnprice) +* Guido van Rossum (@gvanrossum) + + +Preparing Changes +----------------- + +Before you begin: if your change will be a significant amount of work +to write, we highly recommend starting by opening an issue laying out +what you want to do. That lets a conversation happen early in case +other contributors disagree with what you'd like to do or have ideas +that will help you do it. + +The best pull requests are focused, clearly describe what they're for +and why they're correct, and contain tests for whatever changes they +make to the code's behavior. As a bonus these are easiest for someone +to review, which helps your pull request get merged quickly! Standard +advice about good pull requests for open-source projects applies; we +have [our own writeup](https://github.com/python/mypy/wiki/Good-Pull-Request) +of this advice. + +See also our [coding conventions](https://github.com/python/mypy/wiki/Code-Conventions) -- +which consist mainly of a reference to +[PEP 8](https://www.python.org/dev/peps/pep-0008/) -- for the code you +put in the pull request. + +You may also find other pages in the +[Mypy developer guide](https://github.com/python/mypy/wiki/Developer-Guides) +helpful in developing your change. + + +Issue-tracker conventions +------------------------- + +We aim to reply to all new issues promptly. We'll assign a milestone +to help us track which issues we intend to get to when, and may apply +labels to carry some other information. Here's what our milestones +and labels mean. + +### Milestones + +We use GitHub "milestones" ([see our +list](https://github.com/python/mypy/milestones)) to roughly order +what we want to do soon and less soon. + +This means they represent a combination of priority and scale of work. +Bugs that aren't a huge deal but do matter to users and don't seem +like a lot of work to fix generally go in a near milestone; things +that will take longer may go further out. + +Specifically: + +* **Numbered milestones** correspond to releases. These assignments + are changeable, and issues may be moved earlier or later. + Assignments to further-out milestones are more likely to + change. +* Point releases, like 0.x.y when we're already at 0.x.z, generally + have issues that are less work to tackle and whose user-facing + impact is small or a bugfix. Meatier or more radical issues + generally go to a full "minor" release, like 0.x.0. +* **Future** has other things we don't currently plan to get to anytime + soon -- akin to "backlog" in some systems. +* **Questions** is for issue threads where a user is asking a question + but it isn't yet clear that it represents something to actually + change. We use the issue tracker as the preferred venue for such + questions, even when they aren't literally issues, to keep down the + number of distinct discussion venues anyone needs to track. These + might move to a different milestone if after discussion a bug or + feature request emerges. +* Issues **without a milestone** haven't been triaged. We aim to + triage all new issues promptly, but there are some issues from 2015 + and earlier that we haven't yet reviewed for triage since adopting + these conventions. + +### Labels + +* **needs discussion**: This issue needs agreement on some kind of + design before it makes sense to implement it, and it either doesn't + yet have a design or doesn't yet have agreement on one. +* **feature**, **bug**, **refactoring**: These classify the user-facing + impact of the change. Specifically "refactoring" means there should + be no user-facing effect. +* **duplicate**, **wontfix**: These identify issues that we've closed + for the respective reasons. +* **priority**, **question**, **postponed**: These labels predate the + milestone conventions and are deprecated; they should be gone on all + issues that have been triaged to a milestone. diff --git a/README.md b/README.md index d056fad..07cbf21 100644 --- a/README.md +++ b/README.md @@ -4,6 +4,13 @@ Mypy: Optional Static Typing for Python [![Build Status](https://travis-ci.org/python/mypy.svg)](https://travis-ci.org/python/mypy) +Got a question? File an issue! +------------------------------ + +We don't have a mailing list; but we are always happy to answer questions +filed as issues in our [tracker](https://github.com/python/mypy/issues). + + What is mypy? ------------- diff --git a/python3-mypy.spec b/python3-mypy.spec index 47c08b6..99c2952 100644 --- a/python3-mypy.spec +++ b/python3-mypy.spec @@ -1,7 +1,7 @@ Name: python3-mypy # Last actual version was 0.2.0, which is 7805b2c, continues as 0.2.0_dev -Version: 0.4.2 -Release: 2 +Version: 0.4.3 +Release: 1 Summary: A static type checker for Python %{?python_provide:%python_provide python3-mypy} @@ -9,12 +9,13 @@ Summary: A static type checker for Python # package does not include those files License: MIT URL: https://github.com/python/mypy -Source0: mypy-lang-%{version}.tar.gz +Source0: https://pypi.python.org/packages/a8/8c/a20d897c709901c3332e87c8521a18664671fe7fd9e426082300b4b9a341/mypy-lang-%{version}.tar.gz # doc files are missing from sdist, these are the copies from upstream github Source1: LICENSE Source2: README.md Source3: CREDITS +Source4: CONTRIBUTING.md # Change the search for data_dir to use Fedora's typeshed package instead of a # bundled version @@ -44,6 +45,7 @@ running them! cp %{SOURCE1} . cp %{SOURCE2} . cp %{SOURCE3} . +cp %{SOURCE4} . %build %py3_build @@ -64,7 +66,7 @@ PYTHONPATH=%{buildroot}%{python3_sitelib} \ %{buildroot}%{_bindir}/stubgen %files -%doc README.md CREDITS +%doc README.md CREDITS CONTRIBUTING.md %license LICENSE %{python3_sitelib}/mypy %{python3_sitelib}/mypy_lang-*.egg-info @@ -76,6 +78,9 @@ PYTHONPATH=%{buildroot}%{python3_sitelib} \ %{_prefix}/lib/mypy %changelog +* Mon Jul 18 2016 David Shea - 0.4.3-1 +- Update to mypy 0.4.3 + * Mon Jun 13 2016 David Shea - 0.4.2-1 - Update to mypy 0.4.2 diff --git a/sources b/sources index 51ddc91..30951be 100644 --- a/sources +++ b/sources @@ -1 +1 @@ -c69737b88598c52e16b24ccadb4e9d0e mypy-lang-0.4.2.tar.gz +4d3e9add7336a018aabe67aee7158031 mypy-lang-0.4.3.tar.gz