Skip to content

Commit 19f56f0

Browse files
committed
Update README
1 parent 575696f commit 19f56f0

File tree

1 file changed

+10
-14
lines changed

1 file changed

+10
-14
lines changed

README.md

Lines changed: 10 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -9,28 +9,24 @@ where we have had to deviate from the C++ API, however.
99

1010
## Current status
1111

12-
Currently, Haiku-PyAPI is best suited to scripts and small, simple
13-
applications.
12+
Virtually everything from Haiku's API is available. It is likely that you will
13+
run into some bugs if you try to make an application. Please report them! Also,
14+
there's a good chance we can give you a workaround to use until it is fixed.
1415

15-
Almost everything in the app and interface kits have been ported. The storage
16-
kit has mostly been ported. The support kit has only partially been ported.
17-
The other kits haven't been ported yet.
18-
19-
Of the kits that have been ported, many of the functions haven't been tested
20-
yet. You should, therefore, expect to encounter problems occasionally. Besides
21-
this, you can expect memory leaks, as little work has been done on getting
22-
memory freed correctly once it is no longer needed.
16+
Probably, the biggest bug is memory leaks. Unless memory management for a class
17+
was simple for us to do, it is likely that we opted to never free the memory
18+
so that we could worry about memory management later!
2319

2420
## Installing
21+
2522
### From HaikuPorts
23+
2624
Installation on Haiku is easy, just run
25+
2726
```
2827
pkgman install haiku_pyapi_python310
2928
```
30-
or
31-
```
32-
pkgman install haiku_pyapi_python39
33-
```
29+
3430
If you need the latest widgets and bugfixes, then you should compile from source, see below.
3531

3632
### From source

0 commit comments

Comments
 (0)