Update README.md
Browse files
README.md
CHANGED
@@ -25,3 +25,31 @@ configs:
|
|
25 |
- split: train
|
26 |
path: data/train-*
|
27 |
---
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
25 |
- split: train
|
26 |
path: data/train-*
|
27 |
---
|
28 |
+
|
29 |
+
# ManyTypes4Py-Reconstructed
|
30 |
+
|
31 |
+
This is a reconstruction of the original code from the [ManyTypes4Py paper]
|
32 |
+
from the following paper
|
33 |
+
|
34 |
+
A. M. Mir, E. Latoškinas and G. Gousios, "ManyTypes4Py: A Benchmark Python
|
35 |
+
Dataset for Machine Learning-based Type Inference," *IEEE/ACM International
|
36 |
+
Conference on Mining Software Repositories (MSR)*, 2021, pp. 585-589
|
37 |
+
|
38 |
+
[The artifact] (v0.7) for ManyTypes4Py does not have the original Python files.
|
39 |
+
Instead, each file is pre-processed into a stream of types without comments,
|
40 |
+
and the contents of each repository are stored in a single JSON file.
|
41 |
+
This reconstructed dataset has raw Python code.
|
42 |
+
|
43 |
+
More specifically:
|
44 |
+
|
45 |
+
1. We extract the list of repositories from the "clean" subset of ManyTypes4Py,
|
46 |
+
which are the repositories that type-check with *mypy*.
|
47 |
+
|
48 |
+
2. We attempt to download all repositories, but only succeed in fetching
|
49 |
+
4,663 (out of ~5.2K).
|
50 |
+
|
51 |
+
3. We augment each file with the text of each type annotation, as well as their
|
52 |
+
start and end positions (in bytes) in the code.
|
53 |
+
|
54 |
+
[ManyTypes4 paper]: https://arxiv.org/abs/2104.04706
|
55 |
+
[The artifact]: https://zenodo.org/records/4719447
|