VMS Python compatibility issues - Revision history

Marty.stu at 07:50, 1 July 2021

2021-07-01T07:50:39Z

Marty.stu at 07:48, 1 July 2021

2021-07-01T07:48:33Z

← Older revision		Revision as of 07:48, 1 July 2021
Line 45:		Line 45:
	##Compiler does not support relative include paths		##Compiler does not support relative include paths
	----		----
	[[Category:VMS ~~IDE~~]]		[[Category:VMS Python]]

Brett.cameron at 00:58, 13 September 2020

2020-09-13T00:58:58Z

← Older revision		Revision as of 00:58, 13 September 2020
Line 30:		Line 30:
	##Binding a socket to an empty address fails (wildcard resolved to multiple address)		##Binding a socket to an empty address fails (wildcard resolved to multiple address)
	##<code>getpeername()</code> returns ‘0.0.0.0’ instead of an error		##<code>getpeername()</code> returns ‘0.0.0.0’ instead of an error
	##~~OpenVMS crashed on~~ <code>socket.socket.sendall</code>		##<code>socket.socket.sendall</code> does not work correctly (process may crash)
	#Time		#Time
	##<code>time_t</code> is unsigned		##<code>time_t</code> is unsigned
Line 40:		Line 40:
	##There is no appropriate way to programmatically get all environment variables (logical names and/or symbols)		##There is no appropriate way to programmatically get all environment variables (logical names and/or symbols)
	##The current OpenVMS port of sqlite3 does not support "OR ROLLBACK"		##The current OpenVMS port of sqlite3 does not support "OR ROLLBACK"
	~~##Program prints crush dump~~
	##<code>locale.strxfrm()</code> does not work as expected		##<code>locale.strxfrm()</code> does not work as expected
	#Compiler		#Compiler

Brett.cameron at 00:54, 13 September 2020

2020-09-13T00:54:16Z

← Older revision		Revision as of 00:54, 13 September 2020
Line 27:		Line 27:
	##Processes do not handle recursion overflow cleanly		##Processes do not handle recursion overflow cleanly
	#Sockets		#Sockets
	##<code>AF_UNIX</code> has different meaning		##<code>AF_UNIX</code> has somewhat different meaning
	##Binding socket to empty address fails (wildcard resolved to multiple address).		##Binding a socket to an empty address fails (wildcard resolved to multiple address)
	##<code>getpeername()</code> returns ‘0.0.0.0’ instead of error		##<code>getpeername()</code> returns ‘0.0.0.0’ instead of an error
	##OpenVMS crashed on <code>socket.socket.sendall</code>		##OpenVMS crashed on <code>socket.socket.sendall</code>
	#Time		#Time
Line 38:		Line 38:
	##*<code>%4Y</code> is padded with spaces		##*<code>%4Y</code> is padded with spaces
	#Miscellaneous		#Miscellaneous
	##~~Environment variables have unusual implementation - through logical names.~~ There is no appropriate way to get all environment variables.		##There is no appropriate way to programmatically get all environment variables (logical names and/or symbols)
	##The OpenVMS sqlite3 ~~port~~ does not support "OR ROLLBACK"		##The current OpenVMS port of sqlite3 does not support "OR ROLLBACK"
	##Program prints crush dump		##Program prints crush dump
	##<code>locale.strxfrm()</code> ~~works unusual~~		##<code>locale.strxfrm()</code> does not work as expected
	#Compiler		#Compiler
	##<code>uint_ptr</code> is always 64 bit, void* is 32 bit or 64 bit		##<code>uint_ptr</code> is always 64-bit, <code>void*</code> is either 32-bit or 64-bit (depending on selected pointer size)
	##Compiler does not support relative include paths		##Compiler does not support relative include paths
	----		----
	[[Category:VMS IDE]]		[[Category:VMS IDE]]

Brett.cameron at 00:42, 13 September 2020

2020-09-13T00:42:44Z

← Older revision		Revision as of 00:42, 13 September 2020
Line 35:		Line 35:
	##<code>strftime()</code>		##<code>strftime()</code>
	##*Does not support <code>%G</code> format		##*Does not support <code>%G</code> format
	##*Exhibits undefined behavior when format ends with <code>'%'</code>		##*Exhibits undefined behavior when format ends with <code>%</code>
	##*<code>‘%~~4Y’~~</code> is padded with spaces		##*<code>%4Y</code> is padded with spaces
	#Miscellaneous		#Miscellaneous
	##Environment variables have unusual implementation - through logical names. There is no appropriate way to get all environment variables.		##Environment variables have unusual implementation - through logical names. There is no appropriate way to get all environment variables.
	##OpenVMS sqlite3 port does not support "OR ROLLBACK"		##The OpenVMS sqlite3 port does not support "OR ROLLBACK"
	##Program prints crush dump		##Program prints crush dump
	##<code>locale.strxfrm()</code> works unusual		##<code>locale.strxfrm()</code> works unusual

Brett.cameron at 00:41, 13 September 2020

2020-09-13T00:41:14Z

← Older revision		Revision as of 00:41, 13 September 2020
Line 25:		Line 25:
	##Interrupting I/O operations may cause the process to hang		##Interrupting I/O operations may cause the process to hang
	##There is no root user with zero UID		##There is no root user with zero UID
	##~~There is no unix commands like: echo, exit …~~		##Processes do not handle recursion overflow cleanly
	~~##OpenVMS cannot~~ handle recursion overflow ~~properly - just crashes~~
	#Sockets		#Sockets
	##<code>AF_UNIX</code> has different meaning		##<code>AF_UNIX</code> has different meaning
Line 35:		Line 34:
	##<code>time_t</code> is unsigned		##<code>time_t</code> is unsigned
	##<code>strftime()</code>		##<code>strftime()</code>
	##*Does not support %G format		##*Does not support <code>%G</code> format
	##*~~Undefined~~ behavior when format ends with '%'		##*Exhibits undefined behavior when format ends with <code>'%'</code>
	##*‘%4Y’ is padded with spaces		##*<code>‘%4Y’</code> is padded with spaces
	#Miscellaneous		#Miscellaneous
	##Environment variables have unusual implementation - through logical names. There is no appropriate way to get all environment variables.		##Environment variables have unusual implementation - through logical names. There is no appropriate way to get all environment variables.

Brett.cameron at 00:38, 13 September 2020

2020-09-13T00:38:00Z

← Older revision		Revision as of 00:38, 13 September 2020
Line 22:		Line 22:
	##The functions <code>select()</code> and <code>poll()</code> work only with sockets		##The functions <code>select()</code> and <code>poll()</code> work only with sockets
	##The function <code>siginterrupt()</code> is not supported		##The function <code>siginterrupt()</code> is not supported
	##~~A lot of~~ issues with signals		##Numerous compatibility issues with signals
	##Interrupting I/O ~~operation~~ may hang		##Interrupting I/O operations may cause the process to hang
	##There is no root user with zero ~~uid~~		##There is no root user with zero UID
	##There is no unix commands like: echo, exit …		##There is no unix commands like: echo, exit …
	##OpenVMS cannot handle recursion overflow properly - just crashes		##OpenVMS cannot handle recursion overflow properly - just crashes

Brett.cameron at 00:33, 13 September 2020

2020-09-13T00:33:58Z

← Older revision		Revision as of 00:33, 13 September 2020
Line 17:		Line 17:
	##On OpenVMS <code>mkdir()</code> creates all intermediate directories (if required)		##On OpenVMS <code>mkdir()</code> creates all intermediate directories (if required)
	#Process		#Process
	##There is no ~~normal~~ <code>fork()</code>, <code>spawn()</code> ~~function.~~		##There are no Linux-like <code>fork()</code> and <code>spawn()</code> functions
	##Pipes are created via mailbox and ~~have a lot of~~ compatibility issues.		##Pipes are created via mailbox and are not totally compatible with UNIX pipes (compatibility issues)
	##If child has threads, each thread posts 'END-OF-PIPE' when ~~it finishes.~~		##If a child process has threads, each thread posts 'END-OF-PIPE' when the child completes/terminates
	##~~There is no normal~~ <code>select()</code>, <code>poll()</code> ~~e.t.c~~		##The functions <code>select()</code> and <code>poll()</code> work only with sockets
	##<code>siginterrupt()</code> is not supported		##The function <code>siginterrupt()</code> is not supported
	##A lot of issues with signals		##A lot of issues with signals
	##Interrupting I/O operation may hang		##Interrupting I/O operation may hang

Brett.cameron at 00:11, 13 September 2020

2020-09-13T00:11:19Z

← Older revision		Revision as of 00:11, 13 September 2020
Line 1:		Line 1:
	#File system		#File system
	##Directories and files with the same name are allowed.		##Directories and files with the same name are allowed
	##~~File has a version~~, therefore two files with the same name might have different content.		##Files have versioning, therefore two files with the same name might have different content
	##Shared stream I/O does not work.		##Shared stream I/O does not work
	##To guarantee the file content is on the disk the <code>fsync()</code> function must be used.		##To guarantee the file content is on the disk the <code>fsync()</code> function must be used
	##Because of using logical names the real file path may be different from ~~path~~ used to open file.		##Because files can be referenced using logical names the real file path may be different from the “path” used to open a file
	##Files has no access time attribute.		##Files has no access time attribute
	##Changing a files permissions also changes its modification time.		##Changing a files permissions also changes its modification time
	##Changing the content of a directory does not change the directory modification time.		##Changing the content of a directory does not change the directory modification time.
	##~~File has~~ four rights bits - read, write, execute and delete~~. In unix it~~ has three ~~of it -~~ read, write and execute.		##Files have four rights bits (read, write, execute, and delete); Linux (UNIX) has only three (read, write, and execute)
	##‘.DIR’ extension is reserved		##The ‘.DIR’ extension is reserved
	##Non-blocking file IO is not supported in the OpenVMS CRTL.		##Non-blocking file IO is not supported by the OpenVMS CRTL
	##There are various known issues with symbolic link implementation.		##There are various known issues with symbolic link implementation
	##~~Symbol~~ '$' is ~~usual for~~ file and directory names		##The symbol '$' is commonly used in file and directory names
	##OpenVMS ~~<code>~~chmod(0)~~</code>~~ sets user's default permissions~~, not resets them~~		##On OpenVMS chmod(0) sets the user's default permissions as opposed to resetting permissions
	##To delete directory user has to have ‘delete’ permission for ~~this~~ directory		##To delete a directory the user has to have ‘delete’ permission for the directory
	##OpenVMS ~~creates all intermediate directories on~~ <code>mkdir()</code>		##On OpenVMS <code>mkdir()</code> creates all intermediate directories (if required)
	#Process		#Process
	##There is no normal <code>fork()</code>, <code>spawn()</code> function.		##There is no normal <code>fork()</code>, <code>spawn()</code> function.

Brett.cameron at 23:54, 12 September 2020

2020-09-12T23:54:50Z

← Older revision		Revision as of 07:50, 1 July 2021
Line 1:		Line 1:
	#File system		= File system =
	##Directories and files with the same name are allowed		#Directories and files with the same name are allowed
	##Files have versioning, therefore two files with the same name might have different content		#Files have versioning, therefore two files with the same name might have different content
	##Shared stream I/O does not work		#Shared stream I/O does not work
	##To guarantee the file content is on the disk the <code>fsync()</code> function must be used		#To guarantee the file content is on the disk the <code>fsync()</code> function must be used
	##Because files can be referenced using logical names the real file path may be different from the “path” used to open a file		#Because files can be referenced using logical names the real file path may be different from the “path” used to open a file
	##Files has no access time attribute		#Files has no access time attribute
	##Changing a files permissions also changes its modification time		#Changing a files permissions also changes its modification time
	##Changing the content of a directory does not change the directory modification time.		#Changing the content of a directory does not change the directory modification time.
	##Files have four rights bits (read, write, execute, and delete); Linux (UNIX) has only three (read, write, and execute)		#Files have four rights bits (read, write, execute, and delete); Linux (UNIX) has only three (read, write, and execute)
	##The ‘.DIR’ extension is reserved		#The ‘.DIR’ extension is reserved
	##Non-blocking file IO is not supported by the OpenVMS CRTL		#Non-blocking file IO is not supported by the OpenVMS CRTL
	##There are various known issues with symbolic link implementation		#There are various known issues with symbolic link implementation
	##The symbol '$' is commonly used in file and directory names		#The symbol '$' is commonly used in file and directory names
	##On OpenVMS chmod(0) sets the user's default permissions as opposed to resetting permissions		#On OpenVMS chmod(0) sets the user's default permissions as opposed to resetting permissions
	##To delete a directory the user has to have ‘delete’ permission for the directory		#To delete a directory the user has to have ‘delete’ permission for the directory
	##On OpenVMS <code>mkdir()</code> creates all intermediate directories (if required)		#On OpenVMS <code>mkdir()</code> creates all intermediate directories (if required)
	#Process		= Process =
	##There are no Linux-like <code>fork()</code> and <code>spawn()</code> functions		#There are no Linux-like <code>fork()</code> and <code>spawn()</code> functions
	##Pipes are created via mailbox and are not totally compatible with UNIX pipes (compatibility issues)		#Pipes are created via mailbox and are not totally compatible with UNIX pipes (compatibility issues)
	##If a child process has threads, each thread posts 'END-OF-PIPE' when the child completes/terminates		#If a child process has threads, each thread posts 'END-OF-PIPE' when the child completes/terminates
	##The functions <code>select()</code> and <code>poll()</code> work only with sockets		#The functions <code>select()</code> and <code>poll()</code> work only with sockets
	##The function <code>siginterrupt()</code> is not supported		#The function <code>siginterrupt()</code> is not supported
	##Numerous compatibility issues with signals		#Numerous compatibility issues with signals
	##Interrupting I/O operations may cause the process to hang		#Interrupting I/O operations may cause the process to hang
	##There is no root user with zero UID		#There is no root user with zero UID
	##Processes do not handle recursion overflow cleanly		#Processes do not handle recursion overflow cleanly
	#Sockets		= Sockets =
	##<code>AF_UNIX</code> has somewhat different meaning		#<code>AF_UNIX</code> has somewhat different meaning
	##Binding a socket to an empty address fails (wildcard resolved to multiple address)		#Binding a socket to an empty address fails (wildcard resolved to multiple address)
	##<code>getpeername()</code> returns ‘0.0.0.0’ instead of an error		#<code>getpeername()</code> returns ‘0.0.0.0’ instead of an error
	##<code>socket.socket.sendall</code> does not work correctly (process may crash)		#<code>socket.socket.sendall</code> does not work correctly (process may crash)
	#Time		= Time =
	##<code>time_t</code> is unsigned		#<code>time_t</code> is unsigned
	##<code>strftime()</code>		#<code>strftime()</code>
	##*Does not support <code>%G</code> format		#*Does not support <code>%G</code> format
	##*Exhibits undefined behavior when format ends with <code>%</code>		#*Exhibits undefined behavior when format ends with <code>%</code>
	##*<code>%4Y</code> is padded with spaces		#*<code>%4Y</code> is padded with spaces
	#Miscellaneous		= Miscellaneous =
	##There is no appropriate way to programmatically get all environment variables (logical names and/or symbols)		#There is no appropriate way to programmatically get all environment variables (logical names and/or symbols)
	##The current OpenVMS port of sqlite3 does not support "OR ROLLBACK"		#The current OpenVMS port of sqlite3 does not support "OR ROLLBACK"
	##<code>locale.strxfrm()</code> does not work as expected		#<code>locale.strxfrm()</code> does not work as expected
	#Compiler		= Compiler =
	##<code>uint_ptr</code> is always 64-bit, <code>void*</code> is either 32-bit or 64-bit (depending on selected pointer size)		#<code>uint_ptr</code> is always 64-bit, <code>void*</code> is either 32-bit or 64-bit (depending on selected pointer size)
	##Compiler does not support relative include paths		#Compiler does not support relative include paths
	----		----
	[[Category:VMS Python]]		[[Category:VMS Python]]

← Older revision		Revision as of 23:54, 12 September 2020
Line 1:		Line 1:
	#File system		#File system
	##Directories and files with the same name are allowed		##Directories and files with the same name are allowed.
	##File has a version, therefore two files with the same name might have different content		##File has a version, therefore two files with the same name might have different content.
	##Shared stream I/O does not work.		##Shared stream I/O does not work.
	##To guarantee the file content is on the disk ~~user have to use~~ <code>fsync()</code> function.		##To guarantee the file content is on the disk the <code>fsync()</code> function must be used.
	##Because of using logical names the real file path may be different from path used to open file.		##Because of using logical names the real file path may be different from path used to open file.
	##~~File~~ has no access time attribute.		##Files has no access time attribute.
	##Changing ~~the file~~ permissions also changes its modification time.		##Changing a files permissions also changes its modification time.
	##Changing content of directory does not change directory modification time.		##Changing the content of a directory does not change the directory modification time.
	##File has four rights bits - read, write, execute and delete. In unix it has three of it - read, write and execute.		##File has four rights bits - read, write, execute and delete. In unix it has three of it - read, write and execute.
	##‘.DIR’ extension is reserved		##‘.DIR’ extension is reserved
	##Non-blocking file IO ~~does~~ not supported in CRTL.		##Non-blocking file IO is not supported in the OpenVMS CRTL.
	##There are ~~a lot of~~ issues with symbolic link implementation		##There are various known issues with symbolic link implementation.
	##Symbol '$' is usual for file and directory names		##Symbol '$' is usual for file and directory names
	##OpenVMS <code>chmod(0)</code> sets user's default permissions, not resets them		##OpenVMS <code>chmod(0)</code> sets user's default permissions, not resets them