Re: Defamation
On Thu, 22 Oct 2015 13:19:14 +0200 Laura Creighton wrote: > One thing to recall is that 'who/what can be defamed' > varies a lot. In Sweden you cannot defame a corporation. The > defamation regulations in the Penal Code only apply to private > individuals. If you cannot bleed, you cannot be defamed. In certain > situations the Swedish Marketing Act may be used to stop defamation of > a corporate entity -- if a rival has, without basis, tainted a rival's > reputation -- but this sort of protection is limited. This makes > Sweden an attractive place to discuss Mosanto, and their evil > practices, even though, like a lot of places Sweden's defamation > law does not have a clause saying roughly 'if it is true, it isn't > defamation'. Just 'intent to villify' is enough. > > Laura Corporations also cannot be defamed here in Australia, but truth is a complete defence. On the other hand, intent is irrelevant. This has the unfortunate consequence that by mocking a fictional character you run the risk of defaming a real person who happens to have the same name, or even similar characteristics, even if you have never heard of them. -- https://mail.python.org/mailman/listinfo/python-list
Re: Defamation
On Thu, 22 Oct 2015 13:19:14 +0200 Laura Creighton wrote: > One thing to recall is that 'who/what can be defamed' > varies a lot. In Sweden you cannot defame a corporation. The > defamation regulations in the Penal Code only apply to private > individuals. If you cannot bleed, you cannot be defamed. In certain > situations the Swedish Marketing Act may be used to stop defamation of > a corporate entity -- if a rival has, without basis, tainted a rival's > reputation -- but this sort of protection is limited. This makes > Sweden an attractive place to discuss Mosanto, and their evil > practices, even though, like a lot of places Sweden's defamation > law does not have a clause saying roughly 'if it is true, it isn't > defamation'. Just 'intent to villify' is enough. > > Laura Corporations also cannot be defamed here in Australia (but only since 2006). Truth is a complete defence; but on the other hand, intent is irrelevant. This has the unfortunate consequence that by mocking a fictional character you run the risk of defaming a real person who happens to have the same name, or even similar characteristics, even if you have never heard of them. -- https://mail.python.org/mailman/listinfo/python-list
how to get python socket to use a specific interface
I need to run lynx on a ubuntu headless server with a specific IP address in
order to try and cancel an email blacklist.
Lynx doesn't provide a way to do that so I thought to use a local proxy. I tried
pymiproxy and hacked the connection code so it looked like this
proxy.py
from socket import socket, SOL_SOCKET
...
import os
BIND_ADDRESS = os.environ.get('PYMIPROXY_BIND_ADDRESS',None)
BIND_DEVICE = os.environ.get('PYMIPROXY_BIND_DEVICE',None)
.
# Connect to destination
sock = self._proxy_sock = socket()
sock.settimeout(10)
if BIND_ADDRESS:
sock.bind((BIND_ADDRESS, 0))
if BIND_DEVICE:
sock.setsockopt(SOL_SOCKET, 25, BIND_DEVICE)
sock.connect((self.hostname, int(self.port)))
25 is derived from /usr/include/asm-generic/socket.h
#define SO_BINDTODEVICE 25
This works if I export BIND_DEVICE='eth0' and run as root, but my desired
interface is actually called 'eth0:0' and when I run with that exported I get a
device error. Does anyone know what I should call the device?
--
Robin Becker
--
https://mail.python.org/mailman/listinfo/python-list
Re: UNABLE TO GET IDLE TO RUN
In a message of Fri, 23 Oct 2015 00:19:42 -0400, Terry Reedy writes: >On 10/21/2015 11:24 AM, Terry Alexander via Python-list wrote: > >> I have tried installing both Python 2.7 and 3.5, and in both cases I >> cannot get IDLE to work. I received the following message both times: > >What OS? Windows? which version? How did you start IDLE? Start menu >icon? Command line? > >> IDLE’s subprocess didn’t make connection.Either IDLE can’t start a >> subprocess or personal firewall software is blocking the connection. >> >> I am running Norton, and disabled it, but still IDLE will not run. Any >> suggestions? > >Don't shout with ALL CAPS in the subject line. It usually indicates >spam. I already know that this problem is very frustrating. > >Firewalls are seldom the problems anymore. I occasionally saw this on >Win 7 when restarting, but never on startup, and never more than once or >twice in a session. > >What's left is misconfiguration of your network interface that prevents >a loopback connection. There might be answers on Stackoverflow that >would help, depending on your OS. > >In the meanwhile, you can start IDLE with the -n option. Either use a >command line or create an 'IDLE -n' icon. Again, details depend on >exact OS. > >-- >Terry Jan Reedy You can also get this message if you run idle in directory where you have your own python file whose name shadows something in the standard library (that idle is interested in). I think it was a file named 'string.py' that did this to a student of mine a few years ago. Laura -- https://mail.python.org/mailman/listinfo/python-list
Re: UNABLE TO GET IDLE TO RUN
Laura Creighton wrote: > In a message of Fri, 23 Oct 2015 00:19:42 -0400, Terry Reedy writes: >>On 10/21/2015 11:24 AM, Terry Alexander via Python-list wrote: >> >>> I have tried installing both Python 2.7 and 3.5, and in both cases I >>> cannot get IDLE to work. I received the following message both times: >> >>What OS? Windows? which version? How did you start IDLE? Start menu >>icon? Command line? >> >>> IDLE’s subprocess didn’t make connection.Either IDLE can’t start a >>> subprocess or personal firewall software is blocking the connection. >>> >>> I am running Norton, and disabled it, but still IDLE will not run. Any >>> suggestions? >> >>Don't shout with ALL CAPS in the subject line. It usually indicates >>spam. I already know that this problem is very frustrating. >> >>Firewalls are seldom the problems anymore. I occasionally saw this on >>Win 7 when restarting, but never on startup, and never more than once or >>twice in a session. >> >>What's left is misconfiguration of your network interface that prevents >>a loopback connection. There might be answers on Stackoverflow that >>would help, depending on your OS. >> >>In the meanwhile, you can start IDLE with the -n option. Either use a >>command line or create an 'IDLE -n' icon. Again, details depend on >>exact OS. >> >>-- >>Terry Jan Reedy > > You can also get this message if you run idle in directory where you > have your own python file whose name shadows something in the > standard library (that idle is interested in). I think it was > a file named 'string.py' that did this to a student of mine a > few years ago. > > Laura I tried it out: $ mkdir test $ cd test $ touch string.py $ idle3 Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3.4/idlelib/run.py", line 12, in from idlelib import CallTips File "/usr/lib/python3.4/idlelib/CallTips.py", line 16, in from idlelib.HyperParser import HyperParser File "/usr/lib/python3.4/idlelib/HyperParser.py", line 14, in _ASCII_ID_CHARS = frozenset(string.ascii_letters + string.digits + "_") AttributeError: 'module' object has no attribute 'ascii_letters' Then idle shows the message and quits after you hit OK. Is there a bug report? -- https://mail.python.org/mailman/listinfo/python-list
ANN: eGenix mxODBC Connect 2.1.5 - Remote Python Database Interface
ANNOUNCING eGenix.com mxODBC Connect Remote Python Database Interface Version 2.1.5 mxODBC Connect is our commercially supported client-server product for connecting Python applications to relational databases in a truly platform independent way. This announcement is also available on our website for online reading: http://www.egenix.com/company/news/eGenix-mxODBC-Connect-2.1.5-GA.html INTRODUCTION The mxODBC Connect Database Interface for Python allows users to easily connect Python applications to all major databases on the market today in a highly portable, convenient and secure way. Python Database Connectivity the Easy Way - Building on our mxODBC database interface for Python, mxODBC Connect is designed as client-server application, so you no longer need to find production quality database drivers for all platforms you target with your Python application. Instead, you use an easy to install royalty-free Python client library which connects directly to the mxODBC Connect database server over the network. This makes mxODBC Connect a great basis for writing cross-platform multi-tier database applications and utilities in Python, especially if you run applications that need to communicate with databases such as MS SQL Server and MS Access, Oracle Database, IBM DB2 and Informix, Sybase ASE and Sybase Anywhere, MySQL, PostgreSQL, SAP MaxDB and many more, that run on Windows or Linux machines. Ideal for Database Driven Client Applications - By removing the need to install and configure ODBC drivers on the client side and dealing with complicated network setups for each set of drivers, mxODBC Connect greatly simplifies deployment of database driven client applications, while at the same time making the network communication between client and database server more efficient and more secure. For more information, please have a look at the mxODBC Connect product page, in particular, the full list of available features. For more information, please see the product page: http://www.egenix.com/products/python/mxODBCConnect/ NEWS mxODBC Connect 2.1.5 is a patch level release of our successful mxODBC Connect database product. It includes these enhancements and fixes: Security Enhancements - * Prevent mxODBC Connect Server from listening on sockets which are unbound due to a configuration error. The OS will typically assign a random port and listen on all interfaces, which can pose a security issue. mxODBC Connect Enhancements --- * Add allow_clients configuration variable to [Session] config section of the mxODBC Connect Server. This allows overriding the list accepted client IP addresses/networks and helps to e.g. allow connections from clients not on the server's interface networks. * Added "connections" shortcut support for allow_clients to easily access the list of configured networks defined by the connection sections. * Added "all" and "localhost" shortcuts support for allow_clients to simplify allowing any client IP address or only the local machine. For the full set of changes, including those of the 2.1 series of mxODBC Connect, please check the mxODBC Connect change log: http://www.egenix.com/products/python/mxODBCConnect/changelog.html UPGRADING You are encouraged to upgrade to this latest mxODBC Connect release. When upgrading, please always upgrade both the server and the client installations to the same version - even for patch level releases. We will give out 20% discount coupons for upgrade purchases going from mxODBC Connect Server 1.x to 2.1 and 50% coupons for upgrades from mxODBC Connect Server 2.x to 2.1. Please contact the eGenix.com Sales Team (sa...@egenix.com) with your existing license serials for details. Users of our stand-alone mxODBC product will have to purchase new licenses from our online shop in order to use mxODBC Connect. You can request free 30-day evaluation licenses by visiting our web-site or writing to sa...@egenix.com, stating your name (or the name of the company) and the number of eval licenses that you need. http://www.egenix.com/products/python/mxODBCConnect/#Evaluation DOWNLOADS The download archives as well as instructions for installation and configuration of the product can be found on the product page: http://www.egenix.com/products/python/mxODBCConnect/ If you want to try the package, jump straight to
