You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Tishj (via GitHub)" <gi...@apache.org> on 2023/11/13 12:00:53 UTC
[I] Time32Type "unit" docs are outdated [arrow]
Tishj opened a new issue, #38683:
URL: https://github.com/apache/arrow/issues/38683
### Describe the bug, including details regarding any error messages, version, and platform.
<https://arrow.apache.org/docs/python/generated/pyarrow.Time32Type.html>
This claims that these are valid options for `unit`:
> The time unit (‘s’, ‘ms’, ‘us’ or ‘ns’).
Using help on the `pyarrow.time32` method shows that only `s` and `ms` are valid options.
### Component(s)
Documentation, Python
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@arrow.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Python][Docs] Time32Type "unit" docs are outdated [arrow]
Posted by "jorisvandenbossche (via GitHub)" <gi...@apache.org>.
jorisvandenbossche closed issue #38683: [Python][Docs] Time32Type "unit" docs are outdated
URL: https://github.com/apache/arrow/issues/38683
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Time32Type "unit" docs are outdated [arrow]
Posted by "rok (via GitHub)" <gi...@apache.org>.
rok commented on issue #38683:
URL: https://github.com/apache/arrow/issues/38683#issuecomment-1808134360
Agreed. That is not documented correctly.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Python][Docs] Time32Type "unit" docs are outdated [arrow]
Posted by "ShaiviAgarwal2 (via GitHub)" <gi...@apache.org>.
ShaiviAgarwal2 commented on issue #38683:
URL: https://github.com/apache/arrow/issues/38683#issuecomment-1809916444
Based on the information you provided, it seems that there is a discrepancy between the documentation and the actual implementation of the **pyarrow.time32 method**. The documentation claims that the valid options for the time unit are `'s', 'ms', 'us', or 'ns'`, while the help command shows that only `'s' and 'ms'` are valid options. This could potentially cause confusion for developers trying to use this library.
Can you please provide more information about the error messages and version you are using?
> ### Describe the bug, including details regarding any error messages, version, and platform.
> https://arrow.apache.org/docs/python/generated/pyarrow.Time32Type.html
>
> This claims that these are valid options for `unit`:
>
> > The time unit (‘s’, ‘ms’, ‘us’ or ‘ns’).
>
> Using help on the `pyarrow.time32` method shows that only `s` and `ms` are valid options.
>
> ### Component(s)
> Documentation, Python
Based on the information you provided, it seems that there is a discrepancy between the documentation and the actual implementation of the **pyarrow.time32** method. The documentation claims that the valid options for the time unit are '`s', 'ms', 'us', or 'ns'`, while the help command shows that only `'s' and 'ms'` are valid options. This could potentially cause confusion for developers trying to use this library.
Can you please provide more information about the error messages and version you are using?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org