Is unix file path a valid URL? - url

Question

Suppose we have a string /path/to/file, when I use urlparse of Python, it will treat the string as a valid URL and return the following result:
from urllib.parse import urlparse
urlparse('/path/to/file')
# ParseResult(scheme='', netloc='', path='/path/to/file', params='', query='', fragment='')
But if I do the same thing with JavaScript, it will throw the following error
new URL('/path/to/file')
// Uncaught TypeError: Failed to construct 'URL': Invalid URL
I am wondering which implemetation is right. Shall a unix file path treat as a valid URL? I don't dive in to the RFCs, but personally I prefer the way of Python as it makes it clear to distingiush local file or remote resource by parsing it and checking the scheme field. It's useful when you write a program that allow use to load file from local or remote.
Update:
According to the document provided by Alexei Levenkov
: The Fine Manual on JavaScript it says
url: A string ... that represents an absolute or relative URL. If url is a relative URL, base is required, and will be used as the base URL. If url is an absolute URL, a given base will be ignored.
In JavaScript it will not throw error if base parameters is provided
new URL('/path/to/file', 'file://')
But it still have gap with the implement of python when input string is a relative path ./path/to/file.
In JavaScript it will ignore the ./ but Python will still keep it.
JavaScript:
new URL('/path/to/file', 'file://')
new URL('./path/to/file', 'file://')
// both yeild the same result:
// URL {origin: 'file://', protocol: 'file:', pathname: '/path/to/file'}
Python:
from urllib.parse import urlparse
urlparse('/path/to/file')
# ParseResult(scheme='', netloc='', path='/path/to/file', params='', query='', fragment='')
urlparse('./path/to/file')
# ParseResult(scheme='', netloc='', path='./path/to/file', params='', query='', fragment='')