Import error 2291

import error 2291

Windows 7 - Import Error: no module named 'ant'. (Original URL). Hi, I am helping a guy get sorted in line , in load return sprers.eue() File. However I get this message when it comes to importing a certain table. IMP row rejected due to ORACLE error IMP ORACLE. ORA integrity constraint (APEX_WWV_FLOW_STEP_UI_FK) violated when exporting/importing single page on APEX Environment.

Gradually. opinion: Import error 2291

Socket error code 10014
Import error 2291
APACHE2 ERROR NO SITE FOUND MATCHING
ERROR 5100 CANON I250

youtube video

How to Fix : “ImportError: Cannot import name X” in Python?

Matthias Hoys

Environment: Application Express , Oracle database

We recently upgraded from APEX to The upgrade went fine, import error 2291, no problems were seen in the installation log files.

However, when I tried to export a single application page from one APEX installation and import it into another APEX installation, I received the following error:

ORA Error creating page name=&#;page01&#; ORA integrity constraint APEX_WWV_FLOW_STEP_UI_FK) violated &#; parent key not found

The application has the same application ID and workspace name. Individual page exports used to work fine on APEX versions prior to

I searched the OTN forum and the Oracle support site and I found that this is a know issue with APEX

I have you access to Oracle support, the problem is registered as bug

This is from the bug report:

&#;After upgrading the APEX instances on dev and prod to APEX the single 
page export/import from dev into prod doesn&#;t work anymore. It fails with 
ORA integrity constraint (APEX_WWV_FLOW_STEP_UI_FK) violated &#; 
parent key not found

Explain why this is not a bug:
Single component export/import is only supported for application which are 
identical on the source and target system. It relies on the fact import error 2291 other 
referenced components (for example user interface, templates, &#;) use the 
same IDs on body systems.

Because of the APEX upgrade, import error 2291, that&#;s not the case anymore. As part of the 
upgrade, several new components had to be created on the fly which do now 
have different IDs on dev and prod. That&#;s why the single component 
export/import doesn&#;t work anymore.

If the single component export/import is used to patch applications, it&#;s 
recommended to do a full export of the app on dev and import it into prod 
after upgrading to a newer version of APEX to make sure that body systems are 
using the same component IDs.&#;

There are 2 workarounds for this problem:

1) Find an existing ID in the table wwv_flow_user_interfaces on the database where you want to import. Update the export file, so you replace the ID in &#;p_user_interface_id => <id number>&#; to the existing number in wwv_flow_user_interfaces.

2) Do a full export/import of the application first. After this, you will again be able to export/import individual pages.

I tried the second workaround, and this works fine! I don&#;t receive an error anymore when I export a single page to the other installation.

 

HTH,

Matthias

 

 

Like this:

LikeLoading

Related

This entry was posted in APEX, Bugs and tagged apexAPEX_WWV_FLOW_STEP_UI_FK, application express, bug, export/import single page, integrity constrained violated, ORA by matthiashoys. Bookmark the permalink.

Junior Member

hi
we are having two schemas sc1 and sc2 at two different places.
sc1 is having all tables with data and constraints while import error 2291 is having only structure of same tables with constraints but no data.
in sc1 there r some tables having self refferential integrity constraints ,i.e, import error 2291. P rimary and Foreign key constraints.
we are trying to tranfer data from Sc1 to Sc2 & for that we are using export and import utility of oracle.
when we import data from sprers.eu to sc2, we phase problem while importing tables which have 'self refferential integrity constraints' b'coz import utility tries to import child row before parent row and finally is rejected on parent not found.

kindly give solution how to import all data to sc2.

thanking u
Hiral patel
Bhadresh patel [DBA-L&T].


Report message to a moderator

Re: Problem while importing[message # is a reply to message #]Fri, 20 May Go to previous messageGo to next message
Mahesh Rajendran
Messages:
Registered: March
Location: oracleDocoVille

Senior Member
Account Moderator

the import should handle it.
Please see the session.
Else,
you can disable all the constraints before loading
load ( import with constraints=n)
enable the consraints.
-- -- set up the tables -- [email protected] > alter table emp add constraint pk_eno primary key (empno); Table altered. [email protected] > alter table emp add constraint self_1 foreign key (mgr) references emp(empno); Table altered. -- -- Test the constraints -- [email protected] > insert into emp values (,'sam','newbie',sysdate,10,10); insert into emp values (,'sam','newbie',sysdate,10,10) * ERROR at line 1: ORA integrity constraint (sprers.eu_1) violated - parent key not found [email protected] > insert into emp values (,'sam','newbie',sysdate,10,10); 1 row created. [email protected] > commit; Commit complete. -- -- export the import error 2291. -- [email protected] > !exp scott/tiger tables=(emp) indexes=y constraints=y statistics=none Export: Release - Production on Fri May 20 Copyright (c), Oracle Corporation. All rights reserved. Connected to: Oracle9i Enterprise Edition Release - 64bit Production With the Partitioning option JServer Release - Production Export done in US7ASCII character set and AL16UTF16 NCHAR character set server uses WE8ISOP1 character set (possible charset conversion) About to export specified tables via Conventional Path. . exporting table EMP 15 rows exported Export terminated successfully without warnings. -- -- import the table to another user!. -- [email protected] > !imp scott/tiger fromuser=scott touser=mag Import: Release - Production on Fri May 20 Copyright (c), Oracle Corporation. All rights reserved. Connected to: Oracle9i Enterprise Edition Release - import error 2291 Production With the Partitioning option JServer Release - Production Export file created by EXPORT:V via conventional path import done in US7ASCII character set and AL16UTF16 NCHAR character set import server uses WE8ISOP1 character set (possible charset conversion). importing SCOTT's objects into MAG. . importing table "EMP" 15 rows imported About to enable constraints Import terminated successfully without warnings. -- -- If the target table is already present. -- [email protected] > truncate table sprers.eu; Table truncated. -- -- Import with ignore = y. -- [email protected] import error 2291 !imp scott/tiger fromuser=scott touser=mag ignore=y Import: Release - Production on Fri May 20 Copyright (c), import error 2291, Oracle Corporation. All rights reserved. Connected to: Oracle9i Enterprise Edition Release - 64bit Production With the Partitioning option JServer Release - Production Export file created by EXPORT:V via conventional path import done in US7ASCII character set and AL16UTF16 NCHAR character set import server uses WE8ISOP1 character set (possible charset conversion). importing SCOTT's objects into MAG. . importing table "EMP" 15 rows imported About to enable constraints Import terminated successfully without warnings.

Report message to a moderator

 Switch to threaded view of this topic Create a new topic Submit Reply
Goto Forum:

-=] Back to Top [=-


Current Time: Fri Sep 02 CDT

ORA integrity constraint violated

oracle tutorial webinars

ORA

The pleasure of Oracle software is the ease through which information can communicate across multiple tables in a database. Beyond having the ability to cleanly join tables and merge parameters, a number of devices in the software permit the access to and referencing of data from multiple tables, with unique features that allow you to create statements that can render formerly complex database issues with relatively little trouble.

Still, no user is perfect and no database can predict all of the potential errors that can arise during everyday use. In the realm of manipulating data across multiple data tables, a common error that you can encounter is the ORA

The Problem

ORA is typically accompanied with the message, “integrity constraint <constraint name> violated – parent key not found”, import error 2291. This means that you attempted to execute a reference to a certain table using a primary key. However, in the process of doing so, the columns that you specified failed to match the primary key. The error can also be triggered when referencing a primary key that does not exist for the table in question.

Before moving on, we should note a few things about primary keys. A primary key is a field or combination import error 2291 fields that can distinctly denote a record. It can be established in either an ALTER TABLE or CREATE TABLE statement. A given table can only have one primary key, and none of the fields that populate the primary key can hold a null value. A primary key cannot exceed thirty-two columns.

Now that we have an understanding of primary keys, we can address the error at hand. Often, the error will arise when there is a parent-child relationship between two tables via a foreign key, import error 2291. A foreign key is a method to state that values in one particular table must exist in another. Typically the referenced table is a parent table, while the child table is where the foreign key emanates from. A primary key in a parent table will, most of the time, be referenced by a foreign key in the child table.

The ORA will be triggered when you attempt to insert a value into the child table (with the foreign key), but the value does not exist in the corresponding parent table. This violates the integrity of the referential relationship, prompting Oracle to issue an error message.

The Solution

In order to remedy this error, you will need to insert the value that you attempted to place in the child table into the parent table first. Once inserted as a parent row, you can go back and insert the value into the child table.

An Example

Let’s say that you first attempted to build the parent-child key relationship:


From there, you attempt to place the following in the departments table:

You will receive an “ORA integrity constraint violated” error. Since the employee_id value of does import error 2291 already occur in the employees table, you will have to go back and insert the following into the employees table:

You can then return to the departments table and finish the key relationship:

Looking forward

Working with multiple sets of data tables can seem daunting, and it can be easy to get the references mixed up. Luckily, Oracle alleviates a great deal of stress associated with working in multiple tables at once. Remaining aware of how you are cross-referencing information from table to table can provide a solid foundation to avoiding an error like the ORA Still, because this problem requires a little bit of background knowledge and coding to solve, it would be advised to speak with a licensed Oracle software consultant if you find yourself continually having issues addressing this error.

ImportError: No module named config #

Log:
Traceback (most recent call last):
File "C:\pythonx64\Scripts\sprers.eu", line 11, in
File "C:\pythonx64\Scripts\sprers.eu", line 11, in
load_entry_point('z3==', 'console_scripts', 'z3')()
File "c:\pythonx64\lib\site-packages\pkg_resources_init_.py", linein load_entry_point
load_entry_point('z3==', 'console_scripts', 'z3')()
File "c:\pythonx64\lib\site-packages\pkg_resources_init_.py", linein load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "c:\pythonx64\lib\site-packages\pkg_resources_init_.py", linein load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "c:\pythonx64\lib\site-packages\pkg_resources_init_.py", import error 2291, linein load_entry_point
return sprers.eu()
return sprers.eu()
File "c:\pythonx64\lib\site-packages\pkg_resources_init_.py", linein load
File "c:\pythonx64\lib\site-packages\pkg_resources_init_.py", lineimport error 2291, in load
return sprers.eue()
File "c:\pythonx64\lib\site-packages\pkg_resources_init_.py", linein resolve
return sprers.eue()
File "c:\pythonx64\lib\site-packages\pkg_resources_init_.py", linein resolve
module = import(sprers.eu_name, fromlist=['name'], level=0)
File "c:\pythonx64\lib\site-packages\z3\sprers.eu", line 14, in
module = import(sprers.eu_name, import error 2291, fromlist=['name'], level=0)
from sprers.eu import get_config
File "c:\pythonx64\lib\site-packages\z3\sprers.eu", line 14, in
ImportError: No module named configfrom sprers.eu import get_config

ORA- integrity constraint violated-parent key not found tips

Burleson is the American Team

Note:This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience!Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, import error 2291, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


                    

Copyright © - 

All rights reserved by Burleson

Oracle

® is the registered trademark of Oracle Corporation.

 

When you import an EXP, you may encounter constraints that prevent you from importing.
You can disable constraints to make the import complete!
When importing, I encountered the following problems:
Column 30 MOS
IMP row rejected due to ORACLE error
IMP ORACLE error encountered
ORA integrity constraint (sprers.eu_ELEMENT_LOCATION) violated &#; parent key not found
The processing steps are as follows:
SQL> create table sprers.euuration_item_bak as select * from sprers.euuration_item;
Table created.
SQL> import error 2291 table sprers.euuration_item disable primary key;
alter table sprers.euuration_item disable primary key
*
ERROR at line 1:
ORA cannot disable constraint (sprers.eu_CONFIGURATION_ITEM) &#;
dependencies exist

SQL> Alter TABLE cmDB. configuration_item disable constraint PK_CONFIGURATION_ITEM;
alter error code 0x80070241 vista sprers.euuration_item disable PK_CONFIGURATION_ITEM
*
ERROR at line 1:
ora cannot disable constraint (sprers.eu_CONFIGURATION_ITEM) &#;
dependencies exist

SQL> Alter TABLE CMDB. Configuration_item disable constraint PK_CONFIGURATION_ITEM cascade;
Table altered.
SQL> alter table sprers.euuration_item disable primary key;
Table altered.
SQL> Alter TABLE cmDB. configuration_item disable constraint PK_CONFIGURATION_ITEM;
Table altered.

I thought the import should be ok 🙂
imp/file=sprers.eu fromuser=cmdb touser=cmdb ignore=y
But the question remains?
Why is that?The original constraint error here was a violation of the constraint to import data in the file, regardless of whether the constraint on the table was disabled or not.
Just because the table already has the same data as the file, a constraint in the file was violated when importing it.
So you can complete the import by clearing the table data.
truncate table sprers.euuration_item ;

then import:
-bask $imp/file= sprers.eu Fromuser = CMDB Touser = CMDB ignore=y
Import: Release &#; Production on Wed Aug 17
Copyright (C), Oracle and/or its Affiliates. All rights Reserved.

Connected to: Oracle Database 11g Enterprise Edition Release bit Production
With the Partitioning option
Export file created by Export :V via conventional path
import done in UTF8 character set and AL16UTF16 NCHAR character set
import server USES AL32UTF8 character set (possible charset)
export client USES US7ASCII character set (possible charset conversion)
. It is important to import CMDB&#;s objects into CMDB
imported

Read More:

Oracle / PLSQL: ORA Error Message

Resolution

The option(s) to resolve this Oracle error are:

Option #1

This error commonly occurs when you have a parent-child relationship established between two tables through a foreign key. You then have tried to insert a value into the child table, but the corresponding value does not exist in the parent table.

To correct this problem, you need to insert the value into the parent table first and then you can insert the corresponding value into the child table.

For example, if you had created the following foreign key (parent-child relationship).

CREATE TABLE supplier ( supplier_id numeric(10) not null, supplier_name varchar2(50) not null, contact_name varchar2(50), CONSTRAINT supplier_pk PRIMARY KEY (supplier_id) ); CREATE TABLE products ( product_id numeric(10) not null, supplier_id numeric(10) not null, CONSTRAINT fk_supplier FOREIGN KEY (supplier_id) REFERENCES supplier (supplier_id) );

Then you try inserting into the products table as import error 2291 INTO products (product_id, import error 2291, supplier_id) VALUES (, );

You would receive the following error message:

Oracle PLSQL

Since the supplier_id value of does not yet exist in the import error 2291 table, you need to first insert a record into the import error 2291 table as follows:

INSERT INTO supplier (supplier_id, supplier_name, contact_name) VALUES (, 'Microsoft', 'Bill Gates');

Then you can insert into the products table:

INSERT INTO products (product_id, supplier_id) VALUES (, );
import error 2291

Import error 2291 - for

Oracle / PLSQL: ORA Error Message

Resolution

The option(s) to resolve this Oracle error are:

Option #1

This error commonly occurs when you have a parent-child relationship established between two tables through a foreign key. You then have tried to insert a value into the child table, but the corresponding value does not exist in the parent table.

To correct this problem, you need to insert the value into the parent table first and then you can insert the corresponding value into the child table.

For example, if you had created the following foreign key (parent-child relationship).

CREATE TABLE supplier ( supplier_id numeric(10) not null, supplier_name varchar2(50) not null, contact_name varchar2(50), CONSTRAINT supplier_pk PRIMARY KEY (supplier_id) ); CREATE TABLE products ( product_id numeric(10) not null, supplier_id numeric(10) not null, CONSTRAINT fk_supplier FOREIGN KEY (supplier_id) REFERENCES supplier (supplier_id) );

Then you try inserting into the products table as follows:

INSERT INTO products (product_id, supplier_id) VALUES (, );

You would receive the following error message:

Oracle PLSQL

Since the supplier_id value of does not yet exist in the supplier table, you need to first insert a record into the supplier table as follows:

INSERT INTO supplier (supplier_id, supplier_name, contact_name) VALUES (, 'Microsoft', 'Bill Gates');

Then you can insert into the products table:

INSERT INTO products (product_id, supplier_id) VALUES (, );

Matthias Hoys

Environment: Application Express , Oracle database

We recently upgraded from APEX to The upgrade went fine, no problems were seen in the installation log files.

However, when I tried to export a single application page from one APEX installation and import it into another APEX installation, I received the following error:

ORA Error creating page name=&#;page01&#; ORA integrity constraint APEX_WWV_FLOW_STEP_UI_FK) violated &#; parent key not found

The application has the same application ID and workspace name. Individual page exports used to work fine on APEX versions prior to

I searched the OTN forum and the Oracle support site and I found that this is a know issue with APEX

I have you access to Oracle support, the problem is registered as bug

This is from the bug report:

&#;After upgrading the APEX instances on dev and prod to APEX the single 
page export/import from dev into prod doesn&#;t work anymore. It fails with 
ORA integrity constraint (APEX_WWV_FLOW_STEP_UI_FK) violated &#; 
parent key not found

Explain why this is not a bug:
Single component export/import is only supported for application which are 
identical on the source and target system. It relies on the fact that other 
referenced components (for example user interface, templates, &#;) use the 
same IDs on body systems.

Because of the APEX upgrade, that&#;s not the case anymore. As part of the 
upgrade, several new components had to be created on the fly which do now 
have different IDs on dev and prod. That&#;s why the single component 
export/import doesn&#;t work anymore.

If the single component export/import is used to patch applications, it&#;s 
recommended to do a full export of the app on dev and import it into prod 
after upgrading to a newer version of APEX to make sure that body systems are 
using the same component IDs.&#;

There are 2 workarounds for this problem:

1) Find an existing ID in the table wwv_flow_user_interfaces on the database where you want to import. Update the export file, so you replace the ID in &#;p_user_interface_id => <id number>&#; to the existing number in wwv_flow_user_interfaces.

2) Do a full export/import of the application first. After this, you will again be able to export/import individual pages.

I tried the second workaround, and this works fine! I don&#;t receive an error anymore when I export a single page to the other installation.

 

HTH,

Matthias

 

 

Like this:

LikeLoading

Related

This entry was posted in APEX, Bugs and tagged apex , APEX_WWV_FLOW_STEP_UI_FK, application express, bug, export/import single page, integrity constrained violated, ORA by matthiashoys. Bookmark the permalink.
When you import an EXP, you may encounter constraints that prevent you from importing.
You can disable constraints to make the import complete!
When importing, I encountered the following problems:
Column 30 MOS
IMP row rejected due to ORACLE error
IMP ORACLE error encountered
ORA integrity constraint (sprers.eu_ELEMENT_LOCATION) violated &#; parent key not found
The processing steps are as follows:
SQL> create table sprers.euuration_item_bak as select * from sprers.euuration_item;
Table created.
SQL> alter table sprers.euuration_item disable primary key;
alter table sprers.euuration_item disable primary key
*
ERROR at line 1:
ORA cannot disable constraint (sprers.eu_CONFIGURATION_ITEM) &#;
dependencies exist

SQL> Alter TABLE cmDB. configuration_item disable constraint PK_CONFIGURATION_ITEM;
alter table sprers.euuration_item disable PK_CONFIGURATION_ITEM
*
ERROR at line 1:
ora cannot disable constraint (sprers.eu_CONFIGURATION_ITEM) &#;
dependencies exist

SQL> Alter TABLE CMDB. Configuration_item disable constraint PK_CONFIGURATION_ITEM cascade;
Table altered.
SQL> alter table sprers.euuration_item disable primary key;
Table altered.
SQL> Alter TABLE cmDB. configuration_item disable constraint PK_CONFIGURATION_ITEM;
Table altered.

I thought the import should be ok 🙂
imp/file=sprers.eu fromuser=cmdb touser=cmdb ignore=y
But the question remains?
Why is that?The original constraint error here was a violation of the constraint to import data in the file, regardless of whether the constraint on the table was disabled or not.
Just because the table already has the same data as the file, a constraint in the file was violated when importing it.
So you can complete the import by clearing the table data.
truncate table sprers.euuration_item ;

then import:
-bask $imp/file= sprers.eu Fromuser = CMDB Touser = CMDB ignore=y
Import: Release &#; Production on Wed Aug 17
Copyright (C) , , Oracle and/or its Affiliates. All rights Reserved.

Connected to: Oracle Database 11g Enterprise Edition Release bit Production
With the Partitioning option
Export file created by Export :V via conventional path
import done in UTF8 character set and AL16UTF16 NCHAR character set
import server USES AL32UTF8 character set (possible charset)
export client USES US7ASCII character set (possible charset conversion)
. It is important to import CMDB&#;s objects into CMDB
imported

Read More:

ORA integrity constraint violated

oracle tutorial webinars

ORA

The pleasure of Oracle software is the ease through which information can communicate across multiple tables in a database. Beyond having the ability to cleanly join tables and merge parameters, a number of devices in the software permit the access to and referencing of data from multiple tables, with unique features that allow you to create statements that can render formerly complex database issues with relatively little trouble.

Still, no user is perfect and no database can predict all of the potential errors that can arise during everyday use. In the realm of manipulating data across multiple data tables, a common error that you can encounter is the ORA

The Problem

ORA is typically accompanied with the message, “integrity constraint <constraint name> violated – parent key not found”. This means that you attempted to execute a reference to a certain table using a primary key. However, in the process of doing so, the columns that you specified failed to match the primary key. The error can also be triggered when referencing a primary key that does not exist for the table in question.

Before moving on, we should note a few things about primary keys. A primary key is a field or combination of fields that can distinctly denote a record. It can be established in either an ALTER TABLE or CREATE TABLE statement. A given table can only have one primary key, and none of the fields that populate the primary key can hold a null value. A primary key cannot exceed thirty-two columns.

Now that we have an understanding of primary keys, we can address the error at hand. Often, the error will arise when there is a parent-child relationship between two tables via a foreign key. A foreign key is a method to state that values in one particular table must exist in another. Typically the referenced table is a parent table, while the child table is where the foreign key emanates from. A primary key in a parent table will, most of the time, be referenced by a foreign key in the child table.

The ORA will be triggered when you attempt to insert a value into the child table (with the foreign key), but the value does not exist in the corresponding parent table. This violates the integrity of the referential relationship, prompting Oracle to issue an error message.

The Solution

In order to remedy this error, you will need to insert the value that you attempted to place in the child table into the parent table first. Once inserted as a parent row, you can go back and insert the value into the child table.

An Example

Let’s say that you first attempted to build the parent-child key relationship:


From there, you attempt to place the following in the departments table:

You will receive an “ORA integrity constraint violated” error. Since the employee_id value of does not already occur in the employees table, you will have to go back and insert the following into the employees table:

You can then return to the departments table and finish the key relationship:

Looking forward

Working with multiple sets of data tables can seem daunting, and it can be easy to get the references mixed up. Luckily, Oracle alleviates a great deal of stress associated with working in multiple tables at once. Remaining aware of how you are cross-referencing information from table to table can provide a solid foundation to avoiding an error like the ORA Still, because this problem requires a little bit of background knowledge and coding to solve, it would be advised to speak with a licensed Oracle software consultant if you find yourself continually having issues addressing this error.

ORA- integrity constraint violated-parent key not found tips

Burleson is the American Team

Note:This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience!Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


                    

Copyright © - 

All rights reserved by Burleson

Oracle

® is the registered trademark of Oracle Corporation.

 

Error importing certain aliases from zsh #

I just installed xonsh from the AUR. I was having issues and eventually found # so I moved to xonsh-git, which seems to have improved things. However, I am still having some problems. I am using an unmodified grml config file from the extra repository. Two aliases won't import. I can certainly comment those out as I never use them, but I think it is something worth looking at anyway. This is what I am getting:

[email protected] ~ $ source-zsh /etc/zsh/zshrc
Skipping application of 'egrep' alias from 'zsh' since it shares a name with an existing xonsh alias. Use "--overwrite-alias" option to apply it anyway.
Skipping application of 'grep' alias from 'zsh' since it shares a name with an existing xonsh alias. Use "--overwrite-alias" option to apply it anyway.
Skipping application of 'l' alias from 'zsh' since it shares a name with an existing xonsh alias. Use "--overwrite-alias" option to apply it anyway.

snip more of the same

/usr/lib/python/site-packages/xonsh/amalgam.py RuntimeWarning: could not parse alias "term2iso": ValueError('No escaped character',)
RuntimeWarning)
/usr/lib/python/site-packages/xonsh/amalgam.py RuntimeWarning: could not parse alias "term2utf": ValueError('No escaped character',)
RuntimeWarning)

Here's those two aliases from the config file:

alias term2iso="echo 'Setting terminal to iso mode' ; print -n '\e%@'"
alias term2utf="echo 'Setting terminal to utf-8 mode'; print -n '\e%G'"

zsh version is
grml config version is

ImportError: No module named config #

Log:
Traceback (most recent call last):
File "C:\pythonx64\Scripts\sprers.eu", line 11, in
File "C:\pythonx64\Scripts\sprers.eu", line 11, in
load_entry_point('z3==', 'console_scripts', 'z3')()
File "c:\pythonx64\lib\site-packages\pkg_resources_init_.py", line , in load_entry_point
load_entry_point('z3==', 'console_scripts', 'z3')()
File "c:\pythonx64\lib\site-packages\pkg_resources_init_.py", line , in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "c:\pythonx64\lib\site-packages\pkg_resources_init_.py", line , in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "c:\pythonx64\lib\site-packages\pkg_resources_init_.py", line , in load_entry_point
return sprers.eu()
return sprers.eu()
File "c:\pythonx64\lib\site-packages\pkg_resources_init_.py", line , in load
File "c:\pythonx64\lib\site-packages\pkg_resources_init_.py", line , in load
return sprers.eue()
File "c:\pythonx64\lib\site-packages\pkg_resources_init_.py", line , in resolve
return sprers.eue()
File "c:\pythonx64\lib\site-packages\pkg_resources_init_.py", line , in resolve
module = import(sprers.eu_name, fromlist=['name'], level=0)
File "c:\pythonx64\lib\site-packages\z3\sprers.eu", line 14, in
module = import(sprers.eu_name, fromlist=['name'], level=0)
from sprers.eu import get_config
File "c:\pythonx64\lib\site-packages\z3\sprers.eu", line 14, in
ImportError: No module named configfrom sprers.eu import get_config

0 Comments

Leave a Comment