[ python-Bugs-1749512 ] imaplib cannot handle mailboxes with ACL: lrs
Bugs item #1749512, was opened at 2007-07-07 09:52 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1749512&group_id=5470 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Extension Modules Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Florian Friesdorf (chaoflow) Assigned to: Nobody/Anonymous (nobody) Summary: imaplib cannot handle mailboxes with ACL: lrs Initial Comment: The imaplib in python 2.4 and 2.5 is not able to handle a mailbox with ACL set to lrs correctly, as it treats it the same as a mailbox opened with EXAMINE. A mailbox with lrs can save \Seen flags, a mailbox opened with EXAMINE cannot. The attached patch is giving a proposal on how to fix it. The current select raises an exception, in case the server tells READ-ONLY in a response. However, for lrs this is the case, but nevertheless, it is possible to save per-use state information. With the patch this is not the case anymore. A readonly exception is only raised in case of an lr mailbox, as that is an equivalent to a mailbox opened with EXAMINE, i.e. select(..., readonly=True). A READ-ONLY in the response to a select is saved in self.is_readonly. Programs who relied on an exception being raised during select, would now need to query that variable. In case the state was not READ-ONLY during select, but becomes at some later point during command execution, still a readonly exception is raised. The patched imaplib was tested successfully with a slightly adapted offlineimap. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1749512&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1749567 ] PLATFORM macro in PC/pyconfig.h already defined by Apache
Bugs item #1749567, was opened at 2007-07-07 14:34
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1749567&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Interpreter Core
Group: Python 2.5
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Adal Chiriliuc (adalx)
Assigned to: Nobody/Anonymous (nobody)
Summary: PLATFORM macro in PC/pyconfig.h already defined by Apache
Initial Comment:
Both pyconfig.h from Python and os.h from Apache define the PLATFORM macro
("win32" vs. "Win32").
For projects which include both (like mod_wsgi) this generates a level 1
warning in Visual Studio.
Maybe the PLATFORM define could be renamed to PY_PLATFORM? There are a few
other macros which could potentially collide with other libraries like COMPILER.
Obviously this problem is shared by Python and Apache. I'm not implying that
Python is the one which should fix it.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1749567&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1749567 ] PLATFORM macro in PC/pyconfig.h already defined by Apache
Bugs item #1749567, was opened at 2007-07-07 14:34
Message generated for change (Settings changed) made by adalx
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1749567&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Interpreter Core
Group: Python 2.5
Status: Open
Resolution: None
>Priority: 3
Private: No
Submitted By: Adal Chiriliuc (adalx)
Assigned to: Nobody/Anonymous (nobody)
Summary: PLATFORM macro in PC/pyconfig.h already defined by Apache
Initial Comment:
Both pyconfig.h from Python and os.h from Apache define the PLATFORM macro
("win32" vs. "Win32").
For projects which include both (like mod_wsgi) this generates a level 1
warning in Visual Studio.
Maybe the PLATFORM define could be renamed to PY_PLATFORM? There are a few
other macros which could potentially collide with other libraries like COMPILER.
Obviously this problem is shared by Python and Apache. I'm not implying that
Python is the one which should fix it.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1749567&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1749583 ] expanduser("~") on Windows looks for HOME first
Bugs item #1749583, was opened at 2007-07-07 08:44
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1749583&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Library
Group: Python 2.5
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Edward Diener (eldiener)
Assigned to: Nobody/Anonymous (nobody)
Summary: expanduser("~") on Windows looks for HOME first
Initial Comment:
On Windows, using expanduser("~") the home directory is replaced either first
by the environment variable HOME or, if that is not found, by a combination of
HOMEDRIVE and HOMEPATH."
But HOME is almost never the home directory for Windows, although it is under
Linux/Unix, only the combination of HOMEDRIVE and HOMEPATH is valid, which is
always set.
If MSYS is installed under Windows, where HOME must be set to the MSYS home
directory for a given user in order to emulate Linux/Unix, attempting to use
os.path.expanduser("~") will incorrectly return the MSYS home directory for a
given user rather than the Windows home directory for the logged in user. So I
think the os.path.expanduser("~") works incorrectly in this case and needs to
be fixed, else you are telling users never to use MSYS under Windows. There may
be other Linux/Unix emulation packages which can be installed under Windows,
and my guess is that if there is then the HOME environment variable gets set to
some user home directory under that emulation package, just like it does for
MSYS.
The correct order under Windows is to look for the environment variable
combination HOMEDRIVE/HOMEPATH first and only if that is not found ( very
unlikely ) should expanduser("~") look for the environment variable HOME.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1749583&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1749583 ] expanduser("~") on Windows looks for HOME first
Bugs item #1749583, was opened at 2007-07-07 05:44
Message generated for change (Comment added) made by hdiwan650
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1749583&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Library
Group: Python 2.5
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Edward Diener (eldiener)
Assigned to: Nobody/Anonymous (nobody)
Summary: expanduser("~") on Windows looks for HOME first
Initial Comment:
On Windows, using expanduser("~") the home directory is replaced either first
by the environment variable HOME or, if that is not found, by a combination of
HOMEDRIVE and HOMEPATH."
But HOME is almost never the home directory for Windows, although it is under
Linux/Unix, only the combination of HOMEDRIVE and HOMEPATH is valid, which is
always set.
If MSYS is installed under Windows, where HOME must be set to the MSYS home
directory for a given user in order to emulate Linux/Unix, attempting to use
os.path.expanduser("~") will incorrectly return the MSYS home directory for a
given user rather than the Windows home directory for the logged in user. So I
think the os.path.expanduser("~") works incorrectly in this case and needs to
be fixed, else you are telling users never to use MSYS under Windows. There may
be other Linux/Unix emulation packages which can be installed under Windows,
and my guess is that if there is then the HOME environment variable gets set to
some user home directory under that emulation package, just like it does for
MSYS.
The correct order under Windows is to look for the environment variable
combination HOMEDRIVE/HOMEPATH first and only if that is not found ( very
unlikely ) should expanduser("~") look for the environment variable HOME.
--
Comment By: Hasan Diwan (hdiwan650)
Date: 2007-07-07 12:08
Message:
Logged In: YES
user_id=1185570
Originator: NO
This has been fixed as of Rev 54419 in trunk, perhaps someone would be
kind enough to backport it?
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1749583&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1749583 ] expanduser("~") on Windows looks for HOME first
Bugs item #1749583, was opened at 2007-07-07 05:44
Message generated for change (Comment added) made by hdiwan650
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1749583&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Library
Group: Python 2.5
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Edward Diener (eldiener)
Assigned to: Nobody/Anonymous (nobody)
Summary: expanduser("~") on Windows looks for HOME first
Initial Comment:
On Windows, using expanduser("~") the home directory is replaced either first
by the environment variable HOME or, if that is not found, by a combination of
HOMEDRIVE and HOMEPATH."
But HOME is almost never the home directory for Windows, although it is under
Linux/Unix, only the combination of HOMEDRIVE and HOMEPATH is valid, which is
always set.
If MSYS is installed under Windows, where HOME must be set to the MSYS home
directory for a given user in order to emulate Linux/Unix, attempting to use
os.path.expanduser("~") will incorrectly return the MSYS home directory for a
given user rather than the Windows home directory for the logged in user. So I
think the os.path.expanduser("~") works incorrectly in this case and needs to
be fixed, else you are telling users never to use MSYS under Windows. There may
be other Linux/Unix emulation packages which can be installed under Windows,
and my guess is that if there is then the HOME environment variable gets set to
some user home directory under that emulation package, just like it does for
MSYS.
The correct order under Windows is to look for the environment variable
combination HOMEDRIVE/HOMEPATH first and only if that is not found ( very
unlikely ) should expanduser("~") look for the environment variable HOME.
--
Comment By: Hasan Diwan (hdiwan650)
Date: 2007-07-07 12:10
Message:
Logged In: YES
user_id=1185570
Originator: NO
This has been fixed as of Rev 54419 in trunk, perhaps someone would be
kind enough to backport it?
--
Comment By: Hasan Diwan (hdiwan650)
Date: 2007-07-07 12:08
Message:
Logged In: YES
user_id=1185570
Originator: NO
This has been fixed as of Rev 54419 in trunk, perhaps someone would be
kind enough to backport it?
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1749583&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1749583 ] expanduser("~") on Windows looks for HOME first
Bugs item #1749583, was opened at 2007-07-07 05:44
Message generated for change (Comment added) made by hdiwan650
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1749583&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Library
Group: Python 2.5
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Edward Diener (eldiener)
Assigned to: Nobody/Anonymous (nobody)
Summary: expanduser("~") on Windows looks for HOME first
Initial Comment:
On Windows, using expanduser("~") the home directory is replaced either first
by the environment variable HOME or, if that is not found, by a combination of
HOMEDRIVE and HOMEPATH."
But HOME is almost never the home directory for Windows, although it is under
Linux/Unix, only the combination of HOMEDRIVE and HOMEPATH is valid, which is
always set.
If MSYS is installed under Windows, where HOME must be set to the MSYS home
directory for a given user in order to emulate Linux/Unix, attempting to use
os.path.expanduser("~") will incorrectly return the MSYS home directory for a
given user rather than the Windows home directory for the logged in user. So I
think the os.path.expanduser("~") works incorrectly in this case and needs to
be fixed, else you are telling users never to use MSYS under Windows. There may
be other Linux/Unix emulation packages which can be installed under Windows,
and my guess is that if there is then the HOME environment variable gets set to
some user home directory under that emulation package, just like it does for
MSYS.
The correct order under Windows is to look for the environment variable
combination HOMEDRIVE/HOMEPATH first and only if that is not found ( very
unlikely ) should expanduser("~") look for the environment variable HOME.
--
Comment By: Hasan Diwan (hdiwan650)
Date: 2007-07-07 12:10
Message:
Logged In: YES
user_id=1185570
Originator: NO
This has been fixed as of Rev 54419 in trunk, perhaps someone would be
kind enough to backport it?
--
Comment By: Hasan Diwan (hdiwan650)
Date: 2007-07-07 12:10
Message:
Logged In: YES
user_id=1185570
Originator: NO
This has been fixed as of Rev 54419 in trunk, perhaps someone would be
kind enough to backport it?
--
Comment By: Hasan Diwan (hdiwan650)
Date: 2007-07-07 12:08
Message:
Logged In: YES
user_id=1185570
Originator: NO
This has been fixed as of Rev 54419 in trunk, perhaps someone would be
kind enough to backport it?
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1749583&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1749583 ] expanduser("~") on Windows looks for HOME first
Bugs item #1749583, was opened at 2007-07-07 05:44
Message generated for change (Comment added) made by hdiwan650
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1749583&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Library
Group: Python 2.5
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Edward Diener (eldiener)
Assigned to: Nobody/Anonymous (nobody)
Summary: expanduser("~") on Windows looks for HOME first
Initial Comment:
On Windows, using expanduser("~") the home directory is replaced either first
by the environment variable HOME or, if that is not found, by a combination of
HOMEDRIVE and HOMEPATH."
But HOME is almost never the home directory for Windows, although it is under
Linux/Unix, only the combination of HOMEDRIVE and HOMEPATH is valid, which is
always set.
If MSYS is installed under Windows, where HOME must be set to the MSYS home
directory for a given user in order to emulate Linux/Unix, attempting to use
os.path.expanduser("~") will incorrectly return the MSYS home directory for a
given user rather than the Windows home directory for the logged in user. So I
think the os.path.expanduser("~") works incorrectly in this case and needs to
be fixed, else you are telling users never to use MSYS under Windows. There may
be other Linux/Unix emulation packages which can be installed under Windows,
and my guess is that if there is then the HOME environment variable gets set to
some user home directory under that emulation package, just like it does for
MSYS.
The correct order under Windows is to look for the environment variable
combination HOMEDRIVE/HOMEPATH first and only if that is not found ( very
unlikely ) should expanduser("~") look for the environment variable HOME.
--
Comment By: Hasan Diwan (hdiwan650)
Date: 2007-07-07 12:11
Message:
Logged In: YES
user_id=1185570
Originator: NO
This has been fixed as of Rev 54419 in trunk, perhaps someone would be
kind enough to backport it?
--
Comment By: Hasan Diwan (hdiwan650)
Date: 2007-07-07 12:10
Message:
Logged In: YES
user_id=1185570
Originator: NO
This has been fixed as of Rev 54419 in trunk, perhaps someone would be
kind enough to backport it?
--
Comment By: Hasan Diwan (hdiwan650)
Date: 2007-07-07 12:10
Message:
Logged In: YES
user_id=1185570
Originator: NO
This has been fixed as of Rev 54419 in trunk, perhaps someone would be
kind enough to backport it?
--
Comment By: Hasan Diwan (hdiwan650)
Date: 2007-07-07 12:08
Message:
Logged In: YES
user_id=1185570
Originator: NO
This has been fixed as of Rev 54419 in trunk, perhaps someone would be
kind enough to backport it?
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1749583&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1749583 ] expanduser("~") on Windows looks for HOME first
Bugs item #1749583, was opened at 2007-07-07 08:44
Message generated for change (Comment added) made by eldiener
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1749583&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Library
Group: Python 2.5
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Edward Diener (eldiener)
Assigned to: Nobody/Anonymous (nobody)
Summary: expanduser("~") on Windows looks for HOME first
Initial Comment:
On Windows, using expanduser("~") the home directory is replaced either first
by the environment variable HOME or, if that is not found, by a combination of
HOMEDRIVE and HOMEPATH."
But HOME is almost never the home directory for Windows, although it is under
Linux/Unix, only the combination of HOMEDRIVE and HOMEPATH is valid, which is
always set.
If MSYS is installed under Windows, where HOME must be set to the MSYS home
directory for a given user in order to emulate Linux/Unix, attempting to use
os.path.expanduser("~") will incorrectly return the MSYS home directory for a
given user rather than the Windows home directory for the logged in user. So I
think the os.path.expanduser("~") works incorrectly in this case and needs to
be fixed, else you are telling users never to use MSYS under Windows. There may
be other Linux/Unix emulation packages which can be installed under Windows,
and my guess is that if there is then the HOME environment variable gets set to
some user home directory under that emulation package, just like it does for
MSYS.
The correct order under Windows is to look for the environment variable
combination HOMEDRIVE/HOMEPATH first and only if that is not found ( very
unlikely ) should expanduser("~") look for the environment variable HOME.
--
>Comment By: Edward Diener (eldiener)
Date: 2007-07-07 16:00
Message:
Logged In: YES
user_id=490593
Originator: YES
Let me just correct my original report to say that the fix should be
HOMEDRIVE+HOMEPATH, which is probably already known.
--
Comment By: Hasan Diwan (hdiwan650)
Date: 2007-07-07 15:11
Message:
Logged In: YES
user_id=1185570
Originator: NO
This has been fixed as of Rev 54419 in trunk, perhaps someone would be
kind enough to backport it?
--
Comment By: Hasan Diwan (hdiwan650)
Date: 2007-07-07 15:10
Message:
Logged In: YES
user_id=1185570
Originator: NO
This has been fixed as of Rev 54419 in trunk, perhaps someone would be
kind enough to backport it?
--
Comment By: Hasan Diwan (hdiwan650)
Date: 2007-07-07 15:10
Message:
Logged In: YES
user_id=1185570
Originator: NO
This has been fixed as of Rev 54419 in trunk, perhaps someone would be
kind enough to backport it?
--
Comment By: Hasan Diwan (hdiwan650)
Date: 2007-07-07 15:08
Message:
Logged In: YES
user_id=1185570
Originator: NO
This has been fixed as of Rev 54419 in trunk, perhaps someone would be
kind enough to backport it?
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1749583&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
