Under python 3.4 constants.py gives an error at import about pyinotify

[jremes-foss]

Hi. It looks like a classical "gotcha" with Python. Please have a look at this:

In [1]: 02000000
Out[1]: 524288

In [2]: 00004000
Out[2]: 2048

Basically: In Python, leading zeros do convert the number to octal.

[jremes-foss]

Next question: What are constants IN_CLOEXEC and IN_NONBLOCK supposed to be? Hexadecimal? Decimal?

[dickkniep]

As far as I know they should be octal and then they should start with:

 
0o 

 
So if you prepend the current values with 0o it should work. (BTW. there are 4 values affected in constants.py)

If you want I can send you a patch.

Met vriendelijke groet,
Dick Kniep
Lindix BV
tel. [phone]
mob. [phone]

 
-----Oorspronkelijk bericht-----
Van:Juha [email protected]
Verzonden:vr 02-10-2015 13:28
Onderwerp:Re: [PyInotify] Under python 3.4 constants.py gives an error at import (#3)
Aan:dsoprea/PyInotify [email protected];
CC:Dick Kniep [email protected];

Next question: What are constants IN_CLOEXEC and IN_NONBLOCK supposed to be? Hexadecimal? Decimal?

—
Reply to this email directly or view it on GitHub.

 

[ololduck]

Hey, thanks for fixing this.

Any idea about when the commit e747615 will be in pypi?

[dsoprea]

Done.

Dustin

On Thu, Jun 2, 2016 at 8:31 AM, Paul Ollivier [email protected]
wrote:

Hey, thanks for fixing this.

Any idea about when the commit e747615
e747615
will be in pypi?

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#3 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AArram-P8yW2rV5Kay1r4L2W0wO2d6OLks5qHs0dgaJpZM4GGYgW
.