Extend the os module #1175
Extend the os module #1175
Comments
|
Ok, I'm working on get/set uid, guid etc. stuff |
|
I'm going to take a stab at Also, as a general question, is the current goal to match CPython functionality here? Currently it doesn't seem that the os module is implemented in C for CPython. Is the goal here to implement the Python os module in Rust as, for example, the sys module in CPython is implemented in C and not in Python? Or am I completely missing something here? |
|
Because Rust's cross-platform support is so much better than C's, we decided to implement a single |
|
Ah, gotcha..so for |
|
Yep, and you can use the |
|
cool cool, thanks! |
|
PR #1524 has an implementation of |
This comment has been hidden.
This comment has been hidden.
|
Hi, new here. I was just wondering how to start working on one of these outstanding implementations without having any overlap with others? Should we open a new issue for what we want to tackle and then have it assigned to us? Thanks! |
|
I'm so sorry for not responding earlier @nicholasraphael, if you're still interested you can feel free to just open a PR for it; there are a lot of functions and hopefully what you choose won't conflict if anyone else is working on something. You could also just comment what you're working on in this thread. |
|
It's always possible to just do |
|
Hey, I wanted to work on some of these issue. But how can I create tests for this ? Basically after I implement a method, how can I test if it's working as expected? Sorry quite new here. |
|
hi @coolreader18 is the list here #1175 (comment) updated? i'd like to start working on one of the API's thanks! |
|
@AthulMuralidhar I think of that list,
still need to be implemented in os.rs |
|
thanks for the quick reply @coolreader18 i'll try to work on |
Currently, the python
osmodule is missing many methods. Try adding a method to this module by editing the filevm/src/stdlib/os.rs.This is an issue for new contributors, so please do not implement everything at once, so other people have a chance to go for it (or, actually, please implement all! >:)! ).
The text was updated successfully, but these errors were encountered: